In case your password has non-alphanumeric characters in it, try enclosing
the variable substitution on the shell in single or double quotes. You can
rule out if that is your issue by temporarily setting the password to just
a random string of only alphanumeric [A-Za-z0-9]. In my experience
passwords with all kinds of characters will be properly quoted and used by
clogin when they are set in {} inside .cloginrc .
-andreasOn Tue, May 2, 2023 at 10:10 PM Piegorsch, Weylin William <[email protected]> wrote: > Anyone know what I’m doing wrong here? I’ve verified password and devices > names are correct, password has nothing but alphanumerics, and “ssh > weylin@my-switch” login works fine from the rancid account on the same > server. > > > > [rancid@nsgv-prod-59 ~]$ read passwd > > ***********redacted > > [rancid@nsgv-prod-59 ~]$ clogin -u weylin -p $passwd my-switch > > my-switch > > spawn ssh -2 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null > -o LogLevel=ERROR -c > aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc > -x -l weylin my-switch > > Password: > > Password: > > > > Error: Couldn't login: my-switch > > [rancid@nsgv-prod-59 ~]$ clogin -V > > rancid 3.4.1 > > [rancid@nsgv-prod-59 ~]$ > > > > > > > > > > > > [image: signature_1593189312] > > > > *Weylin Piegorsch *| Manager, Network Engineering > > Boston University Information Services & Technology > [email protected] | 617.353.8128 | bu.edu/tech <http://www.bu.edu/tech> > > *Listen. Learn. Lead.* > > > > > > > > > _______________________________________________ > Rancid-discuss mailing list > [email protected] > https://www.shrubbery.net/mailman/listinfo/rancid-discuss >
_______________________________________________ Rancid-discuss mailing list [email protected] https://www.shrubbery.net/mailman/listinfo/rancid-discuss
