This Blog Is Not For Reading

A blog, just like any blog, only more so

  • Subscribe

  • Categories

  • RSS Bob Jonkman’s Microblog

    • Favorite 2 January 2021
      bobjonkman favorited something by stigatle: Out enjoying a nice day with Marlyn and our kids. Love being outdoors:)
    • Favorite 26 December 2020
      bobjonkman favorited something by stigatle: Wish you all a great Christmas!
    • bobjonkman repeated a notice by steve 26 December 2020
      RT @steve Uncertainty Principle Podcast Episode 1: Isaac Newtons Pajamas Lots of people in history were born on this day. This reading of an article in the Washington Post remembers one of them, Isaac Newton, and his pandemic year. https://people.smu.edu/ssekula/2020/03/16/uncertainty-principle-podcast-episode-1-isaac-newtons-pajamas/
    • Favorite 26 December 2020
      bobjonkman favorited something by steve: Uncertainty Principle Podcast Episode 1: Isaac Newtons Pajamas Lots of people in history were born on this day. This reading of an article in the Washington Post remembers one of them, Isaac Newton, and his pandemic year. https://people.smu.edu/ssekula/2020/03/16/uncertainty-principle-podcast-episode-1-isaac-newtons-pajamas/
    • bobjonkman repeated a notice by rozzin 26 December 2020
      RT @rozzin Happy !gravmass, everyone!
    • Favorite 26 December 2020
      bobjonkman favorited something by rozzin: Happy !gravmass, everyone!
    • Favorite 24 December 2020
      bobjonkman favorited something by blacksam: Nothing puts me in the Christmas spirit like watching Ralphie slap the shit out of Scut Farkas. #chistmas
    • New note by bobjonkman 17 December 2020
      I was getting all enraged by Github removing from their site yet more software they don't agree with. It should be perfectly acceptable to have software that enhances privacy and gives users control over what's on their computers. If I want to use software that bans cookies, why should Github care? Cookie banners are perfectly […]
    • bobjonkman repeated a notice by geniusmusing 17 December 2020
      RT @geniusmusing No cookie for you The GitHub Blog https://github.blog/2020-12-17-no-cookie-for-you/ >Good news: we removed all cookie banners from GitHub! 🎉 > >No one likes cookie banners. But cookie banners are everywhere. So how did we pull this off? > >Well, EU law requires you to use cookie banners if your website contains cookies that are […]
    • New note by bobjonkman 6 December 2020
      That article (from 2018!) is just like reading a dystopian #SciFi novel, all newspeak and doublethink: "The chip also supports the Android Strongbox Keymaster module, including Trusted User Presence and Protected Confirmation" https://www.androidauthority.com/titan-m-security-chip-915888/

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 Crypto, PGP/GPG | 1 Comment »

 
Better Tag Cloud