eal @eal@cybre.space

@Azurolu pls

test :kokko:

test 🐻

test :tenshi_eating_corndog:

@hugo "According to the standard, certificates must be presented in the order in which they are needed. The main, server, certificate must come first, followed by the certificate that signed it, followed by the next certificate in the chain, and so on. A small number of sites does not get this order right. Most SSL clients will deal with this problem silently, but there is a small number of platforms that will give up."

@hugo also, prime256v1 didn't fix it either.

@hugo I'm fairly sure since the same issue happened with an other instance with incorrect chain order.

@hugo masto.host TLS seems to be setup wrong (incorrect chain order, extra certs, contains anchor). This means that I can't reach *.masto.host users you from my instance social.sakamoto.gq, as the Elixir TLS library returns an error on handshake. Could you fix these issues?

See here: https://www.ssllabs.com/ssltest/analyze.html?d=esperanto.masto.host&s=2001%3a41d0%3a302%3a1100%3a0%3a0%3a1%3a7615&latest

lynx lynx

<cyan
none
>green
none

>blu
<gren

<blue
>green
<from
>masudon