Thanks for the reply, I have a follow-up question:
Assume the developer used svn+ssh:// to check out
sources.
When she wants to commit the changes, will she have to
use the "--username" argument, or does svn remember
that the checkout was done remotely, and use the cache
/ prompt her for a password (allowing her to omit the
annoying --username argument)?
Thanks,
WJ
--- Max Bowsher <maxb@ukf.net> wrote:
> W J wrote:
> > Hi,
> > Is there a way to store the passwords configured
> in
> > the password file (pointed to by password-db) in
> > non-cleartext form?
> > I realize that obscurity is not security, but in
> my
> > case, our development is based on trust, so I am
> not
> > worried about security at all. We need some way of
> > authenticating users (to know who made each change
> to
> > the sources), and I want to avoid seeing the other
> > users' password in plaintext.
>
> This is not currently possible with plain svn://
> access.
>
> Yes, it probably ought to be.
>
> For now, the available workarounds are:
>
> Use svn+ssh://
> Use http[s]://
>
> Max.
>
>
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 25 17:08:06 2004