Hi guys,
just in case anyone is interested, I renewed the SSL certificate on uvena.de/geany.org. The old one was about to expire at the end of June. The certificate is used on some Geany related sites like the mailing list sites, the wiki and others.
The new SHA1 fingerprint is:
89:6A:7B:42:79:15:4F:EF:6A:DF:27:54:36:E2:39:B3:2F:25:03:0E
Regards, Enrico
2011/6/4 Enrico Tröger enrico.troeger@uvena.de:
Hi guys,
just in case anyone is interested, I renewed the SSL certificate on uvena.de/geany.org. The old one was about to expire at the end of June. The certificate is used on some Geany related sites like the mailing list sites, the wiki and others.
The new SHA1 fingerprint is:
89:6A:7B:42:79:15:4F:EF:6A:DF:27:54:36:E2:39:B3:2F:25:03:0E
Regards, Enrico
Would that explain why Firefox has been objecting to anything on the sites with https?
Error message is:
The certificate is not trusted because the issuer certificate is unknown.
(Error code: sec_error_unknown_issuer)
Cheers Lex
On Sat, 4 Jun 2011 19:25:33 +1000 Lex Trotman elextr@gmail.com wrote:
2011/6/4 Enrico Tröger enrico.troeger@uvena.de:
Hi guys,
just in case anyone is interested, I renewed the SSL certificate on uvena.de/geany.org. The old one was about to expire at the end of June. The certificate is used on some Geany related sites like the mailing list sites, the wiki and others.
The new SHA1 fingerprint is:
89:6A:7B:42:79:15:4F:EF:6A:DF:27:54:36:E2:39:B3:2F:25:03:0E
Regards, Enrico
Would that explain why Firefox has been objecting to anything on the sites with https?
Error message is:
The certificate is not trusted because the issuer certificate is unknown.
(Error code: sec_error_unknown_issuer)
No, this is most likely due the still missing CACert root certificate in Firefox, whereas a bunch of well..... questionable certs are inside....
Cheers, Frank
On Sat, 4 Jun 2011 19:58:32 +1000 Lex Trotman elextr@gmail.com wrote:
No, this is most likely due the still missing CACert root certificate in Firefox, whereas a bunch of well..... questionable certs are inside....
Thanks Frank, importing cacert root and intermediate certificates fixes it.
Did you check, whether its really the root of CACert? *scnr* This is something I'm wondering since a couple of years now. Comodo and friends are still in, but CACert has no chance.
Cheers, Frank
Did you check, whether its really the root of CACert? *scnr*
Did I say I was leaving them there, I just said it fixed it, thus identifying the problem :-)
This is something I'm wondering since a couple of years now. Comodo and friends are still in, but CACert has no chance.
Yeah, I've read various things on the processes of CAcert, but I don't know. Who are Verisign for that matter :-)
Cheers Lex