Bug#675434: nmu: libnet-ssleay-perl_1.48-1

2012-06-02 Thread Salvatore Bonaccorso
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 car...@debian.org (01/06/2012): It was reported [1], that libnet-ssleay-perl does not report the

Bug#675434: nmu: libnet-ssleay-perl_1.48-1

2012-06-02 Thread Kurt Roeckx
On Fri, Jun 01, 2012 at 11:07:44AM +0200, Cyril Brulebois wrote: Salvatore Bonaccorso car...@debian.org (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:

Bug#675434: nmu: libnet-ssleay-perl_1.48-1

2012-06-02 Thread Kurt Roeckx
On Sun, Jun 03, 2012 at 01:34:05AM +0200, Cyril Brulebois wrote: Hi, Kurt Roeckx k...@roeckx.be (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

Bug#675434: nmu: libnet-ssleay-perl_1.48-1

2012-06-01 Thread Salvatore Bonaccorso
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

Bug#675434: nmu: libnet-ssleay-perl_1.48-1

2012-06-01 Thread Cyril Brulebois
Salvatore Bonaccorso car...@debian.org (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