Passing secret material in the command line for long-running and daemon processes is never a good idea [;
"The sshpass utility is designed to run SSH using the keyboard-interactive password authentication mode, but in a non-interactive way." - recommended approach is to use key authentication instead (i.e., SSH(1) - https://man.openbsd.org/ssh#i). Cheers, FP czw., 11 sty 2024 o 12:36 Jon Perryman <jperr...@pacbell.net> napisał(a): > On Wed, 10 Jan 2024 11:37:11 -0600, Kirk Wolf <k...@coztoolkit.com> wrote: > > > ssh -L 623:127.0.0.1:623 zoshost > >How EXACTLY is your userid and password exposed? > > You example ignores using a script to automate SSH login. There are > various implementations. e.g.sshpass -p !4u2tryhack ssh > usern...@host.example.com > > Even IBM tells you how you can use sshpass: > https://www.redhat.com/sysadmin/ssh-automation-sshpass > > Realize that it's not just sysadmins using it. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
