From: "Lyndon Nerenberg (VE7TFX/VE6BBM)" <lyndon@orthanc.ca>
To: Rich Salz <rich.salz@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: seismo/uunet uucp
Date: Tue, 02 Jul 2024 10:16:03 -0700 [thread overview]
Message-ID: <8cf0159b519f1596@orthanc.ca> (raw)
In-Reply-To: <CAFH29tp=_7fH57W0YcbSaXr5pptAQhMR666d0tpsjnZuMSnM8Q@mail.gmail.com>
Rich Salz writes:
> Almost definitely, anything Seismo/UUNET/Rick did would be passed back to
> CSRG.
But did it? I don't remember seeing it in any of the source trees
I was monkeying with. Not that that means much. But I also don't
remember ever seeing a non-gnu UUCP associated with any post-4.2
release. Thus leading back to my original question ...
> You're going to glue TLS to UUCP? You know it's interactive (two way)
> protocol, right?
Yup. It's just wrapping the connection with TLS, ala https vs http.
People have been doing it for decades (e.g. suucp in more tha a few
/etc/services files). With HDB you can arrange this by doing some
contortions in the Dialers file that make it call out to 'openssl
s_client ...' IIRC. It has been a looong time ...
--lyndon
next prev parent reply other threads:[~2024-07-02 17:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 14:26 [TUHS] " Lyndon Nerenberg (VE7TFX/VE6BBM)
2024-07-02 15:05 ` [TUHS] " Clem Cole
2024-07-02 16:00 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2024-07-02 16:32 ` Rich Salz
2024-07-02 17:16 ` Lyndon Nerenberg (VE7TFX/VE6BBM) [this message]
2024-07-02 17:28 ` Grant Taylor via TUHS
2024-07-02 18:05 ` Rich Salz
2024-07-03 20:17 ` Alexander Schreiber
2024-07-02 18:08 ` arnold
2024-07-02 18:56 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2024-07-02 19:14 ` arnold
2024-07-02 21:58 ` Clem Cole
2024-07-03 0:17 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2024-07-03 6:40 ` arnold
2024-07-02 20:15 ` Jeremy C. Reed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8cf0159b519f1596@orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=rich.salz@gmail.com \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).