Where can I find information on rsh -- on a newbie level? Thanks, Tom --- Tom Nielsen Neuro Logic Systems, Inc. 805.389.5435 x18 www.neuro-logic.com
On Tue, 2003-01-21 at 14:38, Tom Nielsen wrote:
Where can I find information on rsh -- on a newbie level?
Thanks, Tom
---
Tom Nielsen Neuro Logic Systems, Inc. 805.389.5435 x18 www.neuro-logic.com
You would be much better off using ssh instead. It is much more secure.
Secure is good. But I'm having a hard time copying files between my work system and my home system. Currently I'm ssh'ing into my work firewall box, then ssh into my work machine (192.168.2.1). Maybe I'm not using scp correctly. Given that information, how would I scp doc.txt to my home system (192.168.3.3)? Tom On Tue, 2003-01-21 at 11:37, Ken Schneider wrote:
On Tue, 2003-01-21 at 14:38, Tom Nielsen wrote:
Where can I find information on rsh -- on a newbie level?
Thanks, Tom
---
Tom Nielsen Neuro Logic Systems, Inc. 805.389.5435 x18 www.neuro-logic.com
You would be much better off using ssh instead. It is much more secure.
--- Tom Nielsen Neuro Logic Systems, Inc. 805.389.5435 x18 www.neuro-logic.com
On Tuesday 21 January 2003 7:46 pm, Tom Nielsen wrote:
Secure is good. But I'm having a hard time copying files between my work system and my home system.
Currently I'm ssh'ing into my work firewall box, then ssh into my work machine (192.168.2.1). Maybe I'm not using scp correctly. Given that information, how would I scp doc.txt to my home system (192.168.3.3)?
if you can ssh in then scp will work. Here's some examples scp files_on_this_server user@domain:/path/to/dir scp user@domain:/path/to/file/with/wildacrds/allowed /path/to/dir scp user1@domain1.com:/file1 user2@domain2.com:/file2 /path/to/dir -- Richard Fletcher, Sheffield, UK.
On Tue, 2003-01-21 at 14:46, Tom Nielsen wrote:
Secure is good. But I'm having a hard time copying files between my work system and my home system.
Currently I'm ssh'ing into my work firewall box, then ssh into my work machine (192.168.2.1). Maybe I'm not using scp correctly. Given that information, how would I scp doc.txt to my home system (192.168.3.3)?
You can try this scp -4 -oProtocol=1 <name of the file> <name of user on machine>@192.168.3.3:~ -- Marshall "Nothing is impossible, We just do not have all the anwsers to make the impossible, possible."
On Tue, 2003-01-21 at 15:41, Marshall Heartley wrote:
On Tue, 2003-01-21 at 14:46, Tom Nielsen wrote:
Secure is good. But I'm having a hard time copying files between my work system and my home system.
Currently I'm ssh'ing into my work firewall box, then ssh into my work machine (192.168.2.1). Maybe I'm not using scp correctly. Given that information, how would I scp doc.txt to my home system (192.168.3.3)?
You can try this
scp -4 -oProtocol=1 <name of the file> <name of user on machine>@192.168.3.3:~
This will not work as he is going across the public network.
-- Marshall
"Nothing is impossible, We just do not have all the anwsers to make the impossible, possible."
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Ken Schneider Senior UNIX Administrator Network Administrator kschneider@rtsx.com
Op dinsdag 21 januari 2003 22:02, schreef Ken Schneider:
On Tue, 2003-01-21 at 14:46, Tom Nielsen wrote:
Secure is good. But I'm having a hard time copying files between my work system and my home system.
Currently I'm ssh'ing into my work firewall box, then ssh into my work machine (192.168.2.1). Maybe I'm not using scp correctly. Given that information, how would I scp doc.txt to my home system (192.168.3.3)?
You can try this
scp -4 -oProtocol=1 <name of the file> <name of user on machine>@192.168.3.3:~
This will not work as he is going across the public network.
what about using ssh's forwarding (-L or -R). It's just a suggestion as I am not familair enough with these features. -- Richard Bos Without a home the journey is endless
On Tue, 2003-01-21 at 16:02, Ken Schneider wrote:
On Tue, 2003-01-21 at 15:41, Marshall Heartley wrote:
On Tue, 2003-01-21 at 14:46, Tom Nielsen wrote:
Secure is good. But I'm having a hard time copying files between my work system and my home system.
Currently I'm ssh'ing into my work firewall box, then ssh into my work machine (192.168.2.1). Maybe I'm not using scp correctly. Given that information, how would I scp doc.txt to my home system (192.168.3.3)?
You can try this
scp -4 -oProtocol=1 <name of the file> <name of user on machine>@192.168.3.3:~
This will not work as he is going across the public network.
OOPS! That's my bad! Sorry about that. I have had a long day and I guess that I did not read the question well enough :( -- Marshall "Nothing is impossible, We just do not have all the anwsers to make the impossible, possible."
On 21 Jan 2003 11:46:18 -0800 Tom Nielsen <tom@neuro-logic.com> wrote:
Secure is good. But I'm having a hard time copying files between my work system and my home system.
Currently I'm ssh'ing into my work firewall box, then ssh into my work machine (192.168.2.1). Maybe I'm not using scp correctly. Given that information, how would I scp doc.txt to my home system (192.168.3.3)?
I've always seemed to prefer sftp over scp, maybe because I learned it first. Try sftp. You create a separate login session, just like ssh, then it's just like ftp. The only "gotcha" is keeping track of the local and remote directories. All the "local" (on your machine) commands begin with "l". -- use Perl; #powerful programmable prestidigitation
On Tuesday, January 21, 2003 11:46:18 AM -0800 Tom Nielsen <tom@neuro-logic.com> wrote: +------ | Secure is good. But I'm having a hard time copying files between my work | system and my home system. | | Currently I'm ssh'ing into my work firewall box, then ssh into my work | machine (192.168.2.1). Maybe I'm not using scp correctly. Given that | information, how would I scp doc.txt to my home system (192.168.3.3)? | | Tom | | On Tue, 2003-01-21 at 11:37, Ken Schneider wrote: | | > On Tue, 2003-01-21 at 14:38, Tom Nielsen wrote: | > > Where can I find information on rsh -- on a newbie level? [...] | > You would be much better off using ssh instead. It is much more secure. +-----X8 When you login to the firewall forward port 22 on your workstation to your home machine (e.g. -L 2222:192.168.2.1:22) then "scp -P 2222 localhost", I usually prefer to use rsync, unison or even sftp. /Michael -- This space intentionally left non-blank.
participants (7)
-
Ken Schneider -
Marshall Heartley -
Michael Salmon -
Richard Bos -
Richard Fletcher -
Tom Nielsen -
zentara