1994-06-23 - Re: Need advice on starting to make PGP library

Header Data

From: NetSurfer <jdwilson@gold.chem.hawaii.edu>
To: “Timothy L. Nali” <tn0s+@andrew.cmu.edu>
Message Hash: feaeed24964d94a98663e00260f8b4b1e111dfbce08221e987f848c83ebced87
Message ID: <Pine.3.07.9406221419.D3899-b100000@gold.chem.hawaii.edu>
Reply To: <8i20C3W00iV0E0jVVf@andrew.cmu.edu>
UTC Datetime: 1994-06-23 01:03:25 UTC
Raw Date: Wed, 22 Jun 94 18:03:25 PDT

Raw message

From: NetSurfer <jdwilson@gold.chem.hawaii.edu>
Date: Wed, 22 Jun 94 18:03:25 PDT
To: "Timothy L. Nali" <tn0s+@andrew.cmu.edu>
Subject: Re: Need advice on starting to make PGP library
In-Reply-To: <8i20C3W00iV0E0jVVf@andrew.cmu.edu>
Message-ID: <Pine.3.07.9406221419.D3899-b100000@gold.chem.hawaii.edu>
MIME-Version: 1.0
Content-Type: text/plain



There is a current freeware Windows interface that works ok, but it
is not truly integrated i.e. it fires off a DOS background session
and stuffs parameters incl. your passphrase.

A DLL or VxD would be the better solution.  (A VxD has no DOS memory
overhead.)

If you were interested, once you have the DLL or VxD you could use the
Microsoft Office developers kit (currently approx. $49 on CD) and integrate
PGP into Excel-type applications, Word-type applications, Powerpoint-type
applications, and *microsoft mail* type applications.  I say "type" because
unlike the current links (OLE etc.) the developers kit gives you objects
to incorporate in your programs, including but *not* limited to Visual
Basic or Visual C++.

-NetSurfer

#include standard.disclaimer

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
==  =    = |James D. Wilson        |V.PGP 2.4:   512/E12FCD 1994/03/17 >
 "  "    " |P. O. Box 15432        |     finger for full PGP key        >
 "  " /\ " |Honolulu, HI  96830    |====================================>
\"  "/  \" |Serendipitous Solutions|    Also NetSurfer@sersol.com      >
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>













Thread