1997-07-18 - Re: Verisign gets export approval

Header Data

From: Jason William RENNIE <jrennie@hardy.ocs.mq.edu.au>
To: cypherpunks@toad.com
Message Hash: 00aaa55e5c9d5bd89300180a88ee337b5fce985e4c1b2244d526dfbe525b15ca
Message ID: <Pine.SOL.3.91.970718203704.3553B-100000@hardy>
Reply To: <>
UTC Datetime: 1997-07-18 10:55:04 UTC
Raw Date: Fri, 18 Jul 1997 18:55:04 +0800

Raw message

From: Jason William RENNIE <jrennie@hardy.ocs.mq.edu.au>
Date: Fri, 18 Jul 1997 18:55:04 +0800
To: cypherpunks@toad.com
Subject: Re: Verisign gets export approval
In-Reply-To: <>
Message-ID: <Pine.SOL.3.91.970718203704.3553B-100000@hardy>
MIME-Version: 1.0
Content-Type: text/plain

> Only a valid VeriSign Global ID cert (an X.509 v3 cert with a special
> extension) will activate the strong encryption in exportable browsers. This
> is hardcoded into Navigator and Internet Explorer.
So, write a new browser (Theres a linux project staring to do 
this for linux soon/now (i think anyway)) and then port to a bunch of 
systems and base it outside the US. There aren't any import restriction 
on strong crypto yet are there ?? Besides you could then set up a home 
page ala. netscape.com and rake in the advertising dollars, if you can 
get teh browser to take off. A lot of if's and work but in theory it 

Jason =8-]