💾 Archived View for gemini.bunburya.eu › newsgroups › gemini › messages › 1644180967.bystand@zzo38co… captured on 2023-06-14 at 14:33:44. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2022-04-28)
-=-=-=-=-=-=-
From: news@zzo38computer.org.invalid
Subject: TLS and non-TLS on same port number
Date: Sun, 06 Feb 2022 19:47:30 -0800
Message-ID: <1644180967.bystand@zzo38computer.org>
I would want to make the Gemini service with both TLS and non-TLS with the
same port number, using xinetd and stunnel. Can this be done easily by
using these programs? (I would rather not use a different port number.)
As far as I know, the first byte of the client's message with TLS is not
going to be the same as the request of Gemini, so this should not cause
any ambiguity, but the implementation might not do that.
A environment variable could specify if it is TLS or not and if a client
certificate is available. This will be relevant if a file is requested
that requires a client certificate; this is the only case where TLS vs
non-TLS will be relevant, in which case it must issue a redirect.
--
Don't laugh at the moon when it is day time in France.
Children: