known_hosts | A simple cli known hosts manager | Awesome List 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 ~.

Your approach is correct and should work if done correctly. Although FYI it doesn't entirely protect from MitM -- ssh-keyscan itself uses an unverified connection and is vulnerable to MitM, although if that connection is legit, checking the key prevents faking on later connections. This is a form/variant of SSH's common 'ToFU' (Trust on First Use) security model.

From my basic understanding, the known_hosts file contains a key. ...

In general, known_hosts contains a mapping from host identities (names and/or IP addresses) to keys. But if your file was created only as you show, it has only one mapping entry containing only one key.

1. make sure you pass the correct path to setKnownHosts, and run as the correct (same) user. If the path you specify cannot be opened (either does not exist or access not allowed) Jsch does NOT throw any error, it just returns without loading anything. You might instead open the file yourself with new FileInputStream(pathstring) and pass to the setKnownHosts(InputStream) overload, so you get an exception if the open fails.

2. make sure you are using the same host identity. If e.g. a host has multiple names (like cloud servers often do) and you use one in ssh-keyscan but a different one in JSch then even though this is actually the same host and key it won't match. But if you are actually using IP addresses in both places, at least if you mean IPv4, this is less likely because very few machines today have multiple public IPv4 addresses. (In the past this was more common and called multihoming.) IPv6 is more possible; most IPv6 machines have both transient and permanent public addresses (as well as local/private ones), and often multiple transients.

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

I asked a senior dev at my company and he suggested that I just update my ~/.ssh.config file. I added:

I was probably over engineering it.

Setting the ssh.ClientConfig like this solved the problem:

It maybe the null-safety of Flutter 2.0.1 cause build release failed(I found other error may cause this error, but the build error tips has no relation with the real error). I fix it by prebuild project add this line in workflow ci file:

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.