From: “Perry E. Metzger” <perry@piermont.com>
To: bryce@digicash.com
Message Hash: 8c334dee835c289b5e67a66464815ca8f7436e9b177aaf9b5ccb06adbf5ac0b0
Message ID: <199605112302.TAA07610@jekyll.piermont.com>
Reply To: <199605112023.WAA08121@digicash.com>
UTC Datetime: 1996-05-12 03:56:28 UTC
Raw Date: Sun, 12 May 1996 11:56:28 +0800
From: "Perry E. Metzger" <perry@piermont.com>
Date: Sun, 12 May 1996 11:56:28 +0800
To: bryce@digicash.com
Subject: Re: found nym-differentiation! Still need perpetual motion, FTL travel, cold fusion
In-Reply-To: <199605112023.WAA08121@digicash.com>
Message-ID: <199605112302.TAA07610@jekyll.piermont.com>
MIME-Version: 1.0
Content-Type: text/plain
bryce@digicash.com writes:
> > How? Identity police taking genetic samples from every person on the
> > planet six times a day?
>
> Sure: genetic samples and biometric ID in general, collected
> by identity police,
I doubt that will work even were it implemented. Every phone on the
planet and terminal would need to constantly do biometric analysis of
every user, and even then people could program their terminals to lie.
> > > Now let's collect N people and form a Dining-Cryptographers'
> > > net. Once the Dining-Cryptographers' net is up-and-running
> > > let's put out a call for each of the N participants to
> > > announce a public key which will be their nym from now on.
> > > Assuming that you get N public keys, you can have _some_
> > > degree of assurance that there is a one-to-one mapping
> > > between pubkeys/nyms and humans on the DC-Net.
> >
> > And how do you catch the person who tries to send out two keys?
>
> Simple as pie, because of some of the properties of DC-Nets.
> If someone sends out the wrong number of pubkeys, then
> everyone will know, right? So when that happens everyone
> just reveals their shared-secret data from the DC-Net
> session.
And if several people lie about their shared secrets?
Really, you aren't thinking nearly deviously enough.
Perry
Return to May 1996
Return to “Simon Spero <ses@tipper.oit.unc.edu>”