The author claims that sshpass is "broken by design" and goes on to show some examples of why, without ever explaining anything.
Can anyone enlighten me why sshpass is broken, or explain the examples on that page?
Can anyone enlighten me why sshpass is broken, or explain the examples on that page?
On the sidebar, in the about, it says,
> sshpass is broken by design
This is another repo. But probably where they got it.
More importantly though is that sshpass keeps your password permanently on your computer, thus increasing security risks considerably.
bad:
bash-4.4# tty
/dev/pts/18 // the bash's stdin is also connected to pts/18
bash-4.4# tty
/dev/pts/18 // the bash's stdin is connected to the new pts/36
And yes, if I use either sshpass or passh, the password will have to be "on my computer" (i.e. in a script or text file), that's the whole point of it: accessing devices that don't do public-key authentication non-interactively
I can argue that SSH password auth only makes sense.as in interactive affair; for non-interactive auth cases, there are public keys, certificates, smart cards, etc.