In the above example output I changed various private information to all capital letters to represent what was there including HTTPS-SVN-REPOSITORY-URL-HERE, THE-USERNAME-HERE, THE-PASSWORD-HERE, USERNAME-HERE, and the path to where the repository was being cloned.
In the output after the command was issued again the SVN URL is removed as well as the URL the SSL certificate was based upon.
However, I am running Redmine over Apache, and Apache runs as www-data. Use the fingerprint to validate the certificate manually!
Certificate information: - Hostname: - Valid: from Tue, GMT until Thu, GMT - Issuer: (c)2002 Comodo Limited, Terms and Conditions of use: Comodo Trust Network, Comodo Limited, GB - Fingerprint: 62:ab:bf:b:cd:f3:1e::2d:51:b2:da:a5:e5:e:8e:5f (R)eject, accept (t)emporarily or accept (p)ermanently?
When attempting to sync a repo to a server or to your desktop you will receive an error if the certificate being used to protect the HTTPS repository URL is not issued by the proper authority.
Many companies generate their own certificates for repository URL’s especially if the repository is primary used internally.
This ensures reasonable protection from eavesdroppers and man-in-the-middle attacks, provided that adequate cipher suites are used and that the server certificate is verified and trusted.Visual SVN Server supports secure connection over the HTTPS protocol (Hypertext Transfer Protocol Secure).This protocol is a combination of the Hypertext Transfer Protocol with the SSL/TLS protocol to provide encryption and secure identification of the server.The message from svn will look similar to the following: Be sure to enter 'p' to permanently accept the new certificate.You will need to enter a valid SVN password using either your SVN CESM developers password or the CESM public access password associated with the 'guestuser' accountthat you received upon successful completion of the CESM registration form.How does Redmine/www-data no to look for SVN config settings in the Redmine root directory? I'm running into this same problem when I run the script as www-data (apache2 on Ubuntu 8.04 with a self-signed SSL key). Lo and behold, running the script under root user succeeds, while running as www-data fails.