public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: kashani <kashani-list@badapple.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] My last words on cryptology and cryptography.
Date: Thu, 26 Jun 2008 11:35:06 -0700	[thread overview]
Message-ID: <4863E15A.80009@badapple.net> (raw)
In-Reply-To: <200806261054.43706.alan.mckinnon@gmail.com>

Alan McKinnon wrote:
> The calculation is quite simple - measure how quickly a specific 
> computer can match keys. Divide this into the size of the keyspace. The 
> average time to brute force a key is half that value. AFAIK this still 
> averages out at enormous numbers of years, even at insane calculation 
> rates like what RoadRunner can achieve.

256 bit keys. The 
115792089237316195423570985008687907853269984665640564039457584007913129639936 
keys are quite a lot to check (although, if all the atoms in the 
universe [estimated 10^78] were to test 1 key/sec, it'd only take about 
0.1157920892 seconds). However.. 512 bit keys with all the atoms testing 
a trillion keys/second would take about 
(2^512)/(10^78)/60/60/24/(36525/100)/(10^12) or 4.2486779507765473608e56 
years..

	I submit that brute forcing an AES key of reasonably length is 
currently impossible in an amount of time that would matter to the human 
race.

kashani
-- 
gentoo-user@lists.gentoo.org mailing list



  reply	other threads:[~2008-06-26 18:35 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-25  2:20 [gentoo-user] loop-aes + extra-ciphers Chris Walters
2008-06-25  5:43 ` Dirk Heinrichs
2008-06-25 13:20 ` Daniel Iliev
2008-06-25 15:14   ` Chris Walters
2008-06-25 18:51     ` Sebastian Wiesner
2008-06-25 20:25       ` Chris Walters
2008-06-25 21:24         ` Sebastian Wiesner
2008-06-25 21:53           ` Jason Rivard
2008-06-25 22:10             ` Sebastian Wiesner
2008-06-26  2:22               ` [gentoo-user] My last words on cryptology and cryptography Chris Walters
2008-06-26  8:54                 ` Alan McKinnon
2008-06-26 18:35                   ` kashani [this message]
2008-06-26 21:52                     ` Steven Lembark
2008-06-27  0:06                       ` kashani
2008-06-27 13:04                       ` Sebastian Wiesner
2008-06-26 20:14                   ` Sebastian Wiesner
2008-06-26 20:39                     ` Alan McKinnon
2008-06-26 22:10                       ` [gentoo-user] h Volker Armin Hemmann
2008-06-26 22:47                         ` Sebastian Günther
2008-06-26 23:37                           ` Neil Bothwick
2008-06-27  9:44                             ` Stroller
2008-06-27 10:08                               ` Neil Bothwick
2008-06-27 13:48                                 ` Alan McKinnon
2008-06-27 22:00                                   ` Chris Walters
2008-06-27 20:26                                 ` Daniel Iliev
2008-06-27  0:16                           ` Volker Armin Hemmann
2008-06-27  0:28                           ` kashani
2008-06-27  8:51                             ` Alan McKinnon
2008-06-27  8:59                               ` Neil Bothwick
2008-06-27 13:21                             ` Sebastian Wiesner
2008-06-27  8:42                         ` Alan McKinnon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4863E15A.80009@badapple.net \
    --to=kashani-list@badapple.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox