Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You are probably asking about the passh page. Examples there show that sshpass creates a new permanent tty entry with each use, while passh does not.

More importantly though is that sshpass keeps your password permanently on your computer, thus increasing security risks considerably.



Yeah, but that's my question, why is all that stuff about TTYs bad? The examples basically say:

bad:

   bash-4.4# tty
   /dev/pts/18     // the bash's stdin is also connected to pts/18
good:

   bash-4.4# tty
   /dev/pts/18     // the bash's stdin is connected to the new pts/36
...and stuff about controlling terminals and missing job control, but why are these things bad?

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




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: