YjELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLĮxZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQLEzEoYykgMjAwNiBWZXJp MIIE0zCCA7ugAwIBAgIQGNrRniZ96LtKIVjNzGs7SjANBgkqhkiG9w0BAQUFADCB It goes:ġ: Verify that the file /etc/ssl/certs/b204d74a.0 is not thereĢ: Comment in the line mozilla/VeriSign_Class_3_Public_Primary_Certification_Authority_-_G5.crt in the file /etc/nfģ: Create a file called /usr/share/ca-certificates/mozilla/VeriSign_Class_3_Public_Primary_Certification_Authority_-_G5.crt that contains this certificate block: -BEGIN CERTIFICATE. Ok, I have a procedure that works, but for all I know could leave one susceptible to security issues. For now all I can do is leave this info in the hands of the more experienced.
If I were comfortable enough with certificates to talk authoritatively on the topic, I would post instructions. I have found a couple other communities that have had the same problem and report that they have solved it by replacing an untrusted certificate. I can't post a "comment," but this is not an "answer" per se.
0 kommentar(er)
