Try ssh -Y Any reason you don’t want to use the -Y flag instead of the -X flag? Quite simply, the difference between -X and -Y is that -Y enables trusted X11 forwarding.
If no one else is using the system at the moment you could do what i’ve done in such cases: stop sshd service (at least i’ve been able to do this while logged in via ssh) start sshd manually and add some -d options to get more verbose debug output. Unless you have something funky … Read more
I don’t think that is the best solution, but it was a solution for me. ANSWER: Adding the domainnames to the known_hosts file using the ssh-keyscan command solved the issue: ssh-keyscan <enter_domainname_e.g._github.com> >> ~/.ssh/known_hosts
Try Match in sshd_config: Match User user1,user2,user3,user4 PasswordAuthentication no Or by group: Match Group users PasswordAuthentication no Or, as mentioned in the comment, by negation: Match User !root PasswordAuthentication no Note that match is effective “until either another Match line or the end of the file.” (the indentation isn’t significant)
As you mentioned, the environment variables are removed by sudo, for security reasons. But fortunately sudo is quite configurable: you can tell it precisely which environment variables you want to keep thanks to the env_keep configuration option in /etc/sudoers. For agent forwarding, you need to keep the SSH_AUTH_SOCK environment variable. To do so, simply edit … Read more
Try ssh -o PasswordAuthentication=yes -o PreferredAuthentications=keyboard-interactive,password -o PubkeyAuthentication=no host.example.org In ssh v2, keyboard-interactive is another way to say “password”. The -o PubkeyAuthentication=no option instructs the client not to attempt key pair authentication. In addition, the PasswordAuthentication=yes option is to override any previously configured ssh options that may have disabled it.
UPDATE: For an actual answer see zero_r’s answer below This isn’t an answer, but a workaround. Use screen. When you first log in, run screen. You get another shell, run commands in that. If you’re disconnected, the screen process keeps the terminal alive so that your shell and the processes it is running don’t fall … Read more
In today’s internet this is quite normal sadly. There are hordes of botnets trying to login to each server they find in whole IP networks. Typically, they use simple dictionary attacks on well-known accounts (like root or certain applications accounts). The attack targets are not found via Google or DNS entries, but the attackers just … Read more
get the rsa key of your server, where server_ip is your server’s IP address, such as 192.168.2.1: $ ssh-keyscan -t rsa server_ip Sample response: # server_ip SSH-2.0-OpenSSH_4.3 server_ip ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAwH5EXZG… and on the client, copy the entire response line server_ip ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAwH5EXZG…, and add this key to the bottom of your ~/.ssh/known_hosts file: server_ip ssh-rsa … Read more
You can do it with Bash’s process substitution: diff foo <(ssh myServer ‘cat foo’) Or, if both are on remote servers: diff <(ssh myServer1 ‘cat foo’) <(ssh myServer2 ‘cat foo’)