1994-12-14 - Re: Encrypted Credit Card Numbers For Transmission….

Header Data

From: “L. McCarthy” <lmccarth@ducie.cs.umass.edu>
To: cypherpunks@toad.com (Cypherpunks Mailing List)
Message Hash: 0331a27f12e4f5e172c7ea03782400bfade0efc6a72f65cd2af8d157fc8319f9
Message ID: <199412140630.BAA28049@ducie.cs.umass.edu>
Reply To: <D0exkOwsccPN075yn@io.org>
UTC Datetime: 1994-12-14 06:29:46 UTC
Raw Date: Tue, 13 Dec 94 22:29:46 PST

Raw message

From: "L. McCarthy" <lmccarth@ducie.cs.umass.edu>
Date: Tue, 13 Dec 94 22:29:46 PST
To: cypherpunks@toad.com (Cypherpunks Mailing List)
Subject: Re: Encrypted Credit Card Numbers For Transmission....
In-Reply-To: <D0exkOwsccPN075yn@io.org>
Message-ID: <199412140630.BAA28049@ducie.cs.umass.edu>
MIME-Version: 1.0
Content-Type: text/plain


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

Mark Terka writes:
> Why don't organizations like Wired (who are ostensibly closely connected to
> the 'net) not have public keys (ie through Viacrypt, as they are a commercial
> enterprise) that subscription purchasers could encrypt a credit card number
> to them, and then e-mail that cyphertext file to them for processing.

Some do; see for example http://northpole.net/buttons.html (as noted by Hal
Finney previously).

> [...] use of encryption is hardly a novel concept for business
> to swallow (particularly a magazine like Wired, who likely have a reasonably
> encryption knowledgeable readership or potential readership).

Wired is tired. Someone should call them on this.

Incidentally, I just tried to get into HotWired using the "cypherpunks"/
"cypherpunks" combo I recommended to Amanda earlier this evening. It didn't
work. I'm just about to re-register cypherpunks on it, so don't be surprised
to see a verification key sent to the list soon. I'll summarize to the list
once the new membership seems ready to go.

- -L. Futplex McCarthy

"Your registration [...] encourages responsible behavior and good citizenship 
by discouraging anonymity." --Hotwired, on http://www.hotwired.com/newform.html




-----BEGIN PGP SIGNATURE-----
Version: 2.6.1

iQCVAwUBLu6Q9Gf7YYibNzjpAQFHswQA38F5Ky8pus0EYJfo7pi/+w+rfTMpXlY/
BIPUL49HQjsLYlKgOkgbsUZYdyHFyqvikqFHDbLuZiuLigsRjmlWc1BJPCSEdHML
tEyPaw8rgwjVaJOP1Y16LW25lkcCn4sXVVxFlpFsjfSKF6peOcAteXFXJ5Y2kpK8
QCmu4pJZpbg=
=uaT5
-----END PGP SIGNATURE-----




Thread