AW: CommitMonitor: Problem with client certificate authentication

Hi Stefan,

thanks for the response.

> Delete the registry keys
> HKCU\TortoiseSVN\CAPIAuthz
> and then try accessing your repo with TSVN. You will most likely get a
> cert selection dialog showing up, and there you can then see that there
> is more than one certificate.
I did that (and re-enabled OpenSSLCAPI), but got the same result:
TSVN just works fine (no dialog at all), CM fails.
Any further advice?

> That feature would require to save a lot of data somewhere. I'm leaning
> against that, because that's also a problem in CM: ending the process
> takes a long time because that data needs to be saved, and that can even
> lead to the process being killed on windows shutdown - and then the data
> is not saved properly...
Yeah, it adds a lot of code complexity for a "little" feature for sure.
I fully understand that from the programmer's point of view.
But from the user's point of view this feature really valuable.
That’s why I would vote for this feature any time :-)

Being an embedded firmware engineer, I am well aware of the challenge
of saving precious data while power can be switched off at any time.
The common solution is to save data as soon as it changes (in the background)
and accept that the very last change might be lost if power drops just that moment.
That’s usually okay, as long as you don’t lose the whole database.
But that’s not done easily, for sure.

Kind regards,

Roland

Pepperl+Fuchs GmbH, Mannheim
Geschaeftsfuehrer/Managing Directors: Dr.-Ing. Gunther Kegel (Vors./CEO), Dr.-Ing. Peter Adolphs, Werner Guthier, Mehmet Hatiboglu
Vorsitzender des Aufsichtsrats/Chairman of the supervisory board: Claus Michael
Registergericht/Register Court: AG Mannheim HRB 4713
-----Ursprüngliche Nachricht-----
Von: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
Gesendet: Freitag, 19. Februar 2016 18:16
An: users_at_tortoisesvn.tigris.org
Betreff: Re: AW: CommitMonitor: Problem with client certificate authentication

On 19.02.2016 16:03, Stahn Roland wrote:
> Hi Stefan,
>
> thank you for pointing me to this registry key.
> With this workaround CM can access the SVN server again, while the client
> certificate is still present within Windows for the web browser. Great!
>
> I can confirm though, that the client certificate is *exactly* the same - at
> least from an user's point of view. I used the very same file, that CM is now
> loading via the 'servers' settings to import the certificate into windows.
> Of course I have no idea, what kind of magic is applied to the certificate
> during this import process. And as stated before, there is no other client
> certificate present, that would explain why TSVN can access the server and
> CM cant.

TSVN uses the same auth code as CM with the only difference that TSVN
can show a cert selection dialog.

Delete the registry keys
HKCU\TortoiseSVN\CAPIAuthz
and then try accessing your repo with TSVN. You will most likely get a
cert selection dialog showing up, and there you can then see that there
is more than one certificate.

> On the long run I plan to switch to TSVN project monitor anyway, as soon as
> it regains CMs ability to manage the 'unread' status of commit messages
> individually. But that’s another story and had been discussed on this list before:
> http://svn.haxx.se/tsvnusers/archive-2015-10/0052.shtml
> Can I vote for this feature somewhere?

That feature would require to save a lot of data somewhere. I'm leaning
against that, because that's also a problem in CM: ending the process
takes a long time because that data needs to be saved, and that can even
lead to the process being killed on windows shutdown - and then the data
is not saved properly...

Stefan

--
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest interface to (Sub)version control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3161760
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Wichtiger Hinweis:
Diese E-Mail einschliesslich ihrer Anhaenge enthaelt vertrauliche und
rechtlich geschuetzte Informationen, die nur fuer den Adressaten bestimmt sind.
Sollten Sie nicht der bezeichnete Adressat sein, so teilen Sie dies bitte dem
Absender umgehend mit und loeschen Sie diese Nachricht und ihre Anhaenge. Die
unbefugte Weitergabe, das Anfertigen von Kopien und jede Veraenderung der E-Mail
ist untersagt. Der Absender haftet nicht fuer Inhalte von veraenderten
E-Mails.
Important Information:
This e-mail message including its attachments contains confidential and legally protected information solely intended for the addressee. If you are not the intended addressee of this message, please contact the addresser immediately and delete this message including its attachments. The unauthorized dissemination, copying and change of this e-mail are strictly forbidden. The addresser shall not be liable for the content of such changed e-mails.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3162309
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].