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 [EMAIL PROTECTED]

Reply via email to