From: “A. Padgett Peterson P.E. Information Security” <PADGETT@hobbes.orl.mmc.com>
To: cypherpunks@toad.com
Message Hash: c16190ff8e8fdd42e9e69f8834fbc2a93bdfcbde506362e7cd30ab7499586605
Message ID: <960303193329.2020177f@hobbes.orl.mmc.com>
Reply To: N/A
UTC Datetime: 1996-03-04 03:16:59 UTC
Raw Date: Mon, 4 Mar 1996 11:16:59 +0800
From: "A. Padgett Peterson P.E. Information Security" <PADGETT@hobbes.orl.mmc.com>
Date: Mon, 4 Mar 1996 11:16:59 +0800
To: cypherpunks@toad.com
Subject: Third Generation Problems
Message-ID: <960303193329.2020177f@hobbes.orl.mmc.com>
MIME-Version: 1.0
Content-Type: text/plain
Bill rites:
>Duress codes need to be designed to minimized the chance of such responses
>when they are used.
Absolutely but is a third generation problem:
First generation: being able to protect the information (encryption)
Second Generation: being able to respond to risks (duress) incurred by the
first generation solution (duress codes)
Third Generation: being able to respond to risks incurred by using the second
generation response (using the duress codes).
Is nice to plan for each up front but often the succeding generation risks
only become apparent after living with the preceeding generation solution
for a while. This should not prevent anyone from implementing the first
because of what *might* happen in the second. "Doing nothing" is a sound
solution only for politicians.
Besides the purpose of "duress codes" is not just to provide an avenue for
use in case of threat, it is also to deter the threat in the first place
by reducing the "win" probability for those who might issue the threat.
(previously mentioned a very real consideration for the fifth amendment. will
not repeat.)
Warmly,
Padgett
Return to March 1996
Return to ““A. Padgett Peterson P.E. Information Security” <PADGETT@hobbes.orl.mmc.com>”
1996-03-04 (Mon, 4 Mar 1996 11:16:59 +0800) - Third Generation Problems - “A. Padgett Peterson P.E. Information Security” <PADGETT@hobbes.orl.mmc.com>