On 12/25/2010 12:44, Greywolf wrote:
> On 11/8/2010 08:02, Phillip Merensky wrote:
>> Hello guys.
>> It took me quite a long time to figure out that the ssl handshake
>> errors I get when I connect to my svn server, relate to the linkage of
>> TortoiseSVN 1.6.11 against neon 0.29.4. TortoiseSVN 1.6.10 which is
>> linked against neon 0.29.3 works flawlessly and so does the nightly
>> build of the 1.6. which also links against neon 0.29.3.
>> Further details of the issue can be found here
>> The neon bug seems to be fixed in neon 0.29.5
>> (http://www.webdav.org/neon/ "Fix GnuTLS handshakes failures with 'TLS
>> warning alert' (Bryan Cain)").
> Hi. Just got bit by this bug. It is NOT an svn bug as my svn on my UNIX
> hosts work fine thru SSL. I can read thru SSL on my Win box. I can not
> commit on my Win box, and I am finding this most distressing.
> Is this the same issue, or is this a different bug?
Sorry,I didn't include relevant items:
OS: NetBSD 5.1
ap22-subversion: 1.6.13 webdav apache module
SSLeay perl OpenSSL glue 0.58 and 1.36
OS: Win 7 Ultimate 64-bit
[and all that goes with it including
[mind you, the discrepancy in OpenSSL vs. SSLeay has not hitherto
presented an issue. My available neon is 0.29.3, I wonder if it's a
backrev-incompatibility issue with the server being lesser than the client.]
Going back to 1.6.10 to see if that helps [don't know why it would...]
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-12-26 21:08:49 CET