Re: [PATCH] default to --no-auth-cache

Justin Erenkrantz <jerenkrantz@apache.org> writes:
> --On Monday, January 13, 2003 14:06:48 -0600 "B. W. Fitzpatrick"
> <fitz@red-bean.com> wrote:
>
> > I'd like to +1 this patch. If we don't switch the password caching
> > behavior to off by default, we're going to wind up getting a BUGTRAQ
> > nastygram, a truckload of bad press, and then have to turn it off by
> > default anyway.
>
> Sorry, but I disagree. CVS stores its passwords in ~/.cvspass using simple
> base-64 encoding. This is no less of a security hole than it was in CVS.
> The only difference is that it is stored in the working copy, not in your
> home directory. Perhaps we should move the passwords to being in your
> ~/.subversion directory. (Although I think there are reasons not to move
> it there though.)

I'd feel a little better having it in ~/.subversion, but until svn
puts it there, I'd say disable storing it in the working copy.
 
> If you use ra_svn with SSH tunneling, you have the same effect as CVS with
> SSH tunneling - no passwords are stored locally.

Sure, but everyone knows that pserver is easily sniffable--ra_dav can
run over ssl, which most people consider to be safe and secure.
 
> I believe that this change is only going to result in frustrated
> users and make it harder to use SVN out of the box.

I don't think it's all that bad.

> Everyone *wants* password caching - security risk or not. -- justin

Well, there I'll agree with you.

:)

-Fitz

--
Brian W. Fitzpatrick    <fitz_at_red-bean.com>   http://www.red-bean.com/fitz/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org