Bloomberg Anywhere Remote Login Bloomberg Terminal Demo Request


Connecting decision makers to a dynamic network of information, people and ideas, Bloomberg quickly and accurately delivers business and financial information, news and insight around the world.


Financial Products

Enterprise Products


Customer Support

  • Americas

    +1 212 318 2000

  • Europe, Middle East, & Africa

    +44 20 7330 7500

  • Asia Pacific

    +65 6212 1000


Industry Products

Media Services

Follow Us

Bloomberg Customers

How a Digital Signature Works

By Stephen H. Wildstrom A technology called public key cryptography makes it possible for you to make sure that the publisher of any piece of software that claims to be from Microsoft (MSFT) or any other publisher really came from there. It has the added benefit of insuring that the contents weren't maliciously altered or damaged in transmission. Here's how it works:

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?").

When the software is ready to be posted for download, the publisher runs it through a mathematical process called a one-way hash which reduces it to a long number called the message digest. The message digest is then encrypted using the publisher's private key, and the result, which looks like a string of gibberish when displayed, is appended to the program when it's downloaded.

HASH SLINGING. The trick of public key encryption -- the best known approach is called RSA for the initials of its inventors -- is that one key can be used to scramble the data while a different, mathematically related, key is used to unscramble it. When you download a digitally signed program, the first thing your computer does is check the Web site's digital certificate. It then queries the CA that issues the certificate to make sure it's still valid and to obtain the public key.

When the download is complete, your computer uses the public key to decrypt the message digest. It also runs the same one-way hash procedure on the downloaded software. If everything is as it should be, the decrypted message digest and the one just created should be identical. If they differ by a single bit, something is wrong and the downloaded software will be rejected.

For the curious, here's the message digest of the five paragraphs above (as plain text), created using the MD5 algorithm from RSA Data Security Inc: c21196eb8e026d47a67883d746c72c8d. Wildstrom is Technology & You columnist for BusinessWeek. Follow his Flash Product Reviews, only at BusinessWeek Online

blog comments powered by Disqus