Client Certificate Bug

20 views
Skip to first unread message

miqro...@gmail.com

unread,
Sep 27, 2018, 11:03:05 AM9/27/18
to TortoiseSVN
If both Basic auth and client certificate auth are enabled in Apache, the repo browser will repeatedly prompt for a certificate file, even after saving a valid username and password.

With such behavior, the certificate auth implementation is somewhat broken and the workaround is to disable it on the server.

TortoiseSVN 1.10.0, Build 28176 - 64 Bit , 2018/04/14 08:00:32

Stefan

unread,
Sep 27, 2018, 12:45:38 PM9/27/18
to TortoiseSVN
if you're using cert files, you have to configure the password yourself:
See the options
ssl-client-cert-file

ssl-client-cert-password

miqro...@gmail.com

unread,
Sep 27, 2018, 12:50:07 PM9/27/18
to TortoiseSVN
On Thursday, September 27, 2018 at 12:45:38 PM UTC-4, Stefan wrote:
> if you're using cert files, you have to configure the password yourself:

My post was not related to encrypted passwords. I'm talking about the client repeatedly asking for a certificate when I am NOT using one.

Stefan

unread,
Sep 27, 2018, 1:33:43 PM9/27/18
to TortoiseSVN
you said "if both Basic auth and client certificate auth are enabled...". So you're asking for a certificate.
And if the client cert auth is configured before basic auth (which it usually is done), then svn will ask you for that certificate.

miqro...@gmail.com

unread,
Sep 27, 2018, 2:02:34 PM9/27/18
to TortoiseSVN
I didn't come here for an argument. Fix it or don't.

Stefan

unread,
Sep 27, 2018, 2:16:45 PM9/27/18
to TortoiseSVN


On Thursday, September 27, 2018 at 8:02:34 PM UTC+2, Robert Chapin wrote:
I didn't come here for an argument.  Fix it or don't.

Well, I can't fix something if you've configured your server wrong.
So did you set up client certificate auth or not?

Also: this place is not for arguments but for help. But to get help, you have to provide answers to questions. If you're not capable of that, then please leave now.

Reply all
Reply to author
Forward
0 new messages