From: Bill Sommerfeld <sommerfeld@orchard.medford.ma.us>
To: Hal <hfinney@shell.portal.com>
Message Hash: 58e127b7208051a2bd77dab495f574bb7f19822bbcb6b5aae207767ca7adad93
Message ID: <199412210316.WAA00684@orchard.medford.ma.us>
Reply To: <199412210221.SAA18077@jobe.shell.portal.com>
UTC Datetime: 1994-12-21 03:29:01 UTC
Raw Date: Tue, 20 Dec 94 19:29:01 PST
From: Bill Sommerfeld <sommerfeld@orchard.medford.ma.us>
Date: Tue, 20 Dec 94 19:29:01 PST
To: Hal <hfinney@shell.portal.com>
Subject: Re: No privacy with DigiCash
In-Reply-To: <199412210221.SAA18077@jobe.shell.portal.com>
Message-ID: <199412210316.WAA00684@orchard.medford.ma.us>
MIME-Version: 1.0
Content-Type: text/plain
-----BEGIN PGP SIGNED MESSAGE-----
> When you buy something, the vendor has to know your machine
> name because he wants to connect back to your ecash wallet process.
> So even if you did connect via a redirector, your anonymity would be
> destroyed (or at least badly hurt) when you tell it your machine
> name so it can connect to you.
>
> Is there something I am overlooking, some way to buy things
> privately with DigiCash?
Yes... at least one TCP/IP proxy system (socks) lets the client
receive incoming connections (the client makes a second connection to
the socks server, and the socks server informs it of the addr/port
that it's listening on; when a connection comes in to that port, the
two incoming connections are gatewayed to each other); that's how
socksified FTP works, by the way.
Things could get sticky if the server needs to make multiple
connections to the wallet at the same address (in sequence or in
series), but I'd imagine that this wouldn't be the case..
- Bill
-----BEGIN PGP SIGNATURE-----
Version: 2.6.1
iQCVAwUBLveeD7T+rHlVUGpxAQFPmAP/SH8FVIKZJqt1OCTHamxmvILo2kEoz/GP
aObHB7X76QWOQXecicGcz/RCKQ7usoHzEI9+P8NkR1yCiZUVAmuK9lFR2YVcDW/Z
KkAglcoppBEQjf2bFhTH7D6W9uSLAYii5M0I0tNTUU61riruhn3akeJ0ur0E7Smw
xN+lKzXuRUo=
=Aiqk
-----END PGP SIGNATURE-----
Return to December 1994
Return to “Jonathan Cooper <entropy@IntNet.net>”