New answers tagged openssh
See if this helps you. ssh <host> bash --login -c <command> Start bash as a login shell through SSH and then load the rbenv via SSH's -c option.
You may want look into GNU screen or tmux. they both have the attach feature. typical workflow looks like this: Connect with SSH Start a screen/tmux session. Do your work. Disconnect. Next time you login, attach the last session and continue working.
The linked answer in the other answer is really old and there are many changed things since then. So once again: If you read through the manual page for sshd_config(5), there is option AuthenticationMethods, which takes the list of methods you need to pass before you are granted access. Your required setup is: AuthenticationMethods pubkey,password This ...
If you're using recent versions of RHEL (Red Hat Enterprise Linux) or Fedora, see the accepted answer to this question. That solution may work on other distributions as well, if your SSH daemon is new enough.
@HXCaine run sudo apt-get install rsyslog Your problem will be solved. You will get ssh logs in /var/log/auth.log Which is used by fail2ban. I had the same problem,solved it using this.
Thanks for the help and for the responses, it turns out, that basically this issue is pointless. My eyes got opened by a helpful redditor ckozler: https://www.reddit.com/r/linuxadmin/comments/3kdn1r/openssh_server_fatal_too_many_listen_sockets/cuwoo02 But they'll still be connecting to YOU on port 22, the reverse SSH tunnel is a port opened on THEM to ...
You can run sshd using inetd (and optionally tcpd) on as many ports as you like with the following inetd.conf: 10000 stream tcp nowait root /usr/sbin/tcpd sshd -i 10001 stream tcp nowait root /usr/sbin/tcpd sshd -i 10002 stream tcp nowait root /usr/sbin/tcpd sshd -i ... You should also read the caveats on sshd -i in the sshd manual.
Top 50 recent answers are included