1995-12-12 - Re: Timing Cryptanalysis Attack

Header Data

From: Peter Monta <pmonta@qualcomm.com>
To: cypherpunks@toad.com
Message Hash: 296fc2bc27ea14ef35609c84657700d0b541a62c4d3aeaf6339a0eca5a84e044
Message ID: <199512120056.QAA16055@mage.qualcomm.com>
Reply To: <199512111906.OAA01139@crypto.com>
UTC Datetime: 1995-12-12 05:05:05 UTC
Raw Date: Tue, 12 Dec 1995 13:05:05 +0800

Raw message

From: Peter Monta <pmonta@qualcomm.com>
Date: Tue, 12 Dec 1995 13:05:05 +0800
To: cypherpunks@toad.com
Subject: Re: Timing Cryptanalysis Attack
In-Reply-To: <199512111906.OAA01139@crypto.com>
Message-ID: <199512120056.QAA16055@mage.qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain


Matt Blaze writes:

> Of course, this works against a remote adversary, but not against one
> on the same machine who can look at actual CPU consumption (which doesn't
> increase when the target is blocked).

Maybe this is a good reason to spinwait, rather than sleep, until
the timer expires.  It would be pretty subtle to distinguish that
from "real" computation.

Peter Monta






Thread