CP uses for the PGP 5.0 source

With the on-line availability of PGP 5.0 source code expected any day,
perhaps the group should consider what CP goals can now be made practical.
Hopefully, PGP will not object to CP uses.  I submit the following as CP
projects which could be substantially eased by the source code:

EMAIL PLUG-INS
PGP 5.0 contains some very good code examples for creating email plug-ins
for Microsoft Exchange for Windows 95 and Windows NT 4.0, Microsoft Outlook
for Windows 95 and Windows NT 4.0, Eudora Pro/Light for Windows 95, Windows
NT 4.0, Macintosh, Claris Emailer for Mac only.  For cross-platform ease, I
suggest we tackle the Eudora emailers, which have a well defined API, first.

1. Remailer:  One reason remailers haven't been as popular as we've hoped
is the need to operate separate, sometime difficult to use, remailer client
software.  By integrating these and other functions into plug-ins, creation
of persistant identities and integration with key generation and management
can be simplified.

2. Digital postage: CPs can gain the high-ground in the battle for handling
the SPAM problem by offering plug-ins which enforce restrictions on
incoming mail using digital postage.  Two postage approaches have been
discussed on the CP lists: ecash and hashcash.  I suggest that the plug-ins
offer both d-postage forms.

Hashcash is eligent in its simplicity and its lack of a required central
clearing facility. Hascash-based d-postage could also seed the development
of commercial distributed computing Net industry, as SPAMers elect to
purchase hashcash rather than generating it themselves-the idea isn't to
eliminate SPAM, just place it on similar economic footing with junk
snailmail. Adam Back has already done a considerable amount of
investigation of ways to implement hascash (See
http://www.dcs.ex.ac.uk/~aba/hashcash/).

ECash could really supply an economic shot in the arm for remailers, making
possible commercial (read profitable) remailers.  It will also offer a
ready-made market for accountless ecash, which will be available soon.
Jeremey Barrett's higher level ecash API should greatly simplify ecash
integration.

--Steve


PGP mail preferred
Fingerprint: FE 90 1A 95 9D EA 8D 61  81 2E CC A9 A4 4A FB A9
---------------------------------------------------------------------
Steve Schear              | tel: (702) 658-2654
CEO                       | fax: (702) 658-2673
First ECache Corporation  |
7075 West Gowan Road      |
Suite 2148                |
Las Vegas, NV 89129       | Internet: azur@netcom.com
---------------------------------------------------------------------

        I know not what instruments others may use,
        but as for me, give me Ecache or give me debt.

        SHOW ME THE DIGITS!

At 04:41 PM 6/22/97 -0700, Steve Schear wrote:
>1. Remailer:  One reason remailers haven't been as popular as we've hoped
>is the need to operate separate, sometime difficult to use, remailer client
>software.  By integrating these and other functions into plug-ins, creation
>of persistant identities and integration with key generation and management
>can be simplified.

Type I remailers were a nice proof of concept. Nothing more. What you want
is a Mixmaster client similar to PGP 5.0. I doubt the PGP source will be of
much help for this task.

>2. Digital postage: 

Has nothing to do with PGP. A different problem entirely.

[...]
>ECash could really supply an economic shot in the arm for remailers, making
>possible commercial (read profitable) remailers.  It will also offer a
>ready-made market for accountless ecash, which will be available soon.
>Jeremey Barrett's higher level ecash API should greatly simplify ecash
>integration.

Amen. What's the ETA?

Thanks,

--Lucky Green <shamrock@netcom.com>
  PGP encrypted mail preferred.
  DES is dead! Please join in breaking RC5-56.
  http://rc5.distributed.net/

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

At 05:05 PM 6/22/97 -0700, Lucky Green wrote:
>>ECash could really supply an economic shot in the arm for remailers, making
>>possible commercial (read profitable) remailers.  It will also offer a
>>ready-made market for accountless ecash, which will be available soon.
>>Jeremey Barrett's higher level ecash API should greatly simplify ecash
>>integration.
>
>Amen. What's the ETA?
>

The API as it stands is done, and tested fairly well on linux and bsdi.
Over the next week or two I have more to add though, and have to do some
porting, notably to windoze. But that's roughly the ETA. I think I'm gonna
set up some sort of mailing list for it, I'll post details.

BTW, I think the API header made it's way to this list a couple weeks ago,
but if people want to know what to expect, lemme know.

Regards,
Jeremey.

-----BEGIN PGP SIGNATURE-----
Version: 5.0
Charset: noconv

iQCVAwUBM63/4C/fy+vkqMxNAQE6JgQAls4T8T9N5wUSdEHY1HNE/ZBfkJJobOhL
7Z2ycP+mEj5dMnOy5Uekwz2sni30BeNAaByunjhd02VMl0otkeyORdIcpn4qvztT
cNUdEDpYnBaB6SGGAaXkXHDc9Ta/PedsPHjB3XfQz1XrIxgSbx4YzHNBbIOwtizh
mrDAxcTZYdI=
=GpwS
-----END PGP SIGNATURE-----

--
Jeremey Barrett                                BlueMoney Software Corp.
Crypto, Ecash, Commerce Systems               http://www.bluemoney.com/
PGP key fingerprint =  3B 42 1E D4 4B 17 0D 80  DC 59 6F 59 04 C3 83 64