I asked AI if svn uses or requires a client authentication certificate and the response was "yes" if Apache uses the mod_dav_svn Module
My /etc/httpd/conf.modules/10-subversion.conf file containd the following: LoadModule dav_svn_module modules/mod_dav_svn.so LoadModule authz_svn_module modules/mod_authz_svn.so LoadModule dontdothat_module modules/mod_dontdothat.so Do you thing commenting out the first line would address the issue I am encountering? From: Kevin Lew Sent: Friday, November 20, 2026 8:42 AM To: Pavel Lyalyakin <[email protected]> Cc: [email protected] Subject: RE: Looking for help Pavel, When I downloaded by certificate, it contains these three files (see image below) [cid:[email protected]] I renamed the .crt file to ddci.crt. I renamed the gd_bundle_ov-r1-g2.crt.pem to gd_bundle.crt. And I provide the private key. I am, in fact, using the new chain file, just renamed. I get zero error on the web browser when I update the certificate but svn complains The certificate is not issued by a trusted authority. Use the\n fingerprint to validate the certificate manually!\nCertificate information:\n - And this error does display the correct fingerprint of the new certificate. I called GoDaddy and they told me that this was caused by the removal of the clientauth sku from all certificates issued after 11/15/2026 and that I would need to set up my own client certificate. Have you heard of anyone in the svn community encounter the same issue? Maybe I am the unlucky first person to encounter this. From: Pavel Lyalyakin <[email protected]<mailto:[email protected]>> Sent: Thursday, November 19, 2026 8:24 AM To: Kevin Lew <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Subject: Re: Looking for help You don't often get email from [email protected]<mailto:[email protected]>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Hello Kevin, I don't think the ClientAuth EKU is directly relevant here. Your server certificate on httpd acts as a server certificate and the certificate most likely has the ServerAuth EKU. Moreover, the warning in the SVN client explicitly says "The certificate is not issued by a trusted authority", so I think the root cause is that the client is unable to build a chain from your new server certificate to a root certificate it trusts. I would suggest that you reach out to GoDaddy support for assistance because some knowledge of their CA is needed to advise further. As a wild guess, I think that you might need to choose another SSLCertificateChainFile from https://certs.godaddy.com/repository like a cross-signed 'gd_bundle_dv-r1-g2.crt.pem' which *maybe* will help the client to build certificate trust to a root certificate known/trusted by your client OS. In the article<https://godaddy.com/help/why-is-godaddy-removing-clientauth-eku-and-transitioning-to-the-r1-root-hierarchy-for-dv-tls-issuance-42783>, they say "... we rely on a cross-signed trust path back to the already-trusted G2 root." I don't know exactly which bundle matches your certificate, because that depends on GoDaddy's CA setup. If the suggestion doesn't help, I would contact GoDaddy support for further assistance. Thank you! On Thu, 19 Nov 2026 at 16:49, Kevin Lew <[email protected]<mailto:[email protected]>> wrote: Pavel; Thank you for responding. I did include the Chain File (gd_bundle) when I updated the certificate. SSLCertificateFile /etc/pki/tls/certs/ddci.crt SSLCertificateKeyFile /etc/pki/tls/private/ddci.key SSLCertificateChainFile /etc/pki/tls/certs/gd_bundle.crt Everything web browser is fine. Subversion and subversion related scripts are giving us the error. I believe this is due to the removal of the ClientAuth EKU. This leads me to believe I will need another certificate to make up for this. Do you know of any documentation out there that could guide me setting up a certificate with the ClientAuth EKU? Yes. I am aware we are running a very old version of svn. Unfortunately the upgrade process has been very challenging. We plan on upgrading but need to keep this going until we do. I really appreciate you responding. Thank you. From: Pavel Lyalyakin <[email protected]<mailto:[email protected]>> Sent: Wednesday, November 18, 2026 4:45 PM To: [email protected]<mailto:[email protected]> Cc: Kevin Lew <[email protected]<mailto:[email protected]>> Subject: Re: Looking for help You don't often get email from [email protected]<mailto:[email protected]>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Hello Kevin, Did you update the intermediate certificate file specified in SSLCertificateChainFile in your httpd's config with a new one from GoDaddy? I guess that the client computer's OS simply doesn't trust GoDaddy's new root. AFAIK, GoDaddy began using a new root certificate<https://godaddy.com/help/why-is-godaddy-removing-clientauth-eku-and-transitioning-to-the-r1-root-hierarchy-for-dv-tls-issuance-42783?lc=en-US#:~:text=As%20we%20migrate%20public%20DV%20TLS%20issuance%20to%20the%20R1%20hierarchy%2C%20the%20R1%20root%20is%20still%20in%20the%20process%20of%20being%20broadly%20trusted%2Fdistributed%20in%20browser%20and%20OS%20trust%20stores.> in 2026 and they say that it "... is still in the process of being broadly trusted/distributed in browser and OS trust stores.", which essentially means that the root certificate isn't trusted by default by some OSes and web browsers. GoDaddy has an article on this topic: https://godaddy.com/help/fix-an-untrusted-root-or-certificate-chain-error-42951. The fix they suggest is to install a complete "certificate bundle" rather than the server certificate alone. So in addition to updating the server certificate, you also need to update the certificate file specified in SSLCertificateChainFile in your httpd's config. This will make the server supply the complete certificate chain to clients and will, most likely, resolve the issue. Note that support for SVN 1.7.x ended in 2015, so your server installation is quite outdated. Please plan an upgrade for your SVN server and clients. Thank you. On Thu, 19 Nov 2026 at 00:46, Kevin Lew via users <[email protected]<mailto:[email protected]>> wrote: I know there are changes coming to SSL Certificates and today, I ran into an issue. We have a Redhat Server running svn version 1.7.14. Our GoDaddy certificate was just renewed Nov. 18, 2026. I installed the new certificate, restarted Apache as I've always done. The web server is fine but svn started giving our users an error that The certificate is not issued by a trusted authority. Use the\n fingerprint to validate the certificate manually!\nCertificate information:\n - Rolling back the certificate got svn working again. Does anyone know why this is? I suspect it has to do with server authentication and client authentication no longer being on the same certificate, but I am not sure what needs to be done. Hopefully, there's someone out there in the subversion community who can provide some insight? Thank you -- With best regards, Pavel Lyalyakin VisualSVN Team -- With best regards, Pavel Lyalyakin VisualSVN Team
