|
Tech
Decrypted
Taking the mystery out of learning cryptography
|
![]()
|
Download Part III: Distribution of Public Keys From Cryptography Decrypted by H.X. Mel and Doris Baker Part
III Synopsis:
Certificates: Distributing Public Keys Even though Even though attacks are possible[1], digital certificates are the preferred way to securely deliver public keys. A digital certificate is a specialized document signed by a trusted third party not much different than a driver’s license. Just as in the case of a driver’s license, if you can trust the issuer and its issuing procedures, you can trust the certificate. The top part of a digital certificate contains plaintext identifying the issuer (signer), subject (whose public key is attached), the subject’s public key and the expiration date of the certificate. The bottom part of a digital certificate contains the issuer’s signed hash of the top part. As mentioned in the article on public key cryptography, the hash saves time when digitally authenticating since it is compressed redundant copy of the original digital certificate. A digital certificate consumer must have a trusted copy of the digital certificate issuer’s public key to verify the certificate. The issuer, subject and consumer are reviewed in table 16-1.
Table 16-1 Digital Certificate Players Here we’ll examine two popular standards for digital certificates – X.509 and Pretty Good Privacy (PGP). These are two ways that a network of digital certificates can be managed. These digital certificate frameworks are commonly called public key infrastructures or PKI. X.509 employs a centralized control in its trust model, while PGP distributes the trust. The Root Certificate Authority (CA) is the single focal point of X.509 certificate policies. Digital certificate users trust the accuracy of the public keys the CA issues. Like a DMV, the CA controls certificate registration, issuance, expiration and revocation. (We’ll see this is in stark contrast to PGP’s trust model, where the individual user acts unilaterally.) The CA can out-source most of these functions to subcontractors. For instance, PKI defines terms and definitions for Registration Authorities (RA) who act on behalf of the CA. The CA can outsource the distribution of the certificate revocation list (CRL). A CA Root Certificate is self-signed by the CA and is usually accepted as valid with additional verification. CA Root Certificates are often distributed through another trusted source; for example Netscape’s Internet Browser.
|
|
(c) H. X. Mel & Doris Baker all rights reserved |