[KLUG Members] IPCOP
paul
members@kalamazoolinux.org
Thu, 21 Mar 2002 22:48:15 -0500
ok, here is an update on my confusion... 'paul' is my machine inside the
firewall - I use mozilla to access the firewall's Secure shell window.
I tried the scp command below, and got a confusing message... a little
more searching at the sourceforge email archive gave me a few more
clues... I'm out of time tonight, I'll finish this task over the weekend.
(the end result here is to get a VPN connection thru IPCOP)
root@ipcop~$ scp -v vanallp@paul:/home/vanallp/ip_masq_ipsec.o
root@ipcop:/root/ip_masq_ipsec.o
Executing: /usr/bin/ssh -v -x -o'FallBackToRsh no' -n -l vanallp paul
scp -v /home/vanallp/ip_masq_ipsec.o ' root@ipcop:/root/ip_masq_ipsec.o'
sh: /usr/bin/ssh/: No such file or directory
root@ipcop~$
SourceForge archived mail:
On Mon, Feb 25, 2002 at 03:53:04PM +0100, Mark Wormgoor wrote:
> Hi
>
> > I've recently install IPCop 0.1.1 and noticed that the ssh client
> > /usr/local/bin/ssh is no longer there. Without that scp (which is
> > still present) no longer works, and I can no longer use scp to
> > backup the configuration.
> >
> > Was it left out delibately ?
>
> Actually, yes it was. There shouldn't be too much client software on a
> firewall. But scp works just fine the other way around (from another
> machine to IPCop). I use it very regularly.
>
> Kind regards,
>
> Mark Wormgoor
Thanks, I can confirm that it works if you run the scp from the
remote machine. Which is probably also safer as it only needs
one ssh connection and one username/password pair.
ps. Note for any else who's thinking of doing this: Do not scp the
"/dev" or "/proc" directories as you'll get into recursive loops.
--
John Edwards
shade@cornerstonelinux.co.uk