1995-11-13 - Re: Timed-release crypto - Proactive security plug

Header Data

From: “Beavis B. Thoopit” <beavis@bioanalytical.com>
To: amir@watson.ibm.com (Amir Herzberg)
Message Hash: e75549b420bda450d6512bc552de11a6711f81a9053b3f37ab15436624c31cd7
Message ID: <199511132053.PAA01851@bioanalytical.com>
Reply To: <9511131904.AA21605@gimili.watson.ibm.com>
UTC Datetime: 1995-11-13 21:31:38 UTC
Raw Date: Tue, 14 Nov 1995 05:31:38 +0800

Raw message

From: "Beavis B. Thoopit" <beavis@bioanalytical.com>
Date: Tue, 14 Nov 1995 05:31:38 +0800
To: amir@watson.ibm.com (Amir Herzberg)
Subject: Re: Timed-release crypto - Proactive security plug
In-Reply-To: <9511131904.AA21605@gimili.watson.ibm.com>
Message-ID: <199511132053.PAA01851@bioanalytical.com>
MIME-Version: 1.0
Content-Type: text/plain


[...]

> A solution to this is proactive secret sharing, as described in [HJKY95].
> In this protocol, the secret shares are periodically refreshed (i.e. new
> shares are computed distributively and then the old shares are erased).
> In this manner, an attacker has to break into most servers during the same
> period; shares from one period are worthless on the next period.
> 
> Best, Amir
> 
> [HJKY95] `Proactive Secret Sharing', A. Herzberg, H. Krawczyk, S. Jareski,
> M. Yung, Crypto 95.

[...]

Here is an example of _dynamics_ being used to increase the security of
a logical protocol.  I believe that dynamics may be usable at a more micro
level to build a physical device that is expensive to compromise...





Thread