Re: Molly Brown and Yggdrasil

Message headers

From: meff <email@example.com>

Subject: Re: Molly Brown and Yggdrasil

Date: Wed, 9 Feb 2022 21:16:14 -0000 (UTC)

Message-ID: <su1aut$k76$1@dont-email.me>

On 2022-02-09, Martin <martin@datapulp.de> wrote:

Loading gemini://[209:dead:1cc2:970:637b:450f:6575:9a24]/~/rtr/...

╔═════════════════════ URL Fetch Error ═════════════════════╗

║ ║

║ Failed to connect to the server: hostname does not ║

║ verify: x509: certificate relies on legacy Common Name ║

║ field, use SANs instead. ║

║ ║

║ Ok ║

║ ║

╚═══════════════════════════════════════════════════════════╝

This means that the cert should use a SAN and not a CN, but may be

indicative of a different error underneath.

I'm using amfora. I made my certificate this way, would the CN be ok in

your eyes? How did you do it? Which browser do you use?

openssl req -x509 -newkey rsa:4096 -days 36500 -nodes \

-keyout yggdrasil.key -out yggdrasil.crt -subj \

"/CN=201:112e:4d49:1af1:9190:6da8:bf38:aa9d"

But: THIS IS THE WRONG WAY

Interesting, did you try this method to create the cert and it didn't

work?

- meff

Parent:

Start of thread:

Children: