Computer Old Farts Forum
 help / color / mirror / Atom feed
From: arrigo at alchemistowl.org (Arrigo Triulzi)
Subject: [COFF] UUCP on macOS / *BSD
Date: Mon, 29 Jun 2020 19:22:32 +0200	[thread overview]
Message-ID: <384AB182-420D-4014-9141-4B9A72ABD904@alchemistowl.org> (raw)
In-Reply-To: <8dbc09dd-07be-a7ab-082e-edc2e74f0d67@tnetconsulting.net>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2275 bytes --]

On 29 Jun 2020, at 18:43, Grant Taylor via COFF <coff at minnie.tuhs.org> wrote:
> 
> On 6/29/20 9:53 AM, Arrigo Triulzi via COFF wrote:
>> I run UUCP on OpenBSD for some very remote sites connected with satellite modems (using UUCP-over-IP, not pure UUCP, where the dial-up script initiates the UUCP exchange). UUCP was recently removed from the base OpenBSD distribution but is still available as a package.
> 
> Do you by chance recall what UUCP software was being used?  Was it by chance Taylor UUCP?  Or was it some other UUCP package in OpenBSD?

It is indeed Taylor UUCP.

> I did have to enable Set UID & GID on some of the UUCP binaries.  -  I don't know if this is a macOS thing that's broken or if it's a difference in how UUCP operates on BSD or something else I'm ignorant of.

Yes, UUCP binaries do have setuid set, even on OpenBSD. Indeed, in the interest of removing setuid binaries, UUCP was completely removed from base OpenBSD and moved to packages.

> Currently, it seems like UUCP is largely working, save for the fact that users other than _uucp (yes, including the leading underscore) can't access the SSH key file that's used as part of the pipe transport.

The key file won't normally work if permissions are more permissive than 0600 so that is not surprising. Is it doing tunnelling between two ports, i.e. using -L etc.? I'm assuming you are then using uucpd on the remote end listening on the appropriate, forwarded, port which would suggest that you don't need UUCP to setup the connection as long as it has access to the local forwarded port?

> I should document what I'm doing, both as notes for my self (self serving) and for others (good of the community).

Also for debugging purposes, i.e. showing us so that we can see the issues you discuss :)

>> Are you trying to configure dial-up UUCP or UUCP-over-IP with uucpd?
> 
> I'm trying to configure UUCP-over-SSH.  It's probably closer to UUCP-over-modem than it is UUCP-over-IP (TCP).  The ""modem pipe is the ssh command which remotely connects to the destination host (using keys to authenticate) and launching uucico through the SSH connection STDIO.

Right, never did that in my life… I set things up when (open)SSH was v1.2 and port forwarding not quite there yet.

Arrigo 





  parent reply	other threads:[~2020-06-29 17:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29  0:50 gtaylor
2020-06-29 15:37 ` lm
2020-06-29 16:13   ` gtaylor
2020-07-05  6:30   ` dave
2020-06-29 15:53 ` arrigo
2020-06-29 16:42   ` gtaylor
2020-06-29 17:20     ` clemc
2020-06-29 20:06       ` gtaylor
2020-06-29 20:59         ` clemc
2020-06-30  2:26         ` rtomek
2020-06-30  3:19           ` gtaylor
2020-06-30  3:26             ` rtomek
2020-06-30  3:46               ` rtomek
2020-06-30  3:50                 ` gtaylor
2020-06-30  3:47               ` gtaylor
2020-06-29 17:22     ` arrigo [this message]
2020-06-29 20:18       ` gtaylor
2020-06-29 20:31         ` gtaylor
2020-07-01 17:32 ` gtaylor

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=384AB182-420D-4014-9141-4B9A72ABD904@alchemistowl.org \
    --to=coff@minnie.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).