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 19 March 2023
      A very thoughtful analysis. I've been on the side of "peace from both sides", but I can see the progression that you lay out.
    • bobjonkman repeated a notice by lnxw48a1 19 March 2023
      RT @lnxw48a1 https://www.bbc.co.uk/news/world-europe-64986744 [www bbc co uk] #Turkiye leader Erdogan signals approval of #Finland joining #NATO ... still hesitant on #Sweden's application After the fall of the USSR, I was in favor of abolishing NATO. Frankly, I was too idealistic. I imagined Europe becoming a sort of demilitarized zone but without conflicting armies on each […]
    • Favorite 19 March 2023
      bobjonkman favorited something by lnxw48a1: https://www.bbc.co.uk/news/world-europe-64986744 [www bbc co uk] #Turkiye leader Erdogan signals approval of #Finland joining #NATO ... still hesitant on #Sweden's application After the fall of the USSR, I was in favor of abolishing NATO. Frankly, I was too idealistic. I imagined Europe becoming a sort of demilitarized zone but without conflicting […]
    • New note by bobjonkman 19 March 2023
      There's a natural spring just a short distance from here. Sometime about 30 years ago some kind of piping was added to it, so now the water comes out of a pipe a distance above the ground. People would fill their water cooler bottles there. About 10 years ago a sign was put up "This […]
    • bobjonkman repeated a notice by lnxw48a1 19 March 2023
      RT @lnxw48a1 Behind this laundromat there is a pipe that continuaously spews water. People drive up and fill bottles, then leave. Trusting. I naturally assume that there is some contaminant and I therefore avoid drinking water from mystery pipes.
    • New note by bobjonkman 19 March 2023
      Why we need elastomeric clothing.
    • New note by bobjonkman 19 March 2023
      The only reason I have a Github account is to provide bug reports and feature requests to projects I want to support. I don't code much, but anything I want to be publicly available is on my own website. Although not in a code repository, which is probably a good idea.
    • bobjonkman repeated a notice by steve 18 March 2023
      RT @steve From https://t.co/Ljk2FwSC2I on Mastodon: In the spirit of deepening the open federated social web, this blog is now powered by ActivityPub, the open federated social standard. This is thanks to the WordPress plugin “activitypub”. You c... https://mastodon.cooleysekula.net/users/steve/statuses/110044125471741899/activity
    • Favorite 18 March 2023
      bobjonkman favorited something by steve: From https://t.co/Ljk2FwSC2I on Mastodon: In the spirit of deepening the open federated social web, this blog is now powered by ActivityPub, the open federated social standard. This is thanks to the WordPress plugin “activitypub”. You c... https://mastodon.cooleysekula.net/users/steve/statuses/110044125471741899/activity
    • Favorite 3 March 2023
      bobjonkman favorited something by clacke: Re: nu.federati.net/notice/3422215@LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} A lot of people move to Fedi from Twitter, in Fedi numbers.Not a lot of people move to Fedi from Twitter in Twitter numbers.

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