From: Adam Shostack <adam@homeport.org>
To: lethin@ai.mit.edu (Rich Lethin)
Message Hash: 3abccb3750968cb4ce75a1b9eae1523550573cf2068d10205f65e6af7998a051
Message ID: <199509241924.PAA18525@homeport.org>
Reply To: <199509241745.NAA20271@toast.ai.mit.edu>
UTC Datetime: 1995-09-24 19:28:42 UTC
Raw Date: Sun, 24 Sep 95 12:28:42 PDT
From: Adam Shostack <adam@homeport.org>
Date: Sun, 24 Sep 95 12:28:42 PDT
To: lethin@ai.mit.edu (Rich Lethin)
Subject: Re: macworld crypto articles
In-Reply-To: <199509241745.NAA20271@toast.ai.mit.edu>
Message-ID: <199509241924.PAA18525@homeport.org>
MIME-Version: 1.0
Content-Type: text/plain
| For the next version, include PGP free with every version of Quicken,
| and have Quicken just "call" PGP.
|
| Of course, users can encrypt their files now with PGP. Is there an
| Intuit bboard where someone could post instructions?
Of course, it would be *much* easier to store Quicken + data
files on an encrypted filesystem (Cryptdisk or SFS). To start
quicken, the user starts Cryptdisk, runs Quicken on his encrypted
files (now transparently available), and then quits. Cryptdisk
disappears 5 minutes later.
Thus, Intuit isn't putting crypto calls which might be illegal
into their code. They maintain a single code base, a single version
in the warehouses, and continue to lobby Congress to change the laws.
(Quicken gets stored on the encrypted area so that it won't
start up and say 'where are my data files?')
Naturally, this works with programs other than Quicken.
Adam
--
"It is seldom that liberty of any kind is lost all at once."
-Hume
Return to September 1995
Return to “lethin@ai.mit.edu (Rich Lethin)”