Tag Info

New answers tagged


Not what you asked for, but have you seen the "-D" option, to turn ssh into a SOCKS5 server? Then you can just run programs on the local side behind tsocks and connect to anything you like on the remote end.


See man sshd_config: AllowUsers This keyword can be followed by a list of user name patterns, separated by spaces. If specified, login is allowed only for user names that match one of the patterns. Only user names are valid; a numerical user ID is not recogā€ nized. By default, login is allowed for all users. If the ...


You could prefix the key with a forced command that tells the user what's going on. For example: command="/usr/bin/printf '*** Your key has been disabled ***\r\n'; sleep 1",no-pty,no-port-forwarding ssh-rsa AAAAB2...19Q== joe@example.net Then they get: $ ssh servername PTY allocation request failed on channel 0 Your key has been disabled Connection to ...


Yes you can just put # (or any other character, as long as the initial entry e.g. ssh-rsa is no longer valid), before the relevant line. If you do that, and the system allows for plain text password logins as well, the user will be prompted for a password to login. So you might want to check that there is no (known) password associates with the account.


Assuming that you have control over your home network, and that there you setup your internal IP address fixed (e.g. based on the MAC address of your home PC), then you can open up a port (e.g. 4321) on your home router to forward to your PC also on 4321. At home make sshd listen on that port. Create a new user locally as you (of course) don't want to use ...


It's easy: [execute from office machine] Setup connection Office -> Home (as Home has public IP). This will setup reverse tunnel from your office machine to home. ssh -CNR 19999:localhost:22 homeuser@home [execute from home machine] Connect to your office from home. This will use tunnel from the step 1. ssh -p 19999 officeuser@home Please ensure, that ...


Why can't the OpenSSH configure script detect OpenSSL explains the possible cause that might have occured in your case. Several reasons for problems with the automatic detection exist. OpenSSH requires at least version 0.9.5a of the OpenSSL libraries. Sometimes the distribution has installed an older version in the system locations that is detected ...

Top 50 recent answers are included