1994-06-22 - PGP Comments and Questions.

Header Data

From: trollins@debbie.telos.com (Tom Rollins)
To: N/A
Message Hash: 1e2e9cfcb7b8eeae8590eaa2e6d3395bb6cc10c6f44f60b914b8939921e18d37
Message ID: <9406221233.AA22563@debbie.telos.com>
Reply To: N/A
UTC Datetime: 1994-06-22 12:33:33 UTC
Raw Date: Wed, 22 Jun 94 05:33:33 PDT

Raw message

From: trollins@debbie.telos.com (Tom Rollins)
Date: Wed, 22 Jun 94 05:33:33 PDT
Subject: PGP Comments and Questions.
Message-ID: <9406221233.AA22563@debbie.telos.com>
MIME-Version: 1.0
Content-Type: text/plain


Hey, Got some comments about the future of PGP.

I would like to compair PGP with DOS. It has gotten a large
following and that is good. It has it's limitations and that
is bad.
Like DOS, expanding it's functions seems to be trouble. Trouble
from the tech side and from government.
I believe that we should lay a framework so that people around
the world can modify and enhance various parts of PGP and not
get in each others way. After all, how much can 1 or 2 or 3 or
4 people do vs thousands on the net.
Also if the code is modular, people in the US can work on
sections that do not contain the crypto engines.
Bulk crypto engines could be replaced and not get in the way of
the Public key stuff.

So, now for some questions....

As I understand the Gnu CopyLeft. People can make changes and
pass them on with the source code and NOT step on anyone's
toes. Why then should there be an official release by a small
group of people that still have bugs in the code after N years.
An official framework which will allow for expansion and change
is in order.

Is Mathew in the UK a named remailer for Phil Z? (just kidding)

How fine do you have to divide the crypto code before it is not
considered crypto code anylonger. (for US ITAR regs)

How do the French get around the anti crypto laws? I want to know
before those laws get enacted here in the US.





Thread