Although the fifth question is not part of the SSL protocol, directory servers can be configured to support this requirement to take advantage of the user entry in an LDAP directory as part of the authentication process.

This used to work before, but maybe the server has been changed.

However, if the certificate is not trusted subversion will ask you whether you trust the certificate and if you want to add this certifacte.

I attempted debugging a bit and the certificate validation is failing in cert.go, line 205 Invalid certs detected; regenerating for 192.76 Copying certs to the local machine directory... Setting Docker configuration on the remote daemon... I built #2006 and copied and to the Docker Toolbox installation directory. If you have time to update the output you get, that'd be just great. Here's the new output: https://gist.github.com/carolynvs/84cd140bcbf9b696e20f. Let me know if there's another way to go about debugging the connection problem.

I'm not quite sure what docker-machine is detecting that is causing it to regenerate the certs but am happy to poke around in /var/lib/boot2docker on the host or compare certs between windows and the host, etc if I knew what to look for. I'm guessing that the issue lies with the certs not matching, which prevents docker-machine from securely connecting to the docker daemon, thus triggering a cert regen?

svn info https://svn.codespot.com/a/eclipselabs.org/xtext-utils/subprojects/unittesting/branches Error validating server certificate for 'https://svn.codespot.com:443': - The certificate is not issued by a trusted authority.

Use the fingerprint to validate the certificate manually!

You probably already had to do this to install the certificate on the Subversion server itself.

However, if you can access the Subversion server without a certificate inside your network, you can also use the tunneling options of SVN:: Notify:: Mirror:: SSH instead.

I do not know if the problem is due to the PR or is present on master.