Date: Thu, 11 Oct 2001 22:42:33 -0700 From: "Crist J. Clark" <cristjc@earthlink.net> To: Francisco Reyes <lists@natserv.com> Cc: FreeBSD Questions List <questions@FreeBSD.ORG> Subject: Re: Automating ssh connections so only one command would run. Message-ID: <20011011224233.G293@blossom.cjclark.org> In-Reply-To: <20011011233059.F7823-100000@zoraida.natserv.net>; from lists@natserv.com on Thu, Oct 11, 2001 at 11:38:34PM -0400 References: <20011011233059.F7823-100000@zoraida.natserv.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
> I have seen in the past on a magazine two options one can put on the
> authorized_keys file: from, command.
>
> Anyone has an example on how to do this? Basically I am trying to automate
> scp, but don't want any other command to run without a passphrase.
scp(1) and ssh(1) are not really designed to work this way. Even if
you can limit users to scp(1), 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.
--
Crist J. Clark | cjclark@alum.mit.edu
| cjclark@jhu.edu
http://people.freebsd.org/~cjc/ | cjc@freebsd.org
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?20011011224233.G293>