5 ms·

Newbie here. Can somebody summing up the implications of this? At first sight it seems terrible.

by marvel_boy 10y ago

viraptor 10y ago
Very small, unless you used some really weird/experimental software/hardware to generate your PGP key. What they keep finding is: keys that do not pass the first sanity test (very non-standard values and values which most likely come from memory corruption) and keys that share primes with other keys (most likely generated by broken or badly initialised PRNGs). The same class of issues has been found before on SSL certificates and SSH keys. (https://factorable.net/index.html https://factorable.net/index.html) It will get interesting people with affected keys can report back how they generated them and find something in common - maybe specific version of PGP / GPG was broken. You can submit your key via http://phuctor.nosuchlabs.com/ http://phuctor.nosuchlabs.com/ if you want to check your own key quickly.
- makomk 10y ago
  Most of the factors are much too short to be the result of broken/badly initialised PRNGs. The exceptions claim to belong to alice@example.com and txn@ti.com, and the TI ones aren't actually PGP keys at all - one is the 512-bit firmware signing key for the TI-83+ calculator which was factored the hard way a while back and another is a key someone's created sharing the same prime, most likely as a way of mocking TI. Other than those two pairs of obviously-fake keys, the rest are most likely just the result of keys being corrupted somewhere in the process of being uploaded to the keyserver.
  - MSRogers 10y ago
    > Most of the factors are much too short to be the result of broken/badly initialised PRNGs. How do you reason?
MSRogers 10y ago
It would seem that Windows and Apple implementations of RSA/PGP do not live up to standards. If you use either products you should probably check your keys.

5 ms·

Newbie here. Can somebody summing up the implications of this? At first sight it seems terrible.

by marvel_boy 10y ago

Newbie here. Can somebody summing up the implications of this? At first sight it seems terrible.

viraptor 10y ago
Very small, unless you used some really weird/experimental software/hardware to generate your PGP key. What they keep finding is: keys that do not pass the first sanity test (very non-standard values and values which most likely come from memory corruption) and keys that share primes with other keys (most likely generated by broken or badly initialised PRNGs). The same class of issues has been found before on SSL certificates and SSH keys. (https://factorable.net/index.html https://factorable.net/index.html) It will get interesting people with affected keys can report back how they generated them and find something in common - maybe specific version of PGP / GPG was broken. You can submit your key via http://phuctor.nosuchlabs.com/ http://phuctor.nosuchlabs.com/ if you want to check your own key quickly.
- makomk 10y ago
  Most of the factors are much too short to be the result of broken/badly initialised PRNGs. The exceptions claim to belong to alice@example.com and txn@ti.com, and the TI ones aren't actually PGP keys at all - one is the 512-bit firmware signing key for the TI-83+ calculator which was factored the hard way a while back and another is a key someone's created sharing the same prime, most likely as a way of mocking TI. Other than those two pairs of obviously-fake keys, the rest are most likely just the result of keys being corrupted somewhere in the process of being uploaded to the keyserver.
  - MSRogers 10y ago
    > Most of the factors are much too short to be the result of broken/badly initialised PRNGs. How do you reason?
MSRogers 10y ago
It would seem that Windows and Apple implementations of RSA/PGP do not live up to standards. If you use either products you should probably check your keys.