Ssh 2 fa support #973
Open
Ssh 2 fa support #973
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
julienfr112
force-pushed
the
ssh-2FA-support
branch
from
315e16d
to
def83a4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The server i'm working with has a bastion that need a yubikey old "One Time Password" with a ssh interactive session. It does not work out of box with pyinfra, so I propose this pull requests.
It's a fallback on connect, when there is a BadAuthenticationType, in my case when the authenfication is interactive. In this case, the solution I found is working with Transport, doing first an "auth_interactive_dumb", that just link the session and stdin stdout, and then a auth_publikey. I've tested it and it work perfectly in my case, without breaking anything. I'm not sure though how generic is my use case.
Thanks again for you good work on pyinfra, that's amazing stuff.