Date: Sat, 13 Oct 2001 00:59:00 -0400 (EDT) From: Francisco Reyes <lists@natserv.com> To: <cjclark@alum.mit.edu> Cc: FreeBSD Questions List <questions@FreeBSD.ORG> Subject: Re: Automating ssh connections so only one command would run. Message-ID: <20011013005710.A10822-100000@zoraida.natserv.net> In-Reply-To: <20011011224233.G293@blossom.cjclark.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 11 Oct 2001, Crist J. Clark wrote: > On Thu, Oct 11, 2001 at 11:38:34PM -0400, Francisco Reyes wrote: > > I followed several tutorials on how to automate ssh connections, but I > > would like to restrict the connection so only scp would run. > > scp(1) and ssh(1) are not really designed to work this way. Even if > you can limit users to scp(1), Do you know? That is what I am trying to find. >it is trivial to slip commands through scp(1), >$ scp 'remote:somefile;touch /tmp/scp_test' . > And check for /tmp/scp_test on the remote machine. I don't see how this is a security problem. Could you explain? Automating scp may not be the most secure way to copy data, but is there a better way? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011013005710.A10822-100000>