Bug#336373: workaround

2006-01-06 Thread Jim Paris
Sorry for all the spam.. This is definitely the openssl bug. It appears that the fix in subversion 1.2.3dfsg1-3 only postponed the problem until libneon24 upgraded to openssl 0.9.8. I found that a workaround is to limit the ciphers on the Apache end. Removing all SSLv3 ciphers except RC4 seems

Bug#336373: workaround

2006-01-06 Thread Peter Samuelson
[Jim Paris] This is definitely the openssl bug. It appears that the fix in subversion 1.2.3dfsg1-3 only postponed the problem until libneon24 upgraded to openssl 0.9.8. That seems unlikely since libneon24 in unstable uses openssl 0.9.8. ...E, wait, are you saying openssl 0.9.7 has the

Bug#336373: workaround

2006-01-06 Thread Jim Paris
This is definitely the openssl bug. It appears that the fix in subversion 1.2.3dfsg1-3 only postponed the problem until libneon24 upgraded to openssl 0.9.8. That seems unlikely since libneon24 in unstable uses openssl 0.9.8. ...E, wait, are you saying openssl 0.9.7 has the bug, or

Bug#336373: workaround

2006-01-06 Thread Peter Samuelson
[Peter Samuelson] That seems unlikely since libneon24 in unstable uses openssl 0.9.8. ...E, wait, are you saying openssl 0.9.7 has the bug, or 0.9.8? Never mind. Having read #338006, all is clear now. Thanks again for the information. Peter signature.asc Description: Digital signature