A cryptosystem (or cryptographic system) is the package of all procedures, protocols, cryptographic algorithms and instructions used for encoding and decoding messages using cryptography. It will generally contain an integrated assembly of cryptographic primitives (e.g., encryption algorithms, hash algorithms, etc), protocols for their use, operational procedures, and auxillary elements (documentation, user training materials, and so on) which together make possible effective security as intended by the designer(s). It is cryptosystems that users interact with, it is cryptosystems which provide whatever security is desired, and it is (usually) cryptosystems which fail in practice. An understanding of some of the system level issues in the use of cryptography will be helpful to all who propose to use it, or who will have it deployed by default on their behalf.

This article discusses the nature of cryptosystems using as an illustrative example the design and implementation an influential modern cryptosystem—PGP. PGP is computer software, as essentially all practical cryptographic systems now are. It is more complex than earlier hand or mechanical rotor systems, but was chosen because it is far more typical of modern cryptographic practice. Version 2.6x is used as an example rather than say the OpenPGP standard, as it is conceptually similar, but has fewer algorithm choices.

Design overview

encryption, integrity, non-repudiation, key exchange

First-level issues

MD5, RSA, IDEA, hybrid use of encryption for efficiency purposes, key distribution, digital signature of certificates / messages, key vetting, open source, use of publicly known and examined primitives

Second-level issues

RSA/IDEA key choices, random inputs

Third-level issues

format and content of certificates, choice of certificate vetting mechanism, lack of truly secure channels for key distribution and vetting,