Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

macos cant update

See original GitHub issue

VSCode Version:1.37.0
OS Version:macos 10.14.6
Extension Version:1.54.4
System Language:Simplified Chinese
SVN Version:1.12.2

Issue

Unable to update

Steps to Reproduce

I checkout my repository use cornerstone 4.1,I can update use cornerstone
I open a trunk dir use vscode
I can look the changes use plugin

SVN Output

Using svn "1.12.2" from "/usr/local/bin/svn"
[20190812_xiaoben]$ svn info --xml
[20190812_xiaoben]$ svn stat --xml --no-ignore --ignore-externals --show-updates
[20190812_xiaoben]$ svn: E170013: Unable to connect to a repository at URL 'https://hezhongfengg@124.235.224.202/svn/icar/00-ProcedureLibrary/01-SourceCode/h5/vfac/branches/20190812_xiaoben'
[20190812_xiaoben]$ svn: E230001: Server SSL certificate verification failed: certificate issued for a different hostname, issuer is not trusted

Screenshots

Issue Analytics

State:
Created 4 years ago
Comments:6 (2 by maintainers)

Top GitHub Comments

1reaction

hezhongfengcommented, Aug 26, 2019

i use svn lsand p

0reactions

4x10mcommented, Jul 1, 2021

Hi there, Just to inform you that sometimes, the permanent option is not available.

I spent a long time investigate this issue and what are the possibilities outside of vscode because its tedious to press t every times for big updates. So for me the best solution to bypass that is the following alias: alias svn="svn --non-interactive --trust-server-cert --trust-server-cert-failures=\"unknown-ca,cn-mismatch,expired,not-yet-valid,other\""

❯ svn ls
Erreur de validation du certificat du serveur pour '...' :
 - Le nom d'hôte du certificat ne correspond pas.
 - Le certificat a expiré.
 - Le certificat conduit à une erreur inconnue.
Informations du certificat :
 - nom d'hôte : ...
 - valide de Aug 27 14:05:48 2010 GMT à Aug 24 14:05:48 2020 GMT
 - signataire : ...
 - empreinte : ...
(R)ejet, ou acceptation (t)emporaire ? p
svn: E170013: Unable to connect to a repository at URL '...'
svn: E230001: Server SSL certificate verification failed: certificate has expired, certificate issued for a different hostname, and other reason(s)

May you can do something for that ? May be add an option which spitulate that this may produce security holes ?

Thks

PS: just to be complete, if i remember right, an other solution to bypass certificate check is by modifying repository proposet but I didn’t succeed to make it working, also I didn’t succeed to put the “trust-server-cert-failures” param in the .subversion/servers file.