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

Header Data

From: Lucky Green <shamrock@netcom.com>
To: Bill Frantz <adam@homeport.org>
Message Hash: a003733c09e90af920f878aafdba572834825d4073e5c5693e78cfd8d15c2c64
Message ID: <>
Reply To: <199707171339.JAA19638@homeport.org>
UTC Datetime: 1997-07-17 17:21:31 UTC
Raw Date: Fri, 18 Jul 1997 01:21:31 +0800

Raw message

From: Lucky Green <shamrock@netcom.com>
Date: Fri, 18 Jul 1997 01:21:31 +0800
To: Bill Frantz <adam@homeport.org>
Subject: Re: Verisign gets export approval
In-Reply-To: <199707171339.JAA19638@homeport.org>
Message-ID: <>
MIME-Version: 1.0
Content-Type: text/plain

At 09:16 AM 7/17/97 -0700, Bill Frantz wrote:
>It seems to me that someone who has a one year export approved Verisign
>cert should use it to authenticate a new top-level CA cert which they pass
>to their customers.  Cut Verisign and their nosy/noisy partner out of the

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.

--Lucky Green <shamrock@netcom.com>
  PGP encrypted mail preferred.
  DES is dead! Please join in breaking RC5-56.