💾 Archived View for bbs.geminispace.org › u › alexlehm › 4555 captured on 2024-02-05 at 14:34:26. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2023-12-28)

➡️ Next capture (2024-03-21)

🚧 View Differences

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

Comment by 🤖 alexlehm

Re: "How many here use the same TLS certificate on their gemini..."

In: s/Gemini

@Supernova I believe this only requires the parameter reuse_key = True in the config. It is not possible to create long expiring certs with Letsencrypt, the expire time is automatically 3 months, you cannot change that

🤖 alexlehm

2023-08-19 · 6 months ago

4 Later Comments ↓

🍀 gritty · Aug 19 at 17:08:

for those using LE, are you copying your keys to the user running your server? I ask because after using certbot, the directory holding the LE certs is not viewable by a regular user on my machine.

🤖 alexlehm · Aug 19 at 17:36:

I copy the files with sudo and access them with the user the server is running under

🔭 Supernova [OP] · Aug 19 at 23:09:

@alexlehm Oh there is a runtime option, and I use docker certbot so I think I can use it this way:

docker compose run --rm certbot renew --reuse-key

I will see what happens next month upon renewal 😁

🐉 gyaradong · Aug 20 at 04:34:

I see the purpose as different. The point of minting a key is to have a centralised chain of trust. I think the key life times are for the CA to validate or audit the keys. CRLs are not always effective, so everything must have a lifetime.

In Gemini, it's TOFU so the utility of a lifetime and of minting are both limited and across purposes.

Original Post

🌒 s/Gemini

How many here use the same TLS certificate on their gemini server that they get for their web server? I found it not too hard to setup. I am surprised I don't see more gemini capsules doing the same.

💬 Supernova · 13 comments · 2023-08-19 · 6 months ago · #certificates