From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] My last words on cryptology and cryptography.
Date: Thu, 26 Jun 2008 10:54:43 +0200 [thread overview]
Message-ID: <200806261054.43706.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <4862FD4F.8070303@comcast.net>
On Thursday 26 June 2008, Chris Walters wrote:
> Sebastian Wiesner wrote:
> | I don't and I did not say so, things like the Debian disaster bring
> | you back to reality from dreams ...
This is the favoured method of cracking encryption - misuse by the user.
The canonical example is of course Enigma and the stupid mistake that
let the Allies crack it. This is entirely analogous to the Debian
fiasco.
> With desktop computing power and speed growing at the rate that it
> currently is, does it stretch the imagination so much that
> supercomputer power and speed is also growing at a similar rate.
> Even if an AES256 key cannot be broken "in a million years" by one
> supercomputer (*I* would like to see a citation for that), there will
> soon be a time when it will be able to be cracked in a much shorter
> time - with one supercomputer.
No-one has ever seriously said that it will take X time to crack a key.
The possibility exists that the first key randomly selected in a brute
force attack will match which gives you a time to crack in the
millisecond range.
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.
All this presupposes that the algorithm in question has no known
cryptographic weaknesses so brute force is the only feasible method of
attack currently.
--
Alan McKinnon
alan dot mckinnon at gmail dot com
--
gentoo-user@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-06-26 8:54 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 [this message]
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 ` [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=200806261054.43706.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--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