[BLU] Re: Trusted ssh/scp and Linux (Slackware 7)

[david at kramer.ne.mediaone.net (David Kramer)]

On Fri, 14 Jul 2000, Derek Martin wrote:

> On Fri, 14 Jul 2000, Scott Ehrlich wrote:
> 
> > My biggest question now is how to set up the scp trust between the four
> > machines (now) each containing log files, and a central destination system
> > to receive said logs?  The goal is for an automated secure copy so no user
> > intervention needs to enter a password for ssh authentication for scp to
> > work.   The logs will most likely get transferred to one account on the
> > destination site.
> 
> You need to create a key to use, and create it WITH NO PASSPHRASE.
> Obviously this has implications, so you'll want to make sure that you're
> careful about who has physical access to the key file.  

There is another way of doing it, though I have to admit I am VERY shaky
on the details because I saw someone do it about four years ago and that
was it.  It involved setting up the key with a password, and then you
issue some command that opens up a pipe to the other side.  You leave that
pipe open, and the scp goes over that existing pipe, leaving it open for
next time.

I realize this is probably not enough information for anyone to figure out
what I'm talking about, and I apologize for that, but on the off chance
that someone can, here it is.

See y'all tomorrow. 

-------------------------------------------------------------------
DDDD   David Kramer                   http://kramer.ne.mediaone.net
DK KD  
DKK D  Every non-key attribute depends on the key, the whole key,
DK KD  and nothing but the key, so help me Codd.
DDDD                                      (Sybase training class)

-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).