Are Keybase.io generated GPG keys vulnerable to the ROCA CVE?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
https://crocs-muni.github.io/roca/
TL;DR Keys generated by certain (Infineon) hardware devices are easily reversible to generate a private key from only public key material. If an OS or browser uses any hardware assisted encryption it could produce a vulnerable key (this is conjecture). This only applies to keys <4096 bits, though they assume if generated on the same hardware those may also be vulnerable, they just require extremely expensive amounts of CPU and more time than is feasible to test with current hardware.
I don't know if you guys use an HSM or anything to accelerate key generation or if they are generated client side, but it might be good to scan the public keys on Keybase and alert potentially vulnerable users. See the article on services available to test whether keys are in fact vulnerable.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked ROCA advisory and determine whether Keybase-generated keys use affected Infineon hardware or another hardware-assisted generation path. Done would require confirming or disproving the vulnerability and defining whether scanning public keys and alerting potentially affected users is appropriate.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100