Results 1 to 2 of 2
Thread: Securing SSH setup
Enjoy an ad free experience by logging in. Not a member yet? Register.
Securing SSH setup
I just set up a server with SSH access. I made an account called "tunnel", and made a perl script saying this account is only intended for remote tunneling and nothing else. After that message, the user can press enter to close the terminal.
I logged into the account using FileZilla, with the SFTP protocol. And it logs in succesfully, showing no directories, which is exactly what I want.
This account has no sudo acces and it's used for logging in from non-trustable machines.
The question is: Is it enough to have an account without /bin/bash to avoid people doing anything with such account?
Also, when logging in, the system tries to cd into /home/tunnel. (Which doesn't work because I didn't create the folder in the first place). Is there any way to prevent the system from cd'ing into /home/tunnel when logging in with tunnel (but letting other users cd into their $HOME as usual)?
- Join Date
- May 2011
- Austin, TX