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
I have many SSH keys and the step of putting IdentitiesOnly in the .ssh/config is entirely do-able in most situations, but feels like it might help reduce friction if there were an option to have SSH keys coming in checked against the known set of keys and rejected if there were no users with a given key.
It doesn't look like it'd be that hard to implement (at the SSH server layer - don't allow through any key coming in, tell the server to go to the next auth method)... but I don't want to try implementing something if this is a design issue.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have many SSH keys and the step of putting IdentitiesOnly in the .ssh/config is entirely do-able in most situations, but feels like it might help reduce friction if there were an option to have SSH keys coming in checked against the known set of keys and rejected if there were no users with a given key.
It doesn't look like it'd be that hard to implement (at the SSH server layer - don't allow through any key coming in, tell the server to go to the next auth method)... but I don't want to try implementing something if this is a design issue.
Beta Was this translation helpful? Give feedback.
All reactions