[15891] in cryptography@c2.net mail archive
Re: How a Digital Signature Works
daemon@ATHENA.MIT.EDU (Dave Howe)
Thu Aug 12 16:54:59 2004
X-Original-To: cryptography@metzdowd.com
X-Original-To: cryptography@metzdowd.com
Date: Wed, 11 Aug 2004 11:56:44 +0100
From: Dave Howe <DaveHowe@gmx.co.uk>
To: Email@metzdowd.com,
List@metzdowd.com:Cryptography <cryptography@metzdowd.com>
In-Reply-To: <p06110433bd3e6324677b@[66.149.49.5]>
R. A. Hettinga wrote:
> The publisher first has to obtain a digital certificate from a recognized
> "certificate authority" or CA (VeriSign (VRSN ) is the largest and best
> known CA in the U.S.). The publisher receives a private and a public key,
> each of which is a long number of about 300 digits. These are used to
> create a digital signature for each program (see BW Online, 8/10/04,
> "Windows of Vulnerability No More?").
And which will guarantee to... erm... *try* not to sell the same
certificate to someone else, or to at least notice if they do (provided
it has a famous name on it like "microsoft" of course)
and what is "new" about MS's signed executable support? its been around
long enough...
---------------------------------------------------------------------
The Cryptography Mailing List
Unsubscribe by sending "unsubscribe cryptography" to majordomo@metzdowd.com
