AW: parse tlsext bug
From: Sebastian Krysmanski <sebastian_at_krysmanski.de>
Date: Wed, 5 Aug 2009 11:27:00 +0200
Hi Joe,
I could file a bug against mod_ssl but I'm not sure what to insert in this report since the problem only seems to appear in Subversion.
Yes, I control the server the problem occurs on. I've reproduced the problem and uploaded the Apache log (level: debug) here: http://files.mayastudios.de/svn-fail.log
The log only contains log entries from Apache's startup and this svn command (nothing else):
> svn merge -r 992:993 https://svn.mayastudios.de/fred/repos/branches/Fred2.0
I can reproduce the problem every time. You can find the exact steps here: https://svn.mayastudios.de/fred/ticket/55#comment:4 However, since I and several other people are using the server I downgraded to Apache 2.2.11 again (with which you can't reproduce the problem). However, I could upgrade to Apache 2.2.12 for a short time so that you could reproduce the problem yourself. Just let me know when you're ready to do so (so that I can keep my server's "downtime" as short as possible). I'm in the SVN IRC chat very often (username is "Manski") so this would be a way to contact me.
Regards
-----Ursprüngliche Nachricht-----
On Mon, Aug 03, 2009 at 08:17:26PM +0200, Sebastian Krysmanski wrote:
httpd 2.2.12 enabled the TLS SNI extension, which is undoubtedly
https://issues.apache.org/bugzilla/enter_bug.cgi?product=Apache%20httpd-2
(it is possible this bug lies anywhere between neon, OpenSSL and
Do you control the server for which this bug can be reproduced? If so
Do you also have a precise set of steps I could follow to reproduce the
Regards, Joe
------------------------------------------------------
|
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.