Error validating server certificate for subversion


11-Oct-2017 09:06

At the time of writing, Apache 1.3 is by far the most popular version of Apache.

The world has been somewhat slow to upgrade to the Apache 2.

In order to work over the HTTPS protocol, the Visual SVN Server should be equipped with an SSL certificate.

A server certificate contains detailed identification information, such as the name of the organization that is affiliated with the server content, the name of the organization that issued the certificate, the name of the server and so on.

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?

This protocol takes the ubiquitous HTTP protocol that is the core of the World Wide Web, and adds writing–specifically, versioned writing–capabilities. Much of the following discussion includes references to Apache configuration directives.

The main idea of HTTPS is to create a secure channel over an insecure network.

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.

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.

I also experience a problem accessing log/when I run the script, even though everything in the redmine tree is owned by www-data and in the www-data group, and the log files are all chmod 0666. Don't know exactly why, but if this is the case, it appears to be a permissions issue. I did all the steps described above and it didn't help in any way.Use the fingerprint to validate the certificate manually!