Computer Old Farts Forum
 help / color / mirror / Atom feed
From: gtaylor at tnetconsulting.net (Grant Taylor)
Subject: [COFF] UUCP on macOS / *BSD
Date: Mon, 29 Jun 2020 14:18:02 -0600	[thread overview]
Message-ID: <5059126e-23d2-0e65-11eb-f3a41be84356@tnetconsulting.net> (raw)
In-Reply-To: <384AB182-420D-4014-9141-4B9A72ABD904@alchemistowl.org>

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

On 6/29/20 11:22 AM, Arrigo Triulzi via COFF wrote:
> It is indeed Taylor UUCP.

Cool.  Thank you for the confirmation.

> Yes, UUCP binaries do have setuid set, even on OpenBSD.

That clarifies setuid.  Can the same be said about setgid?

> Indeed, in the interest of removing setuid binaries, UUCP was 
> completely removed from base OpenBSD and moved to packages.

That seems understandable, especially for OpenBSD.

I think many distros are simply removing UUCP as an antiquated package.

> The key file won't normally work if permissions are more permissive 
> than 0600 so that is not surprising.

Agreed.  I also tried it any way and got the expected error from OpenSSH 
saying that it was ignoring the key file with bad permissions.

I was, still am, naively expecting that uucp / uuto / uux are run as 
normal users (not root and not the uucp user) to copy files to the uucp 
queue directory structure, and then something will cause the uucp user 
to initiate the outbound connection as the uucp user.  I think this 
later part is where my understanding breaks down.

> 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?

No.

sys:
system targetHost
call-login targetHost
called-login targetHost
port targetHost

port:
port targetHost
type pipe
command /usr/bin/ssh targetHost.fqdn /usr/sbin/uucico

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

What would you like me to show / share?

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

ACK

I've got this same type of configuration working quite well with 
multiple Linux systems.

macOS mostly works.



-- 
Grant. . . .
unix || die

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4013 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200629/4a474c09/attachment-0001.bin>


  reply	other threads:[~2020-06-29 20:18 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
2020-06-29 20:18       ` gtaylor [this message]
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=5059126e-23d2-0e65-11eb-f3a41be84356@tnetconsulting.net \
    --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).