1995-10-21 - Re: Verisign and MITM

Header Data

From: Hal <hfinney@shell.portal.com>
To: cypherpunks@toad.com
Message Hash: 68108aa9bf92b8719a00a5ecbf14ef952dcf8551e4e5d1b22365f3757dee1488
Message ID: <199510211553.IAA02421@jobe.shell.portal.com>
Reply To: <199510201540.IAA11523@infinity.c2.org>
UTC Datetime: 1995-10-21 20:53:08 UTC
Raw Date: Sat, 21 Oct 95 13:53:08 PDT

Raw message

From: Hal <hfinney@shell.portal.com>
Date: Sat, 21 Oct 95 13:53:08 PDT
To: cypherpunks@toad.com
Subject: Re: Verisign and MITM
In-Reply-To: <199510201540.IAA11523@infinity.c2.org>
Message-ID: <199510211553.IAA02421@jobe.shell.portal.com>
MIME-Version: 1.0
Content-Type: text/plain


sameer <sameer@c2.org> writes:

>	I recently submitted a certificate request to Verisign for my
>SSL web server. Looking over the process, I don't see how it avoids
>MITM in any way.
>[...]
>	I don't see any mechanism in place to avoid an MITM subverting
>step (A), and putting in his cert request in there. There isn't a
>strong cryptographic unforgeable relationship between my
>usmail/fax/proof request and the emailed kx509 cert request.

I guess the one limitation is that you would either not get the
certificate (because the MITM kept it) or you would find out that it did
not include your public key (if he forwarded it to you).  In either case
the MITM would be discovered.  In the mean time he could wreak some
havoc, though.  But he would be found out after a few days.  That's one
of the things they need Certificate Revocation Lists for in their system,
but I don't know if they are used.

Hal






Thread