Hi,
after upgrading from 1.14.x to TortoiseSVN 1.15.0.29830 (64 bit, svn 1.15.0),
every operation that contacts our svnserve repository crashes (TortoiseProc
"has stopped working"). Downgrading to 1.14.9.29743 x64 (svn 1.14.5) fixes it
immediately.
Environment:
- Windows 11 Pro 10.0.26300, x64
- TortoiseSVN 1.15.0.29830 x64, bundled Cyrus SASL 2.1.28
(SASL SearchPath -> C:\Program Files\TortoiseSVN\bin, no foreign SASL DLLs
on PATH)
- Server: svnserve 1.14.5 with SASL authentication (probably DIGEST-MD5),
reached via svn://
127.0.0.1:3690 through a local stunnel (TLS-PSK) tunnel
- Working copy format 31
The crash also happens with the bundled command line client, so it does not
seem to be GUI related:
svn info svn://
127.0.0.1/<my_repo>
-> process terminates with exit code -1073741819 (0xC0000005,
access violation), no error message
What I found while narrowing it down:
- Wrong password: clean error, no crash
svn: E170001: Authentication error from server: SASL(-13):
authentication failure: client response doesn't match what we generated
- No credentials (fresh --config-dir, --non-interactive): clean error
"Can't get username or password"
- Correct password (cached or typed manually in the GUI, also with an empty
auth cache): crash
- A server that simply drops the connection: clean error E210002
So the crash seems to happen right after a *successful* SASL authentication.
The same setup works fine with TortoiseSVN 1.14.9.
Might this be an issue on our server side, as we are still using 1.14.5?
Best regards,
Leon Nimke