[PATCH] storing auth after auth failure
From: Philip Martin <philip_at_codematters.co.uk>
Date: 2005-08-12 05:10:34 CEST
Philip Martin <philip@codematters.co.uk> writes:
> Branko Èibej <brane@xbc.nu> writes:
I stepped through trunk client aginst tsvn server:
a) the client calls svn_ra_dav__lock
b) svn_ra_dav__lock calls shim_svn_ra_dav__lock
c) shim_svn_ra_dav__lock calls svn_ra_dav__get_baseline_info which
d) shim_svn_ra_dav__lock calls ne_lock which prompts for auth three
e) the ne_lock call fails and returns 1 (or NE_ERROR)
f) shim_svn_ra_dav__lock calls svn_ra_dav__convert_error which
g) shim_svn_ra_dav__lock returns to svn_ra_dav__lock
h) svn_ra_dav__lock
i) svn_auth_save_credentials retieves a NULL provider and then SEGVs
I don't really understand the auth stuff, but I think the fact that
1) the ra_dav code does not recognise the error as an auth failure
2) the auth code crashes when asked to store auth after an auth
I don't know whether, or how, we should fix (1) but I can fix (2)
Index: subversion/libsvn_subr/auth.c
and then the client gives me
$ svn lock wc/Doxyfile --username guest
I don't know whether it's sensible to silently do nothing when storing
-- Philip Martin --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org For additional commands, e-mail: dev-help@subversion.tigris.orgReceived on Fri Aug 12 05:11:53 2005 |
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.