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:31:32 -0600	[thread overview]
Message-ID: <838270a9-c1a0-a3d0-0192-3b2f51f1608c@tnetconsulting.net> (raw)
In-Reply-To: <5059126e-23d2-0e65-11eb-f3a41be84356@tnetconsulting.net>

On 6/29/20 2:18 PM, Grant Taylor via COFF wrote:
> 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

I should probably include details about how SSH is configured:

uucp user's ~/.ssh/config file:
Host *
	User shortName	# matches the output of uuname -l

Calling system's ~/.ssh/authorized_keys file:
command="/usr/sbin/uucico" ...typical contents...

The uucp user can successfully ssh to the target system without being 
prompted for username or password.  uucico starts automatically.



-- 
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/a98200e5/attachment.bin>


  reply	other threads:[~2020-06-29 20:31 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
2020-06-29 20:31         ` gtaylor [this message]
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=838270a9-c1a0-a3d0-0192-3b2f51f1608c@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).