From: shawn leas <sleas@d.umn.edu>
To: cypherpunks@toad.com (cypher list)
Message Hash: e55dc9bd6d22b073abc2b5602ee170b5d3b9e82b377a95d75fa238250ebb9b9e
Message ID: <199412142323.RAA18339@ub.d.umn.edu>
Reply To: N/A
UTC Datetime: 1994-12-14 23:23:34 UTC
Raw Date: Wed, 14 Dec 94 15:23:34 PST
From: shawn leas <sleas@d.umn.edu>
Date: Wed, 14 Dec 94 15:23:34 PST
To: cypherpunks@toad.com (cypher list)
Subject: Re: pgp lib
Message-ID: <199412142323.RAA18339@ub.d.umn.edu>
MIME-Version: 1.0
Content-Type: text
-----BEGIN PGP SIGNED MESSAGE-----
> Don't get me wrong. I understand how difficult it is to do this and I
> am not ragging on the PGP developers for being slow or lazy or
> anything like that (I know they are underpaid). BUT, somebody must
> write a PGP library if we are to see major advancement in the
> penetration of crypto software into the mainstream. The question is,
> who is writing it? It almost seems as if PGP development is now
> happening in secret, and nobody really knows what the statusis on pgp
> 3.0 and the rumored library. There are people on this list who know,
> but nobody is telling. If the PGP people really are making progress
> on a PGP library, we need to know. We can probably help. If not, we
> also need to know so we can write one.
Here here! I agree. There are those who know, and to merely shut out
all the expertise that might be on this mailing list is nonesense. I
think the pgp library approach is very interesting. It could make pgp
almost as common as winsock. We know that there is vast interest in
finding a good front-end for pgp. The thing is, no one wants to dig
around in code that utilizes poor modularity and try to flesh out an
API. Once 3.0 comes out, one could build an app under windows using a
PGP v2.x DLL, and a newly made PGP v3 DLL that would handle all kinds of
keyfiles, a one step option to convert keyfiles, etc... I think the idea
of writing a PGP DLL while the format will change in v3 of PGP is still
feasable. Just use it again for backwards compatability. a PGWINP.EXE,
a PGPV2.DLL, and a PGPV3.DLL. Or whatever. I've only had experience in
UN*X, and maybe I'm oversimplifying everything. But, then again, what is
ever simple when you have the trusty old 'windoze' GPF errors. I much
preferr the unix 'segmentation fault (core dumped)'. Anyway, I will
happily stand corrected on anything I say. Remember, just an idea!
#include <stddisclaimer.h>
#include <stdbroken_bsd_routine_defines_and_other_solaris_shortcomings.h>
#include <stdbugs.h>
#include <Niki_taylor.h>
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQEVAwUBLu99gCdA5IMp25vRAQFM7gf9Fmzx1ueMjuh9iORMQG03+33Z9DRUsL7W
s8AFAQCHEwSSLgCNUZBQoRXhgb56c1z+Wvjhk6FvZTF6GyMqdF/8pkJTeQl2tHgo
ayX61LDPqu7Xlx5tDyBblfJZ0kJJpF/SIpBe6dUIquSq5NxHodNcH8UmWNXzJ7LO
9fYl5/UJozyqLZHFPISNI/yIZtMJmFn1ogzIFagxrF4YxUVGe6+UAw+ZYfxiYYfb
8yVDdfmCkcjk3ksEcFtgmXs1ZJwAZ8B1IVeAWuJZSxSsO9Au6sO3q3rtFLEY3Vgu
Ml45vI9gTJDlR0lwB0tAfx/R/VDfr2ji5Bra27ru69NUvt2zB54pMg==
=Jx1p
-----END PGP SIGNATURE-----
Return to December 1994
Return to “shawn leas <sleas@d.umn.edu>”
1994-12-14 (Wed, 14 Dec 94 15:23:34 PST) - Re: pgp lib - shawn leas <sleas@d.umn.edu>