feat: PreferredAuthentications #189
Merged
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
caarlos0
changed the title
aymanbagabas
approved these changes
May 31, 2023
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.
This adds support for the
PreferredAuthenticationsSSH option.Wishlist will then try to respect the endpoint's configuration, both for remote and local clients.
Supported methods are:
none(implicit),publickey(with and without agents),passwordandkeyboard-interactive.Default methods are:
none,publickey,keyboard-interactive1closes #186
Footnotes
passwordis not the default because the way it works oncrypto/ssh: we must know the password before creating the passwordssh.AuthMethod, so, if we were to add it as a default, we would have to ask for the password every time, even for endpoints that do not support it ↩