Back in May I discussed it on the users list in a thread entitled:
"Re: Accessing SVN repository via Apache and SSL client certificate?"
Ralph Seichter ended up saying that he thought it was a problem with
neon and that he posted about it on the issues mailing list but got no
reply. Then the thread sort of died.
To rehash it here, the problem is that you can configure apache to
require a client cert for the entire virtual host, in which case, it
prompts the client for a cert during the initial connection handshake.
This works currently. The problem is that if you don't want the entire
virtual host to require a client cert, you can configure apache to only
require one for access to certain resources, and when the client
requests an operation on those resources, then apache will prompt the
client for the cert. When this happens with svn, it barfs.
This is annoying because I don't really want to require a client cert
for non svn areas of the web server, or for read only access to the
repository.
Ben Collins-Sussman wrote:
>
> On Aug 9, 2005, at 9:30 AM, Phillip Susi wrote:
>
>> Has the bug been fixed yet where subversion blows up if apache asks
>> it for a client certificate after the initial connect handshake?
>>
>
> It may be foremost on your mind, but I suspect that most readers of
> this list don't remember this bug. Can you provide a reference? A
> filed issue? Or a link to a mail thread?
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 9 16:59:08 2005