diff options
author | Daniel Friesel <derf@finalrewind.org> | 2011-05-18 17:18:07 +0200 |
---|---|---|
committer | Daniel Friesel <derf@finalrewind.org> | 2011-05-18 17:18:07 +0200 |
commit | e3d8540722c7948553c6141afa834d35e04872ae (patch) | |
tree | f4dc643af2cd73144fb94fb79da4f30b49c31b41 /bin | |
parent | 998462a05c1d5af997d4ae59ad52d1ab69265071 (diff) |
Improve language in ssh-forcecommand(1)
Diffstat (limited to 'bin')
-rwxr-xr-x | bin/ssh-forcecommand | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/bin/ssh-forcecommand b/bin/ssh-forcecommand index 5443920..a355656 100755 --- a/bin/ssh-forcecommand +++ b/bin/ssh-forcecommand @@ -47,14 +47,14 @@ This is B<ssh-forcecommand> version 1.0 =head1 DESCRIPTION B<ssh-forcecommand> is a trivial script to safely execute remote commands via -ssh. It is especially aimed at automated remote commands (so, ssh keys not -secured via password), where a compromise of the remote system (-> private -key) could also compromise the local system. - -To prevent this, you can put the forcecommand into the ssh config -(authorized_keys, to be precise), so the remote system can only execute a set -of statically defined commands. This way, compromising the local system is -made much more difficult. +ssh. It is especially aimed at automated remote commands (in which ssh keys +are not secured via password), where a compromise of the remote system could +also compromise the local system. + +To prevent this, you can invoke ssh-forcecommand through the ssh +configuration, which will limit the romet system so that it can only execute a +set of statically defined commands. This way, compromising the local system is +made much more diffecult. =head1 CONFIGURATION |