Ssh error validating server certificate
The Open SSL library does this by examining the signer of the server certificate, or certifying authority (CA).If Open SSL is unable to automatically trust the CA, or if some other problem occurs (such as an expired certificate or hostname mismatch), the Subversion command-line client will ask you whether you want to trust the server certificate anyway.Certificate information: - Hostname: *.- Valid: from Wed, GMT until Thu, GMT - Issuer: Geo Trust, Inc., US - Fingerprint: ea:cb:3f:f3:e6:0c::0c::1f:5c:b3:df:5b::4c (R)eject, accept (t)emporarily or accept (p)ermanently?I managed to setup a SVN (over SSL) server and Tortoise SVN client on Win. The Post-Commit will update the web dir so the App in PHP can be executed with the newest version. The only problem is, when i commit the changes over the client in Win the change is commited but HOOK throws error post-commit hook failed (exit code 1) with output: Error validating server certificate for 'https://SERVER_IP:443': - The certificate is not issued by a trusted authority.
Remember that on Windows, each user can have completely independent security settings, etc., so the only way to validate this fully is to attempt to perform any testing as the remote user that is performing the update, not as yourself.
In addition, certificate authentication is more convenient because no local database of user public keys is required on the server.
It is also easy to deny a user's access to the system by revoking his or her certificate, although this does not take effect until the next CRL update and requires that every other authentication method has been disabled.
This dialogue should look familiar; it's essentially the same question you've probably seen coming from your web browser (which is just another HTTP client like Subversion).
If you choose the (p)ermanent option, the server certificate will be cached in your private run-time auth/ area in just the same way your username and password are cached (see the section called “Client Credentials Caching”).
The signature created with the private key and the verification of the signature using the public key (contained in the X.509 certificate when doing certificate authentication) are done identically with both conventional public keys and certificates.