ssh_config | a simple ssh config parser/writer lib in go | Parser library

So I found the issue: I was trying to mount the .ssh folder (which has the key to connect to the remote server).

I don't know exactly why it was working on the command line and not through fstab (may be something with the SSH agent) but mounting the folder used to connect to SSHFS caused the issue. I moved the SSH keys to another directory and then it worked like a charm.

It depends on what you used for the $keyFile in your script.

A default name should be part of the /home/pi/.ssh/id_xxx names considered during an SSH session.
But a non-default name would need to be specified in an ~/.ssh/config: double-check if you have one.

Also, in your script, to be sure, don't use ~/.ssh, but /home/$USER/.ssh consistently, to avoid any mistake when the shell substitutes ~.

Solved. The solution was to generate new rsa and dsa keys with:

Your server/device seems to require some dummy keyboard interactive authentication:

TL;DR Your config file "github" entry should look like this:

I have been able to solve this and will explain how.

My issue was my password was not being accepted even after resetting the password in the droplet.

"Password not accepted in the console" info can be found here https://docs.digitalocean.com/products/droplets/resources/troubleshooting-ssh/authentication/

I followed the Boot into the Recovery process linked here: https://docs.digitalocean.com/products/droplets/resources/recovery-iso/#boot-into-the-recovery-iso

• Power down or stop droplet
• Select boot from recovery ISO
• Turned on the droplet again
• clicked the console

At this stage I was present with a list of options.

1. Mount your Disk Image [Not Mounted]
2. Check Filesystem
3. Reset Droplet Root Password
4. Configure Keyboard
5. Attempt to 'chroot' into installed system
6. Interactive Shell [/bin/bash] Choose (1-6) and press Enter to continue.

• I selected option 1, then 3, followed by 6.

• After this I powered off the droplet and selected boot from hard drive.

• Accessing the console I was able to login and enter the password which was accepted and the ghost install began and completed successfully.

I hope this helps anyone who is experiencing the same issue.

There are a few things you are doing wrong

1. You should not login from within the gerrit container as it will use the gerrit user and ssh key. There is no gerrit user in gerrit in such a way
2. You should create a new user, are you using LDAP?
3. Next, log in to gerrit using that users credentials and add the public ssh key from the user in the user profile. Depending on your server url: https://myserver.net/settings/#SSHKeys
4. Now you should be able to connect

I answer my question:

Since putty is working well : use Putty to forward 22 port through SOCKS5

A) proxy :

• SOCKS 5
• hostname : 127.0.0.1
• port:1080

B ) forward port L22 127.0.0.1:22

C) ssh to 127.0.0.1:22 ssh -l "username" 127.0.0.1

You can this way use Remote Visual Studio Code through shadowsocks proxy...

If the private key format differs, that means, as I mentioned here that:

• one platform is using openssh prior to 7.8, with an old PEM 64-chars per line format.
• one is using a more recent OpenSSH format, 70-chars per line.

You can force a recent openSSH to generate the old format with: