💾 Archived View for bbs.geminispace.org › u › jdcard › 13010 captured on 2024-03-21 at 21:25:51. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2024-02-05)

➡️ Next capture (2024-05-10)

🚧 View Differences

-=-=-=-=-=-=-

Apparently my tinkering on the server today caused agate to generate a new security certificate for jdcard.com. Since I hadn't backed up the old certificate I have no way to restore it.

👤 jdcard

2023-12-25 · 3 months ago · 🙁 1

2 Comments ↓

🚀 ran-ford · Dec 25 at 21:54:

This is one of the unfortunate things with Public / Private key based system, if you delete it or loose control you get screwed.

I recommend two things: 1) do backups 2) Use a third way to autheticate yourself like PGP in which you can sign a message with the new certificate in case you need to change it.

🐙 norayr · Dec 26 at 02:02:

i think we can do better in geminispace. even curl author mentioned among gemini problems, that it teaches people to agree, whenever cert is untrusted.

so one way is to use ca issued certs.

that is good, not bad.

another way to not eve depend on ca is 'web of trust'. i think we can adopt it in geminispace and our browsers.