Re: Telnet Pbl
From: Dances With Crows (danSPANceswitTRAPhcrows_at_usa.net)
Date: 02/16/04
- Next message: petefa: "Re: Terminal application for SUSE"
- Previous message: Ulf Doz: "Re: mv ate my file, rev. 2"
- In reply to: Peter Höltschi: "Telnet Pbl"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 16 Feb 2004 21:50:09 GMT
On Mon, 16 Feb 2004 22:08:10 +0100, Peter Höltschi staggered into the
Black Sun and said:
> I have a little logical problem with telnet. I have a windows box
> connected to a internet gateway (redhat 9). Now I would like over
> night to download some big files, like the iso files from other lx
> distros onto my redhat box. To do this I login to the redhat box from
> my windows pc via telnet
Argh. Not only is telnet insecure, it's less convenient than ssh. Set
up your ssh keys properly, and you'll never have to remember a password
to a remote machine again--check the end of this message for a quick way
to do that.
> and start the ftp download this machine. Then I logout from redhat to
> shutdown my windows pc over night. But at the same time the ftp
> process stops too. How can I make the ftp process go on without beeing
> logged in to redhat?
Use nohup (makes a process immune to HUP signals--your processes get a
HUP signal when you log out), scp (Secure CP, encrypted file-transfer
that can be made password-less), and & (puts a process in the
background.) Like so:
(use PuTTY to ssh to your Redhat machine:)
redhat:~$ nohup scp localfile othermachine:/path/to/remote/directory/ &
redhat:~$ exit
(done)
...you can use ncftp instead of scp if you really want, but running an
interactive program like the normal /usr/bin/ftp won't really work well
if you try to use nohup on it.
Passwordless ssh:
0. machine1:~$ if [ -d ~/.ssh ] ; then true ; else mkdir ~/.ssh ; fi ; chmod
700 ~/.ssh
1. machine1:~$ ssh-keygen
2. machine1:~$ scp ~/.ssh/id_dsa.pub machine2:/home/me/machine1key
3. machine1:~$ ssh machine2
4. machine2:~$ if [ -d ~/.ssh ] ; then true ; else mkdir ~/.ssh ; fi ; chmod
700 ~/.ssh
5. machine2:~$ cat ~/machine1key >> ~/.ssh/authorized_keys2
...may look a little confusing, but it should work, and you'll like the
convenience even if you don't care about ssh's additional security. HTH,
-- Matt G|There is no Darkness in Eternity/But only Light too dim for us to see Brainbench MVP for Linux Admin / mail: TRAP + SPAN don't belong http://www.brainbench.com / Hire me! -----------------------------/ http://crow202.dyndns.org/~mhgraham/resume
- Next message: petefa: "Re: Terminal application for SUSE"
- Previous message: Ulf Doz: "Re: mv ate my file, rev. 2"
- In reply to: Peter Höltschi: "Telnet Pbl"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
