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
>> http://bugs.gentoo.org/show_bug.cgi?id=340825.
>> 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?

Client:
OS: Win 7 Ultimate 64-bit
TortoiseSVN: 1.6.12
[and all that goes with it including
apr 1.3.8
apr-utils 1.3.9
neon 0.29.5
OpenSSL 0.9.8p
zlib
[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...]