RE: svn+ssh long-lived daemon
From: Bert Huijben <bert_at_qqmail.nl>
Date: Fri, 20 Nov 2015 18:36:16 +0100
But in case of git you have git-ssh like servers implemented as a combination of two tools which avoid these problems. (Sometimes in java though). Perhaps we could also look in that direction instead of looking at a new protocol between svnserve and ssh.
Or checking if ssh style public key authentication could be introduced directly in the svnserve protocol.
Both these options would also fix the problems raised.
Sent from Outlook Mail for Windows 10 phone
From: Mark Phippard
I've always felt the same, but now that I've used SSH more (with Git) I kind of question it.
Are HTTP client certs much better than passwords? The cert itself still has to be physically secured and if you protect the cert with a passphrase then you have all of the same cache problems that passwords do.
With SSH there is infrastructure like ssh-agent that just does not exist for HTTP.
On Fri, Nov 20, 2015 at 9:16 AM, Bert Huijben <bert_at_qqmail.nl> wrote:
From: Philip Martin
-- Philip Martin WANdisco -- Thanks Mark Phippard http://markphip.blogspot.com/Received on 2015-11-20 18:36:34 CET
This is an archived mail posted to the Subversion Dev mailing list.