You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 19, 2022. It is now read-only.
This is a rather silly edge case, but I figured I would see if anyone else has come across it. I use authy-ssh to secure my login with 2FA. When I attempt to deploy to a server with this enabled, the dialog hangs.
$ knife solo cook stephen@<my-node>
Running Chef on <my-node>...
Checking Chef version...
My assumption is that the prompt isn't being routed out into view. A normal login:
$ ssh <my-node>
Authy Token (type 'sms' to request a SMS token): 12345678
Good job! You've securely logged in with Authy.$
The text was updated successfully, but these errors were encountered:
Interesting! I may have to try that out. I do notice there's a section here about disabling it for chef, so could be a lost cause, but if you can manage to get Net::SSH & rsync handling the 2FA, then we can probably patch that into knife-solo (ultimately knife-solo is just a wrapper around both).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is a rather silly edge case, but I figured I would see if anyone else has come across it. I use
authy-ssh
to secure my login with 2FA. When I attempt to deploy to a server with this enabled, the dialog hangs.My assumption is that the prompt isn't being routed out into view. A normal login:
The text was updated successfully, but these errors were encountered: