>> If there is to be any more discussion of agent programs, please don't
>> bastardise and clone the ssh-agent design -- as it does not apply to
>> passwords very well at all. I suspect if someone *really* has some
>> requirement to keep plaintext passwords off-disk, then password
>> authentication will be unsuitable for their environment in the first
>> place.
>
>
> So what's the alternative? Certificates and such usually require a
> passphrase, too -- and if they don't, they're quite as insecure as
> passwords.
Probable long term solution?:
Create a new authentication module for Apache. This module could be a
modified version of mod_digest, which would return a "session token"
with successful logins. It would store these session tokens (along with
an expiration date) in the server. Future client request should send the
session token, the module would look-up it in its cache and voila! The
client would store the session token, which is much more secure: The
token it's only useful for subversion (important when svn is configured
to use passwords from some common source). The token expires in a day or
two, minimizing the damage. Of course, this just means moving the
credential storage from the client to the server.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jan 9 22:34:10 2005