can't transfer files between networked YDL boxes

[David Purdy]

Ron:

I was able to connect via ssh and scp just fine.  It
took a moment to figure out the command formats, but I
got it.  LOL, on my first try I ended up copying the
file from the remote home directory to the remote
desktop!  Well, I got it...thanks.

The one machine (G3 w/ YDL 3.0) seemed to have a ssh
server already running on it.  I don't think the 2.3
machine had it listed in the services.  I'm not sure
why that is.  Is it possible to install ssh after
basic installation?

Back to the FTP thing... how hard is it to install and
configure a basic ftp server anyway? Any good
references for the newbie like me? (reads as: I will
have to have *everything spelled out.)

Thanks again,

Dave Purdy


--- David Purdy <purdyd_at_wisheights@yahoo.com>
wrote:
> Hi Ron:
> 
> Thanks so much.  I will try it as soon as I get
> home. 
> It sounds pretty straightforward...though
> "straightforward" is a relative term - especially in
> the case of a newbie like me.
> 
> I will give the man pages of ssh and scp a good
> looking over, for command syntax & such.
> 
> Much appreciated...I'll let you know either way how
> it
> goes.
> 
> Thanks,
> 
> Dave Purdy
> 
> --- Ron Smith <ronsmith@ydl.net> wrote:
> > I don't think that YDL enables FTP by default.
> > 
> > Do you have ssh running? If so you can scp (secure
> > copy) the files from 
> > one machine to the other. This is a bit overkill
> > since it is *highly* 
> > unlikely that anyone is going to intercept your
> data
> > over a crossover 
> > cable, but it might be easier than starting up
> ftpd.
> > Plus you won't 
> > have the security liability of having ftp running
> > when you do end up 
> > connecting them to the public network.
> > 
> > If you are not familiar with ssh, it is basically
> a
> > secure replacement 
> > for telnet. From the user perspective it works
> just
> > like telnet. Under 
> > the hood it is really creating an encrypted
> session
> > between the two 
> > machines and *never* sends your password across
> the
> > network in plain 
> > text (telnet does).
> > 
> > Instead of:
> > telnet machine2.mydomain.com
> > 
> > you would:
> > ssh machine2.mydomain.com
> > 
> > Or you telnet/ssh directly to the IP address
> instead
> > of by domain name. 
> > The first time you use ssh to a particular machine
> > it will ask you if 
> > you want to accept the key from the remote
> machine.
> > After that it is 
> > just like telnet in that it will ask for your
> > password, then you are 
> > logged in with your normal prompt and at  your
> home
> > directory.
> > 
> > As long as ssh works, scp will work too. If ssh is
> > running and you want 
> > to give that a try it is a good way to transfer
> > files. Unlike ftp it 
> > will give you the status of the file transfer (%
> > complete). It can be a 
> > little tricky at first so if you can't figure it
> out
> > from the scp  man 
> > page, let me know and I will try to explain it
> more
> > clearly.
> > 
> > On Thursday, May 22, 2003, at 12:25 PM, David
> Purdy
> > wrote:
> > 


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com