This Blog Is Not For Reading

A blog, just like any blog, only more so

  • Subscribe

  • Categories

  • RSS Bob Jonkman’s Microblog

    • New note by bobjonkman 24 September 2022
      I have not yet stopped chuckling...
    • Favorite 24 September 2022
      bobjonkman favorited something by clacke: It is impossible to decipher in how many layers if sarcasm this is written. It's glorious.decrypt.co/6234/curry-with-dav…
    • bobjonkman repeated a notice by clacke 24 September 2022
      RT @clacke It is impossible to decipher in how many layers if sarcasm this is written. It's glorious. decrypt.co/6234/curry-with-dav…
    • New note by bobjonkman 9 July 2022
      New Zealand #ProportionalRepresentation
    • Favorite 9 July 2022
      bobjonkman favorited something by blacksam: What country do Canadians threaten to move to when they don't like election outcomes? #politics #canada
    • bobjonkman repeated a notice by blacksam 9 July 2022
      RT @blacksam What country do Canadians threaten to move to when they don't like election outcomes? #politics #canada
    • New note by bobjonkman 5 July 2022
      Congratulations to Dr. Cooley, and to you! And welcome to Canada!https://twitter.com/SNOLABscience/status/1542562373193633793 I saw the news on Twitter, and said to myself "Hey, I know that person!" It's amazing how familiar we humans feel with each other using only social media...
    • bobjonkman repeated a notice by steve 5 July 2022
      RT @steve Spring Cleaning, Except its Packing to Move to Canada https://steve.cooleysekula.net/blog/2022/07/02/spring-cleaning-except-its-packing-to-move-to-canada/
    • Favorite 5 July 2022
      bobjonkman favorited something by steve: Spring Cleaning, Except its Packing to Move to Canada https://steve.cooleysekula.net/blog/2022/07/02/spring-cleaning-except-its-packing-to-move-to-canada/
    • New note by bobjonkman 26 June 2022
      I've never played #Minecraft - Is this #Federated software? Is it #FreeSoftware? If so, how can Microsoft control what's happening on someone's private server? Even if such code existed in a #FreeSoftware application, I would have thought there'd be a fork that eliminates that external control. It's time for that now. But if #Minecraft isn't […]

The cost of long GnuPG/PGP keys

Posted by Bob Jonkman on 25th March 2014

Never Eat That Green Food At The Back Of The Fridge

Never Trust Anyone Over Thirty

and

Never Sign A GnuPG/PGP Key That’s Older Than You Are

Face peeking into fridge

Looking for green food at the back of the fridge

OK, only one of those is true, and it’s not the last one. At the University of Waterloo Keysigning Party last fall, some of the people signing my key were younger than the key they were signing!

At the keysigning I was having a discussion with someone about key lengths. In particular, choosing 4096 bits instead of 2048. I was reading that GnuPG has a limit of 4096 bits, but that 4096 should be enough for all time to come.

I’ve read online that GnuPG does actually support larger key sizes but that there is a const in the source code limiting it to 4096. The reasons for doing so are supposedly speed, 4096 would be very slow to generate and use, and comparability with other implementations that may not support larger keys. Personally I think it’s an inevitability that this will be increased in time but we’re not there yet.

In 1996 when I started with PGP a 1024 bit key was considered adequate, by 1999 a 2048 bit key was still considered large.

Consider Moore’s Law: every 18 months computing capacity doubles and costs halve. I’m not sure if that means that over 18 months x flops increases to 2x flops at the same price, or that in 18 months the cost of x flops is half of today’s cost, or if it means that in 18 months the cost of 2x flops will be half the cost of x flops today. If the latter, then today’s x flops/$ is x/4 flops/$ in 18 months. That factor of four is an increase of two bits every 18 months, or four bits every 3 years.

So, the cost in 1996 to brute-force crack a 1024 bit key is the same as the cost in 1999 to crack a 1028 bit key. And in 2014, 18 years later, it’s the same cost as cracking a 1048 bit key (an additional 24 bits).

An increase in key size from 1024 bits to 2048 bits buys an additional 768 years of Moore’s Law. And going from 2048 bits to 4096 bits buys an additional 1536 years of Moore’s Law.

Is Moore’s Law overestimating the cost of cracking keys? Are there fundamental advances in math that have dropped the cost of cracking 1024 bit keys to near-zero? What’s the economic justification for crippling keysizes in GnuPG, anyway?

–Bob, who is not trolling but really wants to know.

Day 57 / 365 – refrigerator by Jason Rogers is used under a CC BYCC BY license.

This post is based on a message to the KWCrypto Mailing List.

Tags: , , , , , , , , , ,
Posted in PGP/GPG | 1 Comment »

 
Better Tag Cloud