3 ms·
This is exactly the problem. You need to revoke your key (maybe just one key, maybe lots of keys) but you can't revoke it from the new service, only from GitHub
by dmurray 5y ago
This is exactly the problem. You need to revoke your key (maybe just one key, maybe lots of keys) but you can't revoke it from the new service, only from GitHub, because the process of authorizing you to the new service was append-only.
- themacguffinman 5y agoIt's not append-only. No one is suggesting that any new service must only pull keys from GitHub once and then it never changes. GitHub is just a convenient source to bootstrap from. You might need to go into your new service (possibly through another factor like physical access or web admin) and manually revoke compromised keys. I just don't think any of this is a reason to have a separate key for each service you use, that still seems rather unnecessary.