Enhanced OAuth security for SSH keys
We just added more granular permissions so third party applications can specifically request read-only access, read/write access, or full admin access to your public SSH keys. You’re in control As…
We just added more granular permissions so third party applications can specifically request read-only access, read/write access, or full admin access to your public SSH keys.
You’re in control
As always, when an application requests access to your account, you get to decide whether to grant that access or not.

Revoke with ease
In addition to these finer-grained permissions, we’re also making it easier to revoke SSH access to your data. If an OAuth application creates an SSH key in your account, we’ll automatically delete that key when you revoke the application’s access.

To help you track security events that affect you, we’ll still email you any time a new key is added to your account. And of course, you can audit and delete your SSH keys any time you like.
You can read about the new changes in more detail on the GitHub Developer site.
Tags:
Written by
Related posts
Your stack, your rules: Introducing custom agents in GitHub Copilot for observability, IaC, and security
Use partner-built Copilot agents to debug, secure, and automate engineering workflows across your terminal, editor, and github.com.
The ultimate gift guide for the developer in your life
Finding the perfect gift for your favorite developer is easy with our top tips.
Why developers still flock to Python: Guido van Rossum on readability, AI, and the future of programming
Discover how Python changed developer culture—and see why it keeps evolving.