Hi Phil,
first sorry for the delay on answering to this issue.
There some family affairs which keeps me currently busy.
I tested your proposal with a client certificate apache backend.
When I define a /etc/subversion/servers file with these lines:
[groups]
localhost = localhost
[localhost]
ssl-client-cert-file = /etc/ssl/version-management/clientcert.p12
ssl-client-cert-password = ********
[global]
ssl-authority-files = /etc/ssl/version-management/demoCA/cacert.pem
"svn ls" works like expected.
Without these lines "svn ls" ask for certificate file, everytime it is
performed and also when permanently accepting the key.
when using fsvs it also asks for certificate file and it works (which is
very nice) when I manullay input the keypath,
But when using the lines in the servers file globally or in .subversion
it doesn't care about.
Best Regards, Gunnar
Philipp Marek schrieb:
On Monday 07 July 2008 Gunnar Thielebein wrote:
I have seen that this feature already exists in the svn client and can
be controlled via
the following directives in subversion configuration:
ssl-client-cert-file
ssl-client-cert-password
The access to the repository should be authenticated in a host-based way.
...
Using ssh for host-based authentication does not offer the flexibility
of apache2 which we need in this scenario.
Maybe it already works if you get a successfull "svn ls http://..."; and use
the ~root/.subversion on the target machine?
FSVS just invokes the default handler of subversion; but it's possible that
something has to be done specially for certificate based authentication.
(But that would be awfully nice - imagine using a smartcard!)
Could you test that, please?
Regards,
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
