On Sat, Mar 24, 2012 at 07:45:51PM +0100, Bastian Kleineidam wrote: > Hello Kurt, > > Am Saturday, 24. March 2012, 12:39:03 schrieb Kurt Roeckx: > > And forcing an SSL3 or TLS1 connection using s_client also works. > Can I configure this somehow to be the default for all applications > using libssl?
Not that I know, as far as I know they all need to set this up themself. > > On the other hand "gnutls-cli sourceforge.net" does work as > > expected. > Yes, there are some gnutls alternatives. Unfortunately the Perl and > Python https libraries are using libssl. In fact that is when I first > noticed the bug: my custom python script could not login to Sourceforge > anymore. > > > So I think someone at sourceforge will have to take a look at this. > This upstream bug seems to be the same problem: > http://rt.openssl.org/Ticket/Display.html?id=2771&user=guest&pass=guest > Unfortunately the developer does not seem to see that as a regression :-/ That bug report mentions owa.mit.edu, which also responds with: Server: BigIP Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
