Don't know if this helps or not, but, SCP usually used after an SSH session is invoked and authenticated. Setting up configs in hosts/allow hosts/deny circumvents the security intentions of using SSH, and may cause the error messages you are seeing. The FW (if told to) will accept scp via ssh/port 22 or the port designated, but will otherwise cut off (deny) access ...
my .02 cents. (:>) tom
Message: 13
Date: Tue, 21 Jan 2003 15:06:06 +0000
To: [EMAIL PROTECTED]
From: Nick Lindsell <[EMAIL PROTECTED]>
Subject: Re: scp with 2 remote hosts
Reply-To: [EMAIL PROTECTED]
At 09:12 21/01/2003 -0500, you wrote:
> Only a wild guess but can hostA scp to hostB ?
Interestingly I just tried to scp between to remote hosts using "[root@core]# scp nick@host-1:filename nick@host-2:/home/nick" and unless host-2 was resolvable by host-1 then I got "host-2: Name or service unknown" (which is resolver error, aistr). The "command host", core, can resolve host-2 just fine, btw.
Putting host-2 into /etc/hosts on host-1 resulted in a timeout on port 22 of host-2 which was expected as host-1 is blocked by host-2 firewall. So the resolver error came from host-1 it seems. (phew, what a lot of hosts.... a host of hosts?) This indicates to me that host-1 is attempting to contact host-2 directly. I see nothing in my logs (am I looking in the wrong place?). So I believe that hostA needs setting up to scp to hostB with public keys. ??? nick@nexnix -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
