Re: Private Idaho source code now available

At 11:35 PM 1/11/97 -0500, Anonymous wrote:
>Joel McNamara says:
>> Private Idaho 2.8b3, a bug fix version of the popular Windows freeware PGP
>> and remailer utility, is now available.  This will be my last official
>> release of PI for the foreseeable future.
>> 
>> Due to other projects and new directions, I haven't been able to spend as
>> much time as I'd like coding and supporting Private Idaho.  Instead of
>> seeing it die on the vine, I've decided to release the source code under
>> the GNU General Public License (export disclaimer - the sources do not
>> include, or have ever contained, cryptographic algorithms).
>
>	My understanding is that Private Idaho uses PGP internally
>and provides the same functionality as premail, with an 
>easier to use GUI.
>
>	Given that, it would still be export controlled, since it
>enables cryptography. That is why Raph doesn't allow export of premail.

The "enables cryptography" thing just doesn't cut it.  A computer "enables 
cryptography" to a person without a computer.  The MSDOS operating system 
"enables cryptography" to a person with a computer but without an OS.  A 
hard disk with a filesystem "enables cryptography" by providing an 
intermediate data storage location (and format) for encrypted and 
unencrypted data, as well as the encryption program.  Even a modem program 
or mail program "enables cryptography", or at least enables the transmission 
of encrypted data, etc.

Apparently, the phrase "enable cryptography" is either just about 
meaningless, or is so broad as to be not usable to determine which items are 
exportable and which aren't.  How about narrowing it down a bit?  


Jim Bell
jimbell@pacifier.com

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

In article <199701120553.VAA10283@mail.pacifier.com>,
jim bell  <jimbell@pacifier.com> wrote:
>At 11:35 PM 1/11/97 -0500, Anonymous wrote:
>>Joel McNamara says:
>>> Private Idaho 2.8b3, a bug fix version of the popular Windows freeware PGP
>>> and remailer utility, is now available.  This will be my last official
>>> release of PI for the foreseeable future.
>>> 
>>> Due to other projects and new directions, I haven't been able to spend as
>>> much time as I'd like coding and supporting Private Idaho.  Instead of
>>> seeing it die on the vine, I've decided to release the source code under
>>> the GNU General Public License (export disclaimer - the sources do not
>>> include, or have ever contained, cryptographic algorithms).
>>
>>	My understanding is that Private Idaho uses PGP internally
>>and provides the same functionality as premail, with an 
>>easier to use GUI.
>>
>>	Given that, it would still be export controlled, since it
>>enables cryptography. That is why Raph doesn't allow export of premail.
>
>The "enables cryptography" thing just doesn't cut it.  A computer "enables 
>cryptography" to a person without a computer.  The MSDOS operating system 
>"enables cryptography" to a person with a computer but without an OS.  A 
>hard disk with a filesystem "enables cryptography" by providing an 
>intermediate data storage location (and format) for encrypted and 
>unencrypted data, as well as the encryption program.  Even a modem program 
>or mail program "enables cryptography", or at least enables the transmission 
>of encrypted data, etc.
>
>Apparently, the phrase "enable cryptography" is either just about 
>meaningless, or is so broad as to be not usable to determine which items are 
>exportable and which aren't.  How about narrowing it down a bit?  

- From the Commerce Control List:

# 5D002.a: ``Software'' specially designed or modified for the
# ``development'', ``production'' or ``use'' of equipment or ``software''
# controlled by 5A002, 5B002 or 5D002.

# 5A002.a: Designed or modified to use ``cryptography'' employing digital
# techniques to ensure ``information security'';

5A002.a covers PGP, so it would seem that 5D002.a covers premail and
Private Idaho.

   - Ian

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBMtqzukZRiTErSPb1AQHHkAP/ZGiD3s4aMC3A6Ldqi1u9csFUQPGos6rv
yoHqT9Zf1/LZPhFom2ikmbdkm69fq6EcahMyhisThY+7SrzSc7Tz8ZNEtfFUP7ze
+Q7/lUiiPr4sn+ZWk/b3l13sSUlxr3hPcP9gphWPMAQyyHDGZ5QkZH3xcH5WrP3D
nD0ckUAaC0A=
=4y4e
-----END PGP SIGNATURE-----