Conversation

Notices

1. Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca (bobjonkmanformer@sn.jonkman.ca)'s status on Saturday, 01-Oct-2016 09:16:26 UTC Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca

   • Cryptography
   • GnuPG - GNU Privacy Guard
   • Lance Adams
   • Tom K
   @ladams@gs.sdf.org You're not using a mere 4 octets to identify a GnuPG key, are you? Recently I learned that short keyID collisions are now trivial to create, and the keyservers are full of fake short keyIDs. Please check out https://lkml.org/lkml/2016/8/15/445 and https://news.ycombinator.com/item?id=12296974 !crypto !GnuPG /cc @thomask@gs.sdf.org
   • ghostDancer likes this.
   • Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca (bobjonkmanformer@sn.jonkman.ca)'s status on Saturday, 01-Oct-2016 18:07:19 UTC Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca

     • GnuPG - GNU Privacy Guard
     • lnxw48 (Linux Walt)
     Fixed! Thanx! My !GnuPG Key fingerprint = 04F7 742B 8F54 C40A E115 26C2 B912 89B0 D2CC E5EA
     ghostDancer likes this.
   • Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca (bobjonkmanformer@sn.jonkman.ca)'s status on Sunday, 09-Oct-2016 07:22:00 UTC Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca

     • Cryptography
     • GnuPG - GNU Privacy Guard
     • zlg
     @zlg Full !GnuPG fingerprints are best, long KeyIDs (8 octets) are still good, short KeyIDs are definitely broken. I wonder how long it will take for an arbitrary 8-octet #KeyID to be easily generated... !crypto