Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimize the priority of the ssh authentication methods #31

Closed
windvalley opened this issue Feb 9, 2022 · 0 comments
Closed

Optimize the priority of the ssh authentication methods #31

windvalley opened this issue Feb 9, 2022 · 0 comments
Labels
optimization Optimization or adjustment

Comments

@windvalley
Copy link
Owner

Now, there are three authentication methods: password, pubkey, ssh-agent.
If the 3 auth methods are all valid, the current priority order is password > pubkey > ssh-agent.
But I think a more reasonable order should be: ssh-agent > pubkey > password. The next gossh version will adjust the order to this.

Tips:
You can observe the actual authentication method used from the /var/log/secure file of the target host.

tail -f /var/log/secure
@windvalley windvalley added the optimization Optimization or adjustment label Feb 9, 2022
windvalley added a commit that referenced this issue Feb 9, 2022
Optimize priority for auth methods defined in inventory, and fix a bug
about ssh-agent auth for proxy server.
windvalley added a commit that referenced this issue Feb 11, 2022
Bug description:

When attempting ssh-agent fails, pubkey authentication is skipped and password authentication is used directly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
optimization Optimization or adjustment
Projects
None yet
Development

No branches or pull requests

1 participant