undefined | Better HN

0 pointsschoen10y ago0 comments

Wait a minute, I get a different n value by downloading that key and running gpg --list-keys --with-key-data on it.

You have one ending in 131307671292149646652772992033083 and I have one ending in 726103552998367994727700722491707 that is not divisible by 231.

0 comments

asciilifeform10y ago

The key as seen by Phuctor had three sub-keys, one of which was an RSA key which turned out to be factorable.

schoenOP10y ago

Sorry, I was looking at the other one. But something is still very, very odd. (1) Two of the subkeys agree with one another for hundreds of digits and then disagree. (2) I did gpg --recv-key 51221121 and I got a key back from the keyserver with fingerprint 7EAA C969 3E7D 2205 46BE 576C BDA0 6085 493B ACE4 (only, no other keys) -- which doesn't match the key ID that it should, and is seemingly missing the vulnerable subkey entirely.

schoenOP10y ago

Can you post the ASCII-armored key that you have? I am getting a radically different key from the keyservers, and I wonder if there could be some kind of keyserver attack or misbehavior involved here too.

j / k navigate · click thread line to collapse

0 pointsschoen10y ago0 comments

Wait a minute, I get a different n value by downloading that key and running gpg --list-keys --with-key-data on it.

You have one ending in 131307671292149646652772992033083 and I have one ending in 726103552998367994727700722491707 that is not divisible by 231.

0 comments

asciilifeform10y ago

The key as seen by Phuctor had three sub-keys, one of which was an RSA key which turned out to be factorable.

schoenOP10y ago

j / k navigate · click thread line to collapse