mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: gurre@start.no, Rob Landley <landley@trommello.org>
Cc: Aaron Lehmann <aaronl@vitelus.com>,
	Jeff Garzik <jgarzik@mandrakesoft.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	linux-kernel@vger.kernel.org
Subject: Re: ssh primer (was Re: pull vs push (was Re: [bk patch] Make cardbus compile in -pre4))
Date: Thu, 14 Feb 2002 07:50:41 -0600 (CST)	[thread overview]
Message-ID: <200202141350.HAA29931@tomcat.admin.navo.hpc.mil> (raw)

------HEADER END-DONT REMOVE------ 
> Rob Landley <landley@trommello.org> writes:
> 
> > Not that it's worth it. Keys get exponentially more difficult to
> > brute force as the key length increases. I read part of a book a
> > long time ago (might have been called "applied cryptography") that
> > figured out that if you could build a perfectly efficient computer
> > that could do 1 bit's worth of calculation with the the amount of
> > energy in the minimal electron state transition in a hydrogen atom,
> > and you built a dyson sphere around the sun to capture its entire
> > energy output for the however many billion years its expected to
> > last, you wouldn't even brute-force exhaust a relatively small
> > keyspace (128 bits? 256 bits? Something like that).
> >
> > Somebody else here is likely to recognize the above anecdote and give a more 
> > accurate reference.  Book title and page number would be good...
> 
> Bruce Schneier's "Applied Cryptography" (second edition, may be in the
> first edition as well), pages 157-158 ("Thermodynamic Limitations").
Remember - this is a dated example, since some theories are beginning
to consider storing & computing data with photons/interference patterns...
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil
Any opinions expressed are solely my own.

             reply	other threads:[~2002-02-14 13:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-14 13:50 Jesse Pollard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-10  0:36 pull vs push (was Re: [bk patch] Make cardbus compile in -pre4) Herbert Xu
2002-02-10  0:54 ` ssh primer (was Re: pull vs push (was Re: [bk patch] Make cardbus compile in -pre4)) Jeff Garzik
2002-02-10  0:59   ` Herbert Xu
2002-02-10  1:24     ` Jeff Garzik
2002-02-10  8:13       ` Herbert Xu
2002-02-13 17:13       ` Aaron Lehmann
2002-02-14  0:22         ` Rob Landley
2002-02-14  6:57           ` Aaron Lehmann
2002-02-14 11:00           ` Harald Arnesen
2002-02-10  0:59   ` Ben Pfaff
2002-02-10  1:14   ` David Lang

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=200202141350.HAA29931@tomcat.admin.navo.hpc.mil \
    --to=pollard@tomcat.admin.navo.hpc.mil \
    --cc=aaronl@vitelus.com \
    --cc=gurre@start.no \
    --cc=herbert@gondor.apana.org.au \
    --cc=jgarzik@mandrakesoft.com \
    --cc=landley@trommello.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®