Salvatore Bonaccorso <carnil@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 > - Remaps SSL_OP_NO_TLSv1_1, so applications linked to 1.0.0 > can talk to servers supporting TLS 1.1 but not TLS 1.2 > - Drop rc4_hmac_md5.patch, applied upstream Does it mean we're going to hit the same kind of issues next time there's a similar change in openssl? Mraw, KiBi.
Attachment:
signature.asc
Description: Digital signature