Your browser does not allow storing cookies. We recommend enabling them.

SSH Tectia

Using a Shared Account

In case the tunneled applications provide sufficient user authentication, it is possible to use a shared user account, for example with a shared password, not requiring user interaction. Note that the shared account and password must only be used for tunneling, as the account is common to several users and the shared password is stored as plaintext in the Connection Broker configuration file.

See the operating system documentation for instructions on how to create a new user account, for example tunnel, with minimal privileges. It is very important that the shared user account is properly configured on the operating-system level.

The user should be denied at least shell access and the file system permissions should be restricted. This is done as a precaution in case the user is able to access the system using some other means than Secure Shell.

To deny shell access on the operating-system level, you can set the user's shell to /bin/false or use a script that can also inform the user of the situation:

For example, you could have the following saved to name /bin/no-shell:

#!/bin/sh

echo "Shell access to this account has been disabled."
exit 1


 

 
PrivX
 

 

 
What to read next:

  • Reduce Secure Shell risk. Get to know the NIST 7966.



    The NISTIR 7966 guideline from the Computer Security Division of NIST is a direct call to action for organizations regardless of industry and is a mandate for the US Federal government.
    Download now
  • ISACA Practitioner Guide for SSH



    With contributions from practitioners, specialists and SSH.COM experts, the ISACA “SSH: Practitioner Considerations” guide is vital best practice from the compliance and audit community.
    Download now