💾 Archived View for gemini.bunburya.eu › newsgroups › gemini › messages › 87zgn1ckvo.fsf@cassilda.ca… captured on 2023-09-08 at 16:30:04. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2022-04-28)

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

Re: TLS and non-TLS on same port number

Message headers

From: Jason McBrayer <jmcbray@carcosa.net>

Subject: Re: TLS and non-TLS on same port number

Date: Tue, 08 Feb 2022 12:45:47 -0500

Message-ID: <87zgn1ckvo.fsf@cassilda.carcosa.net>

Message content

news@zzo38computer.org.invalid writes:

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.)

To the best of my knowledge, this is not reasonably feasible. Normally,

services where you can run TLS and non-TLS on the same port have some

kind of STARTTLS mechanism, which Gemini lacks. Also, by spec, Gemini is

TLS-only; some people call Gemini-minus-TLS "Mercury" because of a

thought experiment by Solderpunk, but it's not widely deployed, and it's

generally considered that the only use of it is retrocomputing.

All that said... you might look into sslh[1], if you are interested. It

doesn't natively support Gemini or Mercury, but it ought to be possible

to add it. In the dim past, I used it to serve SSH and HTTPS on the same

port.

[1]: https://github.com/yrutschle/sslh

--

Jason McBrayer | “Strange is the night where black stars rise,

jmcbray@carcosa.net | and strange moons circle through the skies,

| but stranger still is lost Carcosa.”

| ― Robert W. Chambers,The King in Yellow

Related

Parent:

TLS and non-TLS on same port number (by news@zzo38computer.org.invalid on Sun, 06 Feb 2022 19:47:30 -0800)