Allow to enable/disable SSH keys without deletion #193477
Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Product Feedback
Body
"For reasons" I have two SSH keys for two different GitHUB users (private and work account); but have both active for the same Linux user.
This can in some situations, e.g. in Vagrant VMs with SSH agent forwarding; lead to the wrong key, and so the wrong github users, being used.
Right now I "solve" this by deleting the offending key from the "wrong" Github user; then re-adding it again later.
It would be much more convenient in such situations to just disable the key registered with the github user; then later re-enable it again, instead of having to do the full "delete, then recreate and copy in the public key part into the webform" dance.
(I am aware of https://github.com/orgs/community/discussions/82748 but it doesn't really seem to be the same as what I am looking for)
Beta Was this translation helpful? Give feedback.
All reactions