git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[BUG] git svn geotrust certificate problem

From
IHIlya Holinov <holinov@netvoxlab.ru>
Date
Jul 5, 2013, 15:16 UTC
Message-ID
<CAOfgeSaRmqRj3gCGy0q9ehr=znzyPONa-Ze03hTo69QLHMuQjA@mail.gmail.com>

I have svn repository on https singed with GeoTrust issued certificate. Every time i try to access this repository i have message :

$ git svn rebase
Error validating server certificate for 'https://svn.egspace.ru:443':
 - The certificate is not issued by a trusted authority. Use the
   fingerprint to validate the certificate manually!
Certificate information:
 - Hostname: *.egspace.ru
 - Valid: from Apr 28 01:38:17 2013 GMT until Apr 30 12:00:40 2014 GMT
 - Issuer: GeoTrust, Inc., US
 - Fingerprint: b2:8d:f8:3b:7c:d2:a2:36:e2:1d:c3:5c:56:ec:87:6f:22:3e:4b:a8
Certificate problem.
(R)eject, accept (t)emporarily or accept (p)ermanently? p
Authentication realm: <https://svn.egspace.ru:443> VisualSVN Server
Username: holinov
Password for 'holinov':

Even if i choose permanently every next attempt to access in i have same issue. And this happens on svn rebase on every commit. I mean if i have 10 commits in local repository i will be asked about cert and user login\passwor for every one of them (and that's is verry annoying). But if i use TortoiseSVN i have no problem with checking that cert.

P.S.: I'm using Windows 8 x64. P.P.S: I like git very much but in this case it makes me impossible to work in this way.

Next: Fredrik Gustafsson
Message 1 of 3 in “[BUG] git svn geotrust certificate problem”
  1. Ilya HolinovJul 5, 2013
  2. Fredrik GustafssonJul 8, 2013
  3. Ilya HolinovJul 9, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.