Hot answers tagged ssh
When you reinstall a machine it gets a new ssh host key, but the old one is still stored in your key file. Open ~/.ssh/known_hosts with an editor and remove the lines containing the problematic host keys. You'll be asked to verify the new host keys the next time you connect.
You must specify the remote user, otherwise it will use the user that you are logged into locally. For example: ssh username@host So, in your case you would use: ssh toto@toto
If you can't boot into a root shell you're kinda boned. I've seen this happen before when people forget to change the access on the key file. The recommended method is to attempt to use the key before turning off password based authentication. If it's an instance in a cloud, call your provider and have them reset the password (which may not be free or even ...
Your Pi is running an ssh server. Your PC is not. Both have ssh clients available. There are numerous ssh server packages available, but I don't know what kind of machine you are running on to recommend one. A simple Google "install ssh server 'machine type, i.e., Linux'" should suffice. To test that it works on the machine you install it on, you can ...
On your lubuntu machine run ifconfig -a to find the ipaddress assuming you don't recall the host name. Then open a terminal on your Ubuntu machine and type ssh user@ipaddress(or host name) and then type in the password for the user. Alternatively you can setup a private key for your Ubuntu machine and upload the public key to your lubuntu machine, ...
Your Subsystem value in sshd_config is wrong. It should be Subsystem sftp /usr/lib/openssh/sftp-server or internal-sftp. Try to modify the /etc/ssh/sshd_config to this value, restart the ssh service ans try once more.
Edit: upon re-reading your question I surmise that your server is behind a firewall that you do not control? If so, please disregard the iptables part of the answer and skip to the SSH config part... Is it a matter of wanting the transport to be encrypted, or is it simply a matter of getting through the firewall? Getting through the firewall could be as ...
One possible cause of the problem is that you have DSA keys but now SSH (apparently) defaults to requiring RSA keys. I got the problem when upgrading to 16.04. You can see more here but the short answer is add the following to ~/.ssh/config: PubkeyAcceptedKeyTypes ssh-dss
This is how I got it working when running byobu Add this line in .bash_login before the "_byobu_source.." line: echo $DISPLAY > $HOME/.display.env And then add this line to .bashrc: export DISPLAY=$(cat $HOME/.display.env)
Only top voted, non community-wiki answers of a minimum length are eligible