Now I'm just back to the subversion balking at the invalid certificate issue. The prompt from the svn binary is there to make sure you really really know that this cert is not a proper one.
The proposed fix is not that hard to do, another fix (for some) would be to use a I totally agree on the manual validation of unofficial SSL certificates.
But there is no repo browsing available; after clicking on a stored document I get an error saying that "object or version was not found in repository"; there is also no automatic update of changesets.
I must do manual updates by runnig the above script.
Yes, when I login as my own user, I can do a SVN co and accept the certificate permenently. BTW - I am running the Redmin 1586 on Ubuntu Hardy. Error validating server certificate for 'https://wush.net:443': - The certificate is not issued by a trusted authority.
Certificate information: - Hostname: *- Valid: from Mon, GMT until Fri, GMT - Issuer: Digi Cert Inc, US - Fingerprint: 3f:97:e9:1f:5c:3e:a9:fb:86:5d:4e:ed:6c:9a:1f:63:a4:f:0a (R)eject, accept (t)emporarily or accept (p)ermanently? This doesn't sound like a Terminal problem, but a subversion and/or permissions problem.Error validating server certificate for 'https://...': - The certificate is not issued by a trusted authority.Use the fingerprint to validate the certificate manually! - Valid: from Wed, GMT until Thu, GMT - Issuer: ... Affected Releases CESM1.0.z Affected Releases CESM1.1.z Affected Releases CESM1.2.z Affected Development tags CESM2.0.z CESM SVN inputdata repository The NCAR Subversion servers which host the CESM code and input data repositories will havetheir SSL Security Certificates updated on Wednesday, 2016-12-14.This update will require usersto permanently accept the new certificate from their local machine login when downloadingany code or data from the NCAR SVN server.