>From: John Peacock <email@example.com>
>To: Tom Martin <firstname.lastname@example.org>
>Subject: Re: Feature request: Disable ssl prompting in "servers" for better
>Date: Mon, 20 Dec 2004 21:27:29 -0500
>Tom Martin wrote:
>>Authentication itself is a very serious security issue.
>>No serious security manager would rely on proper timeouts and on proper
>>IP routing. There are several possibilities for manipulating this.
>>This is exactly the reason why ssl authentication exists.
>>I am sure you don't want to say that this feature has no reason.
>Yes, but it is the ssh program itself which challenged the user about the
>changed key, not Subversion. I'm not even sure that it is possible at the
>Subversion level to affect this behavior, since ssh is the secure transport
>method and only after the connection is established that svn gets control
All ssl properties are read from the subversion config file "servers".
So subversion seems to evaluate them.
Also the subversion command line client evaluates the no-promt option.
Basically my proposal says that "servers" should get a default value for
Because of this, although not being a professional developer, I am quite
that it would be easy possible in subversion.
>This feature belongs in ssh, not in Subversion.
>In particular, the StrictHostKeyChecking option to .ssh/config seems to be
>exactly what you want:
>Set this to ``yes'' in the .ssh/config file (or if all users are on the
>same system, then the systemwide config file), and you won't have to worry
>about this again.
This is ssh. Is there a corresponding ssl option? This would be perfect!
Express yourself instantly with MSN Messenger! Download today it's FREE!
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Dec 21 03:50:24 2004