From: Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] h
Date: Fri, 27 Jun 2008 00:10:20 +0200 [thread overview]
Message-ID: <200806270010.20819.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <200806262239.42820.alan.mckinnon@gmail.com>
On Donnerstag, 26. Juni 2008, Alan McKinnon wrote:
> On Thursday 26 June 2008, Sebastian Wiesner wrote:
> > Alan McKinnon <alan.mckinnon@gmail.com> at Thursday 26 June 2008,
> > 10:54:43
> >
> > > 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.
> >
> > According to Wikipedia RoadRunner is designed for 1.7 petaflops in
> > peak. Assuming for the sake of simplicity, that decryption can be
> > performed within a single flop:
> >
> > (2^256) / (1.7 * 10^15) / 2 ~= 3.5 * 10^61
> >
> > In years:
> >
> > 3.5 * 10^61 / 3600 / 24 / 356 ~= 10^54
> >
> > Correct me if I'm wrong, but it seems impossible to me, to reduce
> > this get the required amount somewhere near to the life time of a
> > human being ;)
>
> Even with your ultra-liberal assumptions, it still comes out to:
>
> 1000000000000000000000000000000000000
>
> times longer than the entire universe is believed to have existed thus
> far (14 billion years). That is an unbelievable stupendously long
> period of time. Yeah, I'd agree that brute force is utterly unfeasible
> as a vector of attack. Not even the almighty NSA could ever pull that
> one off as there simply aren't enough atoms in the universe to make a
> supercomputer big enough.
>
> Numbers don't lie.
and this is why nobody uses brute force.
There a better ways to crack keys. NSA has tons of experts in mathematics and
cryptoanalysis. Plus very sophisticated hardware. I am sure for most ciphers
they use something much more efficient than stupid brute force.
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-06-26 22:11 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
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 ` Volker Armin Hemmann [this message]
2008-06-26 22:47 ` [gentoo-user] h 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=200806270010.20819.volker.armin.hemmann@tu-clausthal.de \
--to=volker.armin.hemmann@tu-clausthal.de \
--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