💾 Archived View for gem.benscraft.info › mailing-list › threads › 189 captured on 2021-12-05 at 23:47:19. Gemini links have been rewritten to link to archived content

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

[spec] The security model for TLS is also discussed inside IETF

- Stephane Bortzmeyer <stephane at sources.org>

@ Sun, 11 Apr 2021 08:40 +0200

In reply to

View Message

────────────────────────────────────────────────────────────────────────────────

This post about TLS

<https://rip-van-webble.blogspot.com/2021/04/quic-elephant-in-room.html>

created a lively discussion inside IETF

<https://mailarchive.ietf.org/arch/msg/ietf/VBAyaRdpqE0UUkIjjSYCXYUer30/>

about the security of TLS: PKI (using CAs and may be CT), DANE, TOFU?

The same sort of issues that Gemini faces

<https://gitlab.com/gemini-specification/protocol/-/issues/5>.

Good to see we are not the only ones questioning the problem and its

solutions :-)

[For the context: the RFCs about the new Internet transport protocol,

QUIC, which will probably take a good market share from TCP, are done

and almost published.]

════════════════════════════════════════════════════════════════════════════════