Contents
Can a restricted shell be run on SSH?
A major problem with restricted shell is that to secure it, you must use .profile or .bashrc to restrict the PATH, disable builtins, etc., but those files are only invoked for interactive shells. If a user uses ssh to run a remote command they are not invoked.
How to get out of a restricted shell?
One of these commands will be ksh, which means a user running the restricted shell can easily exit out of the restricted shell by simply running ksh to start another shell that will run in normal, full access mode. As described later in this document, additional steps must be taken to further restrict access by a user.
Can a shell command be used as a SSH command?
Only complete shell commands can be allowed. But it does support simple patterns to represent similar commands that vary only in the digits that appear on the command line (e.g. sequence numbers or date/time stamps). It’s like a firewall or whitelisting control for ssh commands.
How to use a restricted shell-IBM?
Change the default shell for the user to rksh. Create a .profile in the user’s home directory and set the PATH environment variable to a directory containing all of the commands you want the user to be able to run. Create the directory that will contain the commands.
A command restriction for the user prevents the backup server from being automatically compromised if the private key is compromised. Since the user is restricted to a command in the authorized_keys file, he must not execute any other command or set up a terminal session via SSH.
Is there a way to limit SSH to one command?
In order to limit the user to a single command, the parameter command = is entered before the key. Thereafter, when attempting to set up an SSH connection, only this command is always executed, even if, for example, another command was transferred.