If this matches what you see on your screen, then you are really connected to us and you can press p to accept the certificate permanently.
Subversion will now remember our certificate and your connections will be secured.
It's recommended to replace the default self-signed certificate for a certificate signed by trusted Certificate Authority (domain or third-party). If you wish to obtain certificate from your corporate Active Directory Certificate Services, contact your system administrator or follow the instructions provided in the article below: How to sign server certificate with Active Directory Certificate Services Generally speaking, it's not recommended to use self-signed SSL certificates in production.
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.
Finally, edit the Global section to add the full path to the Entrust certificate in PEM form.
A full explanation can be found here in the Subversion HTTPD guide.
Some people like to have the authentication data deleted when they log off Windows, or on shutdown.
I just updated the certificate on one of my sites due to the old one expiring.
Accept permanently | Accept once | Reject to be related to Tortoise SVN and not the certificate, which checks out fine at Web and I would say that the cause of the error you list above is because the Entrust certificate is simply not listed in the SSL certificates that Tortoise SVN will trust.
It is possible to configure your Subversion client to ignore such warnings, but I don't think that is a very good idea.
However, since you say that your Entrust certificate checks out fine, then you can configure your svn client to accept the Entrust cert.