Error validating server certificate svn dating site for rich women

25 Mar

-----END CERTIFICATE----- --- Server certificate subject=/OU=Domain Control Validated/CN=*.issuer=/C=US/ST=Arizona/L=Scottsdale/O=Go, Inc./OU= Daddy Secure Certificate Authority - G2 --- No client certificate CA names sent --- SSL handshake has read 4910 bytes and written 468 bytes --- New, TLSv1/SSLv3, Cipher is AES128-SHA Server public key is 2048 bit SSL-Session: Protocol : TLSv1 Cipher : AES128-SHA ...

Verify return code: 19 (self signed certificate in certificate chain) --- I assume that return-code 19 is because of Go Daddy's Class 2 Certification Authority being self-signed.

When disappeared in September, I moved my private repo over to It doesn't give me the option to accept (p)ermanently, like my first few searches indicated it would. Per, I tried to update [global]:ssl-authority-files to include the cert from assembla, and set ssl-trust-default-ca to true. When that didn't work, I dug into the format of the ~/.subversion/auth/server/___ files, figured out how to get the same name and encoding from the SSL certificate into that file, as if I had said "(p)ermanent"...but it still kept on giving that same error and prompt every time.For linux there is a command to get and update keys: Error validating server certificate for 'https://org:443': - The certificate is not issued by a trusted authority.Use the fingerprint to validate the certificate manually!