💾 Archived View for bbs.geminispace.org › u › clseibold › 5320 captured on 2023-12-28 at 17:05:55. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-11-14)
-=-=-=-=-=-=-
Re: "Cert Problems with Amfora and AuraGem"
@mediocregopher Thanks for letting me know. I've decided to just switch out the certificate. This will require all existing users to accept this new certificate, but this new cert should work with all the gemini browsers now.
Sep 14 · 3 months ago
@clseibold Too late now, but if you'd kept the same key for the new certificate then many clients wouldn't have shown a warning.
P.S. Welcome back to gemini!
🚀 clseibold · Sep 15 at 12:01:
@mbays This is guaranteed to work with all clients? Because that would be surprising, honestly, lol
Anyways, yeah, I seen this post on your capsule before, I just forgot about it. If I ever do need to change the cert again, I'll keep it in mind.
Also, thanks! :)
@clseibold Not all, but I tested it as working on amfora, lagrange, and diohsc.
Cert Problems with Amfora and AuraGem — Apparently Amfora verifies certs differently than other clients, so it isn't working for AuraGem. It might have to do with CN vs. the subjectAltName thing in the certificate, but I'm not quite sure. I expect clients to look at *both*, because I use CN for the main address and subjectAltName for alternative domains (hence the "Alt"), but maybe that assumption was wrong, idk. If anyone knows anything about this and how I can fix it, that would be...