-- Leo's gemini proxy
-- Connecting to git.thebackupbox.net:1965...
-- Connected
-- Sending request
-- Meta line: 20 text/gemini
repo: gemini-spec action: commit revision: path_from: revision_from: eff8c03cc15a35d3b1cf1bf0f5aebff783df58df: path_to: revision_to:
commit eff8c03cc15a35d3b1cf1bf0f5aebff783df58df Author: Sean Conner <spc@conman.org> Date: Wed Apr 7 22:22:47 2021 -0400 Rework paragraph about TLS 1.2 vs. 1.3. diff --git a/specification.gmi b/specification.gmi
--- a/specification.gmi +++ b/specification.gmi @@ -48,13 +48,12 @@ follow the best practice guide for the Gemini protocol. # The use of TLS -The use of an existing TLS library SHOULD be used, but because not all -existing TLS libraries support TLS 1.3, then at this time (2021), -implementations MUST support TLS version 1.2 or higher. Implementations -MUST support TLS SNI (Server Name Indication), and servers MUST use the TLS -close_notify implementation to close the connection. Clients SHOULD NOT -close a connection by default, but MAY in case the content exceeds -constraints set by the user. +At the time of writing (2021), not all existing TLS libraries support TLS +1.3, but a majority (all?) do support TLS 1.2, thus TLS 1.2 is the minimum +required version. Implementations MUST support TLS SNI (Server Name +Indication), and servers MUST use the TLS close_notify implementation to +close the connection. Clients SHOULD NOT close a connection by default, but +MAY in case the content exceeds constraints set by the user. ## TLS Server certificates
-----END OF PAGE-----
-- Response ended
-- Page fetched on Sun Jun 2 14:15:54 2024