mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Schwartz" <davids@webmaster.com>
To: "tabris" <tabris@tabris.net>, "Hunt, Adam" <ahunt@solvone.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: SecuriKey
Date: Mon, 12 Jan 2004 12:37:06 -0800	[thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKAEDHJHAA.davids@webmaster.com> (raw)
In-Reply-To: <200401111446.27403.tabris@tabris.net>


> 	How do you generate a one-time-pad? a one time pad must be
> by definition
> truly random, and be used only once. and if you can send the Securikey
> via a secure channel at the same time as the message, then you don't need
> the OTP.

	To truly qualify as an OTP, the data would have to be random, used once,
and somehow securely transfered to both ends of what will be the secure
channel. This is, shall we say politely, seldom done for modern
cryptography.

	However, many modern encryption schemes do require data that must be
unpredictable. If you want to encrypt a message using RSA, you generally use
a random key for a symmetric cypher and use RSA to protect the random key
rather than the (usually larger) message itself.

> 	I should also mention that the problem with 'generating' an
> OTP via any
> mechanical or algorithmic means is impossible as at best an OTP will only
> be pseudo-random, and therefore with identical inputs (assuming it is
> possible, which we can assume here for the sake of theory and security),
> the same OTP can be generated, thus breaking our assumption/necessity of
> non-deterministic output.

	Except we don't live in a deterministic world, we live in a quantum world.
It is nearly trivial to mechanically produce data that is truly random. All
you need is a reverse biased zener diode.

	Even if you do believe the world is deterministic, against the weight of
modern science, I really doubt you believe that anyone outside a sealed box
can predict microscopic zone temperature variations within a box and
therefore predict the phase jitter between two crystal oscillators inside
it.

	DS



  parent reply	other threads:[~2004-01-12 20:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-11 15:44 SecuriKey Hunt, Adam
2004-01-11 19:46 ` SecuriKey tabris
2004-01-12  0:39   ` High Quality Random sources, was: SecuriKey Stephen D. Williams
2004-01-12  3:38     ` tabris
2004-01-12  3:47       ` tabris
2004-01-12  4:10         ` Stephen D. Williams
2004-01-12  5:57           ` Valdis.Kletnieks
2004-01-12  6:19             ` Stephen D. Williams
2004-01-12  4:16     ` Mark Borgerding
2004-01-12 20:37   ` David Schwartz [this message]
2004-01-12 21:27     ` SecuriKey Richard B. Johnson

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=MDEHLPKNGKAHNMBLJOLKAEDHJHAA.davids@webmaster.com \
    --to=davids@webmaster.com \
    --cc=ahunt@solvone.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tabris@tabris.net \
    /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®