1995-10-25 - Re: Hack DigiCash: Payee Anonymity

Header Data

From: shamrock@netcom.com (Lucky Green)
To: cypherpunks@toad.com
Message Hash: 6810abd577e44d33265526d2bc1f81d080a80c235b82c243dbadeba569b61701
Message ID: <199510250540.BAA23454@book.hks.net>
Reply To: N/A
UTC Datetime: 1995-10-25 05:42:36 UTC
Raw Date: Tue, 24 Oct 95 22:42:36 PDT

Raw message

From: shamrock@netcom.com (Lucky Green)
Date: Tue, 24 Oct 95 22:42:36 PDT
To: cypherpunks@toad.com
Subject: Re: Hack DigiCash: Payee Anonymity
Message-ID: <199510250540.BAA23454@book.hks.net>
MIME-Version: 1.0
Content-Type: text/plain


-----BEGIN PGP SIGNED MESSAGE-----

In article <199510240750.IAA04175@utopia.hacktic.nl>,
anon-remailer@utopia.hacktic.nl (Name Withheld by Request) wrote:

> Well, Sameer is offering a "Hack DigiCash" promotion, in the same spirit as
> the hack Netscape and Microsoft offer.  However, Chaum is a fairly
> experienced cryptographer, and I doubt that there are any major security
> flaws in the system.  The trial version used RSAREF, so that code at least
> was open for your inspection.  There is still the possibility of bugs
> creeping in when porting to different platforms tho...
> 
> I think the most interesting hack to pursue is to eliminate the
> payee-nonanonymity problem.  The current software uses the following
> protocol:
[protocol elided]

Payee anonymity will never be integrated into the protocol for political
reasons. Still, it is trivial to do this with current Ecash by setting up
a repayer site. I'll release some perl scipts doing just that as soon as
my current project is over (~2-3 weeks).
- ---
[This message has been signed by an auto-signing service.  A valid signature
means only that it has been received at the address corresponding to the
signature and forwarded.]

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Gratis auto-signing service

iQBFAwUBMI3N1CoZzwIn1bdtAQFsNQF/ZxwblP0YIUE47oXukUuSCA0ymeVexjGc
d7AA0efbzER+xKYvjtwppTGoWG+GiNzx
=35an
-----END PGP SIGNATURE-----





Thread