1996-03-02 - Re: X.509 certs that don’t guarantee identity

Header Data

From: Bob Snyder <rsnyder@janet.advsys.com>
To: cypherpunks@toad.com
Message Hash: 443a4fd997f55480f245ecc5f706adc20fad1d44e66f0ffecb54f106f27cfd00
Message ID: <v03005103ad5ca339f896@[204.145.227.11]>
Reply To: <199602260448.WAA01201@proust.suba.com>
UTC Datetime: 1996-03-02 09:25:58 UTC
Raw Date: Sat, 2 Mar 1996 17:25:58 +0800

Raw message

From: Bob Snyder <rsnyder@janet.advsys.com>
Date: Sat, 2 Mar 1996 17:25:58 +0800
To: cypherpunks@toad.com
Subject: Re: X.509 certs that don't guarantee identity
In-Reply-To: <199602260448.WAA01201@proust.suba.com>
Message-ID: <v03005103ad5ca339f896@[204.145.227.11]>
MIME-Version: 1.0
Content-Type: text/plain


>  The navigator will not differentiate them.  We build in a default set of
>CA certificates into the navigator, and then allow the user to modify them as
>they see fit based on their local trust policy.  The default set of CAs that
>we ship with our product will not include the verisign level 1&2 CAs as
>trusted
>SSL Server CAs.

With the level 1&2 CA certs be include but not enabled, or will users have
to go pull them themselves?

Bob







Thread