Should we close this bug?
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
-- Kurt Roeckx
On Fri, Apr 27, 2012 at 05:01:19PM +0800, Guo Yixuan wrote:
Should we close this bug?
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
Some bugs
The problem is that openssl 1.0.0 turned on a non-existing
option in SSL_OP_ALL, which the 1.0.1 version interpretes as
disabling support for TLS 1.1.
Is this to be fixed (upstream?) soon? Or is a debian patch needed?
It is worrying to have to use an old version when several security fixes
On Wed, Apr 25, 2012 at 02:02:12PM +0100, ael wrote:
The problem is that openssl 1.0.0 turned on a non-existing
option in SSL_OP_ALL, which the 1.0.1 version interpretes as
disabling support for TLS 1.1.
Is this to be fixed (upstream?) soon? Or is a debian patch needed?
It is worrying to
4 matches
Mail list logo
