On Sun, Jun 03, 2012 at 01:34:05AM +0200, Cyril Brulebois wrote:
> Hi,
>
> Kurt Roeckx (02/06/2012):
> > This change was made to make sure applications build against
> > 1.0.0 can talk to a server that does TLS 1.1 but not TLS 1.2,
> > as the changelog says. This is not something I like to chang
On Fri, Jun 01, 2012 at 11:07:44AM +0200, Cyril Brulebois wrote:
> Salvatore Bonaccorso (01/06/2012):
> > It was reported [1], that libnet-ssleay-perl does not report the
> > correct constant value for SSL_OP_NO_TLSv1_1. There was the following
> > change in openssl 1.0.1b-1:
> >
> > openssl (1.
Hi Cyril
Thanks for your reply!
(adding debian-perl list to the recipients, to have more comments if
needed)
On Fri, Jun 01, 2012 at 11:07:44AM +0200, Cyril Brulebois wrote:
> Salvatore Bonaccorso (01/06/2012):
> > It was reported [1], that libnet-ssleay-perl does not report the
> > correct con
Salvatore Bonaccorso (01/06/2012):
> It was reported [1], that libnet-ssleay-perl does not report the
> correct constant value for SSL_OP_NO_TLSv1_1. There was the following
> change in openssl 1.0.1b-1:
>
> openssl (1.0.1b-1) unstable; urgency=high
> .
>* New upstream version
> - Rema
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Release Team
It was reported [1], that libnet-ssleay-perl does not report the
correct constant value for SSL_OP_NO_TLSv1_1. There was the
5 matches
Mail list logo