Closed baltpeter closed 1 year ago
We can work around this with -o "StrictHostKeyChecking=no"
. While that doesn't sound ideal security-wise, I think it is a fair compromise:
With this option, the host key is added automatically to ~/.ssh/known_hosts
on the first connection. But it still checks against that. So, if on a later connection, the host key doesn't match the one that was automatically served earlier, it will error.
And let's be honest, here. I certainly didn't verify the iPhones' host keys when I first connected to them, I just entered yes
. :D
Wait, there is a problem with #43, though: When we use iproxy
, we're not using the actual device IP and port anymore. Instead, we'll be connecting to localhost
. And my idea was to use a random free port.
This problem is "solved" because NodeSSH doesn't do key checking by default anyway.
If the user never manually connected to the iPhone via SSH and trusted its fingerprint,
sshpass
calls will not run:If you instead use
ssh
directly, you get this: