Mailing List Archive

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 .
-andreas

On Tue, May 2, 2023 at 10:10?PM Piegorsch, Weylin William <weylin@bu.edu>
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
> weylin@bu.edu | 617.353.8128 | bu.edu/tech <http://www.bu.edu/tech>
>
> *Listen. Learn. Lead.*
>
>
>
>
>
>
>
>
> _______________________________________________
> Rancid-discuss mailing list
> Rancid-discuss@www.shrubbery.net
> https://www.shrubbery.net/mailman/listinfo/rancid-discuss
>

what happens if you try this from the cmd line?
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

maybe add a couple of -v to get debug data.



On Wed, May 3, 2023 at 1:10?AM Piegorsch, Weylin William <weylin@bu.edu>
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
> weylin@bu.edu | 617.353.8128 | bu.edu/tech <http://www.bu.edu/tech>
>
> *Listen. Learn. Lead.*
>
>
>
>
>
>
>
>
> _______________________________________________
> Rancid-discuss mailing list
> Rancid-discuss@www.shrubbery.net
> https://www.shrubbery.net/mailman/listinfo/rancid-discuss
>

Thanks. I had that thought too, so I made sure first that I wasn’t using any special characters. There are no non-alphanumeric characters in the password I’m using - no spaces, quotes, emojis, wingdings etc.





[signature_1593189312]

Weylin Piegorsch | Manager, Network Engineering
Boston University Information Services & Technology
weylin@bu.edu<mailto:weylin@bu.edu> | 617.353.8128 | bu.edu/tech<http://www.bu.edu/tech>
Listen. Learn. Lead.




From: Andreas Ott <andreas@naund.org>
Sent: Wednesday, May 3, 2023 12:41 PM
To: rancid-discuss@sea.shrubbery.net
Cc: Piegorsch, Weylin William <weylin@bu.edu>
Subject: Re: [rancid] Unable to Login via clogin

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 .
-andreas

On Tue, May 2, 2023 at 10:10?PM Piegorsch, Weylin William <weylin@bu.edu<mailto:weylin@bu.edu>> 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 ~]$





[signature_1593189312]

Weylin Piegorsch | Manager, Network Engineering
Boston University Information Services & Technology
weylin@bu.edu<mailto:weylin@bu.edu> | 617.353.8128 | bu.edu/tech<http://www.bu.edu/tech>
Listen. Learn. Lead.




_______________________________________________
Rancid-discuss mailing list
Rancid-discuss@www.shrubbery.net<mailto:Rancid-discuss@www.shrubbery.net>
https://www.shrubbery.net/mailman/listinfo/rancid-discuss

Using SSH, works fine. Using clogin with the same username/password using the -u and -p flags, can’t login.





[signature_1593189312]

Weylin Piegorsch | Manager, Network Engineering
Boston University Information Services & Technology
weylin@bu.edu<mailto:weylin@bu.edu> | 617.353.8128 | bu.edu/tech<http://www.bu.edu/tech>
Listen. Learn. Lead.




From: Aaron Dudek <adudek16@gmail.com>
Sent: Wednesday, May 3, 2023 1:12 PM
To: Piegorsch, Weylin William <weylin@bu.edu>
Cc: rancid-discuss@www.shrubbery.net
Subject: Re: [rancid] Unable to Login via clogin

what happens if you try this from the cmd line?
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

maybe add a couple of -v to get debug data.



On Wed, May 3, 2023 at 1:10?AM Piegorsch, Weylin William <weylin@bu.edu<mailto:weylin@bu.edu>> 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 ~]$





[signature_1593189312]

Weylin Piegorsch | Manager, Network Engineering
Boston University Information Services & Technology
weylin@bu.edu<mailto:weylin@bu.edu> | 617.353.8128 | bu.edu/tech<http://www.bu.edu/tech>
Listen. Learn. Lead.




_______________________________________________
Rancid-discuss mailing list
Rancid-discuss@www.shrubbery.net<mailto:Rancid-discuss@www.shrubbery.net>
https://www.shrubbery.net/mailman/listinfo/rancid-discuss

add debugging to the clogin script

On Wednesday, May 3, 2023, Piegorsch, Weylin William <weylin@bu.edu> wrote:

> Using SSH, works fine. Using clogin with the same username/password using
> the -u and -p flags, can’t login.
>
>
>
>
>
>
>
>
>
>
>
> [image: signature_1593189312]
>
>
>
> *Weylin Piegorsch *| Manager, Network Engineering
>
> Boston University Information Services & Technology
> weylin@bu.edu | 617.353.8128 | bu.edu/tech <http://www.bu.edu/tech>
>
> *Listen. Learn. Lead.*
>
>
>
>
>
>
>
>
>
> *From:* Aaron Dudek <adudek16@gmail.com>
> *Sent:* Wednesday, May 3, 2023 1:12 PM
> *To:* Piegorsch, Weylin William <weylin@bu.edu>
> *Cc:* rancid-discuss@www.shrubbery.net
> *Subject:* Re: [rancid] Unable to Login via clogin
>
>
>
> what happens if you try this from the cmd line?
>
> 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
>
>
>
> maybe add a couple of -v to get debug data.
>
>
>
>
>
>
>
> On Wed, May 3, 2023 at 1:10?AM Piegorsch, Weylin William <weylin@bu.edu>
> 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
> weylin@bu.edu | 617.353.8128 | bu.edu/tech <http://www.bu.edu/tech>
>
> *Listen. Learn. Lead.*
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Rancid-discuss mailing list
> Rancid-discuss@www.shrubbery.net
> https://www.shrubbery.net/mailman/listinfo/rancid-discuss
>
>

Good question, I’m not claiming to be expert on reading the output but I’m not seeing anything glaring. It’s almost like clogin isn’t using my password





[signature_1593189312]

Weylin Piegorsch | Manager, Network Engineering
Boston University Information Services & Technology
weylin@bu.edu<mailto:weylin@bu.edu> | 617.353.8128 | bu.edu/tech<http://www.bu.edu/tech>
Listen. Learn. Lead.




From: Aaron Dudek <adudek16@gmail.com>
Sent: Wednesday, May 3, 2023 4:41 PM
To: Piegorsch, Weylin William <weylin@bu.edu>
Cc: rancid-discuss@www.shrubbery.net
Subject: Re: [rancid] Unable to Login via clogin

add debugging to the clogin script

On Wednesday, May 3, 2023, Piegorsch, Weylin William <weylin@bu.edu<mailto:weylin@bu.edu>> wrote:
Using SSH, works fine. Using clogin with the same username/password using the -u and -p flags, can’t login.





[signature_1593189312]

Weylin Piegorsch | Manager, Network Engineering
Boston University Information Services & Technology
weylin@bu.edu<mailto:weylin@bu.edu> | 617.353.8128 | bu.edu/tech<http://www.bu.edu/tech>
Listen. Learn. Lead.




From: Aaron Dudek <adudek16@gmail.com<mailto:adudek16@gmail.com>>
Sent: Wednesday, May 3, 2023 1:12 PM
To: Piegorsch, Weylin William <weylin@bu.edu<mailto:weylin@bu.edu>>
Cc: rancid-discuss@www.shrubbery.net<mailto:rancid-discuss@www.shrubbery.net>
Subject: Re: [rancid] Unable to Login via clogin

what happens if you try this from the cmd line?
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

maybe add a couple of -v to get debug data.



On Wed, May 3, 2023 at 1:10?AM Piegorsch, Weylin William <weylin@bu.edu<mailto:weylin@bu.edu>> 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 ~]$





[signature_1593189312]

Weylin Piegorsch | Manager, Network Engineering
Boston University Information Services & Technology
weylin@bu.edu<mailto:weylin@bu.edu> | 617.353.8128 | bu.edu/tech<http://www.bu.edu/tech>
Listen. Learn. Lead.




_______________________________________________
Rancid-discuss mailing list
Rancid-discuss@www.shrubbery.net<mailto:Rancid-discuss@www.shrubbery.net>
https://www.shrubbery.net/mailman/listinfo/rancid-discuss

Thu, May 04, 2023 at 12:53:22PM +0000, Piegorsch, Weylin William:
> Good question, I’m not claiming to be expert on reading the output but I’m not seeing anything glaring. It’s almost like clogin isn’t using my password
>

if you privately share your cloginrc with me, I'll help you debug it:
clogin -m <hostname>
and redact the passwords.

> Using SSH, works fine. Using clogin with the same username/password using the -u and -p flags, can’t login.

> [rancid@nsgv-prod-59 ~]$ clogin -V
> rancid 3.4.1

_______________________________________________
Rancid-discuss mailing list
Rancid-discuss@www.shrubbery.net
https://www.shrubbery.net/mailman/listinfo/rancid-discuss