Re: user authentication

Krebs, Steven wrote:
> You could store it in an encrypted file that uses the logged in user's
> Win32 security identifier (SID) as the encryption/decryption key. I
> realize this is not completely secure with open source, but it adds a
> layer of protection. Others may have better ideas...
>
> The problem with plain text in a windows environment is as follows:
>
> Security on Win32 using a domain: Domain Admins are only allowed to
> reset passwords, they cannot see what the current password is (the way
> it should be). I don't want to discuss physical access and crack tools
> here.
>
> With subversion, the passwords are stored in plain text in the user's
> profile area here: C:\Documents and Settings\<username>\Application
> Data\Subversion\auth\... This directory is accessible by the user and
> all *local admins*.
>
> If two users share a system (in my case this would be a shared lab
> system), often both users may be granted local admin access privileges
> on that system (example: for install testing purposes).
>
> Subversion's plain text password files make it easy for anyone with
> local admin access to see what a user's current svn password is. If
> the svn password is synchronized with the user's Win32 domain password,
> it is a BIG security hole (On my team we have different passwords for
> svn to prevent this).

AFAIK, If you use Windows' built in encryption on the folder containing
the password, even an Administrator can't get to them unless logged in
as that user. You just have to make sure that your users log out or
switch users when they are on the machine.

-- 
Brian Mathis
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org