Home / server / Questions / 56566
Accepted
Second
Asked: 2009-08-21 02:43:57 +0800 CST

ssh tunneling only access

  • 772

Is it possible to configure ssh (on linux) to allow access for tunneling only? Ie user can setup tunnels but cannot get a shell/access files?

linux ssh ssh-tunnel

6 Answers

  1. Best Answer

    Yes, just use /bin/false as shell and instruct the user to start the tunneling SSH process without executing any remote command (i.e. the -N flag for OpenSSH):

    ssh -N -L 1234:target-host:5678 ssh-host
    • 57

  2. In the user's .ssh/authorized_keys file, put something like the following:

    permitopen="192.168.1.10:3306",permitopen="10.0.0.16:80",no-pty ssh-rsa AAAAB3N...

    So, basically, you the controls would be in front of the user's ssh public key separated by a space. In the example, connections using the specific public key will be allowed to do SSH port forwarding only to 192.168.1.10's MySQL server and 10.0.0.16's web server, and will not be assigned a shell (no-pty). You're specifically asking about the "no-pty" option, but the others may also be useful if the user is only supposed to tunnel to specific servers.

    Look at the man page for sshd for more options for the authorized_keys file.

    Note that the user's experience may look a little odd: when they ssh in, it will look like the session is hanging (as they are not getting a pty). That's OK. If the user has specified port forwarding with, for example, "-L3306:192.168.1.10:3306", the port forwarding will still be in effect.

    In any case, give it a try.

    • 12

  3. Give the user a shell that only allows them to log out such as /bin/press_to_exit.sh

    #!/bin/bash
read -n 1 -p "Press any key to exit" key

    This way he can stay logged in as long as he wants, with tunnels active, but not run any commands. Ctrl-c closes the connection.

    • 3

  4. Assign a shell that doesn't let the user log in.

    e.g.

    #!/bin/sh
echo "No interactive login available."
sleep 60
exit 0

    would prevent them from getting a shell prompt, and give them a time-out of 60 seconds - if there's no connection active for 60 seconds then it will exit and thereby disconnect them completely (increase the number according to requirements).

    They can't execute a remote command, either, because that shell won't let them.

    • 2 
  5. ​##Create a new user

sudo useradd -m [user]

##Edit /etc/ssh/sshd_config

Match User [user]
   #AllowTcpForwarding yes
   #X11Forwarding no
   #PermitTunnel no
   GatewayPorts yes ##Enable listening on 0.0.0.0
   AllowAgentForwarding no
   PermitOpen localhost:2888 ##specify port
   ForceCommand echo 'This account can only be used for Tunneling'
    • 1

  6. My solution is to provide the user who only may be tunneling, without an interactive shell, to set that shell in /etc/passwd to /usr/bin/tunnel_shell.

    Just create the executable file /usr/bin/tunnel_shell with an infinite loop.

    Additionally make use of the AllowGroups and Match Group option.

    Fully explained here: http://blog.flowl.info/2011/ssh-tunnel-group-only-and-no-shell-please/

    • 0