#include "base64.h"
#include "dsa.h"
#include "endianness.h"
#include "mp32.h"
#include "rsa.h"
#include "rsapk.h"
Go to the source code of this file.
Text from RFC-2440 in comments is Copyright (C) The Internet Society (1998). All Rights Reserved.
Definition in file rpmpgp.h.
|
Definition at line 1252 of file rpmpgp.h. Referenced by pgpCRC(). |
|
Definition at line 1253 of file rpmpgp.h. Referenced by pgpCRC(). |
|
Definition at line 25 of file rpmpgp.h. Referenced by rhnUnload(), rpmDigestDup(), rpmDigestFinal(), rpmDigestInit(), rpmDigestUpdate(), and rpmVerifyDigest(). |
|
Referenced by pgpReadPkts(). |
|
|
|
9.3. Compression Algorithms
Implementations MUST implement uncompressed data. Implementations SHOULD implement ZIP. Implementations MAY implement ZLIB. |
|
9.4. Hash Algorithms
Implementations MUST implement SHA-1. Implementations SHOULD implement MD5.
Referenced by fdFiniDigest(), fdInitDigest(), and rpmDigestInit(). |
|
|
|
|
|
5.5.3. Secret Key Packet Formats The Secret Key and Secret Subkey packets contain all the data of the Public Key and Public Subkey packets, with additional algorithm- specific secret key data appended, in encrypted form. The packet contains:
Algorithm Specific Fields for RSA secret keys:
Algorithm Specific Fields for DSA secret keys:
Algorithm Specific Fields for Elgamal secret keys:
Secret MPI values can be encrypted using a passphrase. If a string- to-key specifier is given, that describes the algorithm for converting the passphrase to a key, else a simple MD5 hash of the passphrase is used. Implementations SHOULD use a string-to-key specifier; the simple hash is for backward compatibility. The cipher for encrypting the MPIs is specified in the secret key packet. Encryption/decryption of the secret data is done in CFB mode using the key created from the passphrase and the Initial Vector from the packet. A different mode is used with V3 keys (which are only RSA) than with other key formats. With V3 keys, the MPI bit count prefix (i.e., the first two octets) is not encrypted. Only the MPI non- prefix data is encrypted. Furthermore, the CFB state is resynchronized at the beginning of each new MPI value, so that the CFB block boundary is aligned with the start of the MPI data. With V4 keys, a simpler method is used. All secret MPI values are encrypted in CFB mode, including the MPI bitcount prefix. The 16-bit checksum that follows the algorithm-specific portion is the algebraic sum, mod 65536, of the plaintext of all the algorithm- specific octets (including MPI prefix and data). With V3 keys, the checksum is stored in the clear. With V4 keys, the checksum is encrypted like the algorithm-specific data. This value is used to check that the passphrase was correct. |
|
5.5.1. Key Packet Variants 5.5.1.1. Public Key Packet (Tag 6) A Public Key packet starts a series of packets that forms an OpenPGP key (sometimes called an OpenPGP certificate). 5.5.1.2. Public Subkey Packet (Tag 14) A Public Subkey packet (tag 14) has exactly the same format as a Public Key packet, but denotes a subkey. One or more subkeys may be associated with a top-level key. By convention, the top-level key provides signature services, and the subkeys provide encryption services. Note: in PGP 2.6.x, tag 14 was intended to indicate a comment packet. This tag was selected for reuse because no previous version of PGP ever emitted comment packets but they did properly ignore them. Public Subkey packets are ignored by PGP 2.6.x and do not cause it to fail, providing a limited degree of backward compatibility. 5.5.1.3. Secret Key Packet (Tag 5) A Secret Key packet contains all the information that is found in a Public Key packet, including the public key material, but also includes the secret key material after all the public key fields. 5.5.1.4. Secret Subkey Packet (Tag 7) A Secret Subkey packet (tag 7) is the subkey analog of the Secret Key packet, and has exactly the same format. 5.5.2. Public Key Packet Formats There are two versions of key-material packets. Version 3 packets were first generated by PGP 2.6. Version 2 packets are identical in format to Version 3 packets, but are generated by PGP 2.5 or before. V2 packets are deprecated and they MUST NOT be generated. PGP 5.0 introduced version 4 packets, with new fields and semantics. PGP 2.6.x will not accept key-material packets with versions greater than 3. OpenPGP implementations SHOULD create keys with version 4 format. An implementation MAY generate a V3 key to ensure interoperability with old software; note, however, that V4 keys correct some security deficiencies in V3 keys. These deficiencies are described below. An implementation MUST NOT create a V3 key with a public key algorithm other than RSA. A version 3 public key or public subkey packet contains:
V3 keys SHOULD only be used for backward compatibility because of three weaknesses in them. First, it is relatively easy to construct a V3 key that has the same key ID as any other key because the key ID is simply the low 64 bits of the public modulus. Secondly, because the fingerprint of a V3 key hashes the key material, but not its length, which increases the opportunity for fingerprint collisions. Third, there are minor weaknesses in the MD5 hash algorithm that make developers prefer other algorithms. See below for a fuller discussion of key IDs and fingerprints. Referenced by pgpPrtKey(). |
|
The version 4 format is similar to the version 3 format except for the absence of a validity period. This has been moved to the signature packet. In addition, fingerprints of version 4 keys are calculated differently from version 3 keys, as described in section "Enhanced Key Formats." A version 4 packet contains:
Algorithm Specific Fields for RSA public keys:
Algorithm Specific Fields for DSA public keys:
Algorithm Specific Fields for Elgamal public keys:
Referenced by pgpPrtKey(). |
|
|
|
5.4. One-Pass Signature Packets (Tag 4) The One-Pass Signature packet precedes the signed data and contains enough information to allow the receiver to begin calculating any hashes needed to verify the signature. It allows the Signature Packet to be placed at the end of the message, so that the signer can compute the entire signed message in one pass. A One-Pass Signature does not interoperate with PGP 2.6.x or earlier. The body of this packet consists of:
Note that if a message contains more than one one-pass signature, then the signature packets bracket the message; that is, the first signature packet after the message corresponds to the last one-pass packet and the final signature packet corresponds to the first one- pass packet. |
|
5.1. Public-Key Encrypted Session Key Packets (Tag 1) A Public-Key Encrypted Session Key packet holds the session key used to encrypt a message. Zero or more Encrypted Session Key packets (either Public-Key or Symmetric-Key) may precede a Symmetrically Encrypted Data Packet, which holds an encrypted message. The message is encrypted with the session key, and the session key is itself encrypted and stored in the Encrypted Session Key packet(s). The Symmetrically Encrypted Data Packet is preceded by one Public-Key Encrypted Session Key packet for each OpenPGP key to which the message is encrypted. The recipient of the message finds a session key that is encrypted to their public key, decrypts the session key, and then uses the session key to decrypt the message. The body of this packet consists of:
Algorithm Specific Fields for RSA encryption
Algorithm Specific Fields for Elgamal encryption:
|
|
5.2. Signature Packet (Tag 2) A signature packet describes a binding between some public key and some data. The most common signatures are a signature of a file or a block of text, and a signature that is a certification of a user ID. Two versions of signature packets are defined. Version 3 provides basic signature information, while version 4 provides an expandable format with subpackets that can specify more information about the signature. PGP 2.6.x only accepts version 3 signatures. Implementations MUST accept V3 signatures. Implementations SHOULD generate V4 signatures. Implementations MAY generate a V3 signature that can be verified by PGP 2.6.x. Note that if an implementation is creating an encrypted and signed message that is encrypted to a V3 key, it is reasonable to create a V3 signature. |
|
5.2.2. Version 3 Signature Packet Format The body of a version 3 Signature Packet contains:
Algorithm Specific Fields for RSA signatures:
Algorithm Specific Fields for DSA signatures:
Referenced by pgpPrtSig(). |
|
5.2.3. Version 4 Signature Packet Format The body of a version 4 Signature Packet contains:
Referenced by pgpPrtSig(). |
|
5.3. Symmetric-Key Encrypted Session-Key Packets (Tag 3) The Symmetric-Key Encrypted Session Key packet holds the symmetric- key encryption of a session key used to encrypt a message. Zero or more Encrypted Session Key packets and/or Symmetric-Key Encrypted Session Key packets may precede a Symmetrically Encrypted Data Packet that holds an encrypted message. The message is encrypted with a session key, and the session key is itself encrypted and stored in the Encrypted Session Key packet or the Symmetric-Key Encrypted Session Key packet. If the Symmetrically Encrypted Data Packet is preceded by one or more Symmetric-Key Encrypted Session Key packets, each specifies a passphrase that may be used to decrypt the message. This allows a message to be encrypted to a number of public keys, and also to one or more pass phrases. This packet type is new, and is not generated by PGP 2.x or PGP 5.0. The body of this packet consists of:
|
|
|
|
|
|
9.1. Public Key Algorithms
Implementations MUST implement DSA for signatures, and Elgamal for encryption. Implementations SHOULD implement RSA keys. Implementations MAY implement any other algorithm. |
|
5.2.1. Signature Types There are a number of possible meanings for a signature, which are specified in a signature type octet in any given signature. |
|
5.2.3.1. Signature Subpacket Specification The subpacket fields consist of zero or more signature subpackets. Each set of subpackets is preceded by a two-octet scalar count of the length of the set of subpackets. Each subpacket consists of a subpacket header and a body. The header consists of:
The length includes the type octet but not this length. Its format is similar to the "new" format packet header lengths, but cannot have partial body lengths. That is:
The value of the subpacket type octet may be:
An implementation SHOULD ignore any subpacket of a type that it does not recognize. Bit 7 of the subpacket type is the "critical" bit. If set, it denotes that the subpacket is one that is critical for the evaluator of the signature to recognize. If a subpacket is encountered that is marked critical but is unknown to the evaluating software, the evaluator SHOULD consider the signature to be in error. |
|
9.2. Symmetric Key Algorithms
Implementations MUST implement Triple-DES. Implementations SHOULD implement IDEA and CAST5. Implementations MAY implement any other algorithm. |
|
4.3. Packet Tags The packet tag denotes what type of packet the body holds. Note that old format headers can only have tags less than 16, whereas new format headers can have tags as great as 63. Referenced by pgpIsPkt(), pgpPrtComment(), pgpPrtKey(), pgpPrtPkt(), pgpPrtPkts(), pgpPrtSig(), pgpPrtSigParams(), and pgpPrtUserID(). |
|
Referenced by pgpPrtVal(), pgpValStr(), and pgpValTok(). |
|
|
|
|
|
9.3. Compression Algorithms
Implementations MUST implement uncompressed data. Implementations SHOULD implement ZIP. Implementations MAY implement ZLIB. |
|
9.4. Hash Algorithms
Implementations MUST implement SHA-1. Implementations SHOULD implement MD5.
|
|
|
5.2.1. Signature Types There are a number of possible meanings for a signature, which are specified in a signature type octet in any given signature.
|
|
5.2.3.1. Signature Subpacket Specification The subpacket fields consist of zero or more signature subpackets. Each set of subpackets is preceded by a two-octet scalar count of the length of the set of subpackets. Each subpacket consists of a subpacket header and a body. The header consists of:
The length includes the type octet but not this length. Its format is similar to the "new" format packet header lengths, but cannot have partial body lengths. That is:
The value of the subpacket type octet may be:
An implementation SHOULD ignore any subpacket of a type that it does not recognize. Bit 7 of the subpacket type is the "critical" bit. If set, it denotes that the subpacket is one that is critical for the evaluator of the signature to recognize. If a subpacket is encountered that is marked critical but is unknown to the evaluating software, the evaluator SHOULD consider the signature to be in error.
|
|
9.2. Symmetric Key Algorithms
Implementations MUST implement Triple-DES. Implementations SHOULD implement IDEA and CAST5. Implementations MAY implement any other algorithm.
|
|
4.3. Packet Tags The packet tag denotes what type of packet the body holds. Note that old format headers can only have tags less than 16, whereas new format headers can have tags as great as 63.
|
|
Definition at line 1258 of file rpmpgp.h. References CRC24_INIT, and CRC24_POLY. Referenced by pgpReadPkts(). |
|
Definition at line 995 of file rpmpgp.c. References _free(), pgpDig_s::c, pgpDigParams_s::hash, pgpDig_s::hm, pgpDig_s::m, pgpDig_s::md5, pgpDig_s::md5ctx, pgpDigParams_s::params, pgpDig_s::pubkey, pgpDig_s::r, rpmDigestFinal(), pgpDig_s::rsa_pk, pgpDig_s::rsahm, pgpDig_s::s, pgpDig_s::sha1, pgpDig_s::sha1ctx, pgpDig_s::signature, and pgpDigParams_s::userid. |
|
Definition at line 1014 of file rpmpgp.h. Referenced by pgpLen(), pgpMpiStr(), pgpPrtKey(), pgpPrtPkt(), pgpPrtSig(), pgpPrtSubType(), and pgpReadPkts(). |
|
Definition at line 1063 of file rpmpgp.h. Referenced by pgpHexStr(), pgpMpiHex(), and pgpMpiStr(). |
|
Definition at line 1080 of file rpmpgp.h. References pgpHexCvt(). Referenced by pgpPrtHex(), and pgpPrtSig(). |
|
Definition at line 1202 of file rpmpgp.h. References pgpTag, PGPTAG_COMMENT, PGPTAG_COMMENT_OLD, PGPTAG_COMPRESSED_DATA, PGPTAG_CONTROL, PGPTAG_ENCRYPTED_MDC, PGPTAG_LITERAL_DATA, PGPTAG_MARKER, PGPTAG_MDC, PGPTAG_ONEPASS_SIGNATURE, PGPTAG_PHOTOID, PGPTAG_PRIVATE_60, PGPTAG_PRIVATE_62, PGPTAG_PUBLIC_KEY, PGPTAG_PUBLIC_SESSION_KEY, PGPTAG_PUBLIC_SUBKEY, PGPTAG_RESERVED, PGPTAG_SECRET_KEY, PGPTAG_SECRET_SUBKEY, PGPTAG_SIGNATURE, PGPTAG_SYMMETRIC_DATA, PGPTAG_SYMMETRIC_SESSION_KEY, PGPTAG_TRUST, and PGPTAG_USER_ID. Referenced by pgpReadPkts(). |
|
Definition at line 1027 of file rpmpgp.h. References pgpGrab(). Referenced by pgpPrtPkt(), and pgpPrtSubType(). |
|
Definition at line 1045 of file rpmpgp.h. Referenced by pgpHexSet(), and pgpMpiLen(). |
|
Definition at line 1054 of file rpmpgp.h. References pgpMpiBits(). Referenced by pgpMpiHex(), pgpMpiStr(), pgpPrtPubkeyParams(), pgpPrtSeckeyParams(), and pgpPrtSigParams(). |
|
Definition at line 1092 of file rpmpgp.h. References pgpGrab(), pgpHexCvt(), and pgpMpiLen(). Referenced by pgpPrtPubkeyParams(), pgpPrtSeckeyParams(), and pgpPrtSigParams(). |
|
Definition at line 989 of file rpmpgp.c. References xcalloc(). |
|
Definition at line 894 of file rpmpgp.c. References _print, pgpPrtHex(), pgpPrtNL(), pgpPrtVal(), pgpTag, and pgpTagTbl. Referenced by pgpPrtPkt(). |
|
Definition at line 815 of file rpmpgp.c. References _digp, _print, pgpGrab(), pgpPktKeyV3, pgpPktKeyV4, pgpPrtNL(), pgpPrtPubkeyParams(), pgpPrtSeckeyParams(), pgpPrtVal(), pgpPubkeyTbl, pgpTag, PGPTAG_PUBLIC_KEY, PGPTAG_PUBLIC_SUBKEY, pgpTagTbl, pgpPktKeyV4_s::pubkey_algo, pgpDigParams_s::pubkey_algo, pgpPktKeyV3_s::pubkey_algo, pgpDigParams_s::tag, pgpPktKeyV4_s::time, pgpDigParams_s::time, pgpPktKeyV3_s::time, pgpPktKeyV3_s::valid, pgpPktKeyV4_s::version, pgpPktKeyV3_s::version, and pgpDigParams_s::version. Referenced by pgpPrtPkt(). |
|
Definition at line 920 of file rpmpgp.c. References pgpGrab(), pgpLen(), pgpPrtComment(), pgpPrtHex(), pgpPrtKey(), pgpPrtNL(), pgpPrtSig(), pgpPrtUserID(), pgpPrtVal(), pgpTag, PGPTAG_COMMENT, PGPTAG_COMMENT_OLD, PGPTAG_COMPRESSED_DATA, PGPTAG_CONTROL, PGPTAG_ENCRYPTED_MDC, PGPTAG_LITERAL_DATA, PGPTAG_MARKER, PGPTAG_MDC, PGPTAG_PHOTOID, PGPTAG_PRIVATE_60, PGPTAG_PRIVATE_62, PGPTAG_PUBLIC_KEY, PGPTAG_PUBLIC_SESSION_KEY, PGPTAG_PUBLIC_SUBKEY, PGPTAG_RESERVED, PGPTAG_SECRET_KEY, PGPTAG_SECRET_SUBKEY, PGPTAG_SIGNATURE, PGPTAG_SYMMETRIC_DATA, PGPTAG_SYMMETRIC_SESSION_KEY, PGPTAG_TRUST, PGPTAG_USER_ID, and pgpTagTbl. Referenced by pgpPrtPkts(). |
|
Definition at line 1038 of file rpmpgp.c. References _dig, _digp, _print, pgpPrtPkt(), pgpTag, PGPTAG_SIGNATURE, pgpDig_s::pubkey, pgpDig_s::signature, and pgpDigParams_s::tag. |
|
Definition at line 500 of file rpmpgp.c. References _debug, _digp, _print, pgpDigParams_s::hash, pgpPktSigV4_s::hash_algo, pgpDigParams_s::hash_algo, pgpPktSigV3_s::hash_algo, pgpPktSigV4_s::hashlen, pgpDigParams_s::hashlen, pgpPktSigV3_s::hashlen, pgpGrab(), pgpHashTbl, pgpHexStr(), pgpPktSigV3, pgpPktSigV4, pgpPrtHex(), pgpPrtNL(), pgpPrtSigParams(), pgpPrtSubType(), pgpPrtVal(), pgpPubkeyTbl, pgpSigTypeTbl, pgpTag, pgpTagTbl, pgpPktSigV4_s::pubkey_algo, pgpDigParams_s::pubkey_algo, pgpPktSigV3_s::pubkey_algo, pgpDigParams_s::signhash16, pgpPktSigV3_s::signhash16, pgpDigParams_s::signid, pgpPktSigV3_s::signid, pgpPktSigV4_s::sigtype, pgpDigParams_s::sigtype, pgpPktSigV3_s::sigtype, pgpDigParams_s::time, pgpPktSigV3_s::time, pgpPktSigV4_s::version, pgpPktSigV3_s::version, pgpDigParams_s::version, and xmalloc(). Referenced by pgpPrtPkt(). |
|
Definition at line 341 of file rpmpgp.c. References _digp, _print, pgpCompressionTbl, pgpGrab(), pgpHashTbl, pgpKeyServerPrefsTbl, pgpLen(), pgpPrtHex(), pgpPrtNL(), pgpPrtVal(), PGPSUBTYPE_BACKWARD_COMPAT, PGPSUBTYPE_EXPORTABLE_CERT, PGPSUBTYPE_INTERNAL_100, PGPSUBTYPE_INTERNAL_101, PGPSUBTYPE_INTERNAL_102, PGPSUBTYPE_INTERNAL_103, PGPSUBTYPE_INTERNAL_104, PGPSUBTYPE_INTERNAL_105, PGPSUBTYPE_INTERNAL_106, PGPSUBTYPE_INTERNAL_107, PGPSUBTYPE_INTERNAL_108, PGPSUBTYPE_INTERNAL_109, PGPSUBTYPE_INTERNAL_110, PGPSUBTYPE_ISSUER_KEYID, PGPSUBTYPE_KEY_EXPIRE_TIME, PGPSUBTYPE_KEY_FLAGS, PGPSUBTYPE_KEYSERVER_PREFERS, PGPSUBTYPE_NOTATION, PGPSUBTYPE_POLICY_URL, PGPSUBTYPE_PREFER_COMPRESS, PGPSUBTYPE_PREFER_HASH, PGPSUBTYPE_PREFER_KEYSERVER, PGPSUBTYPE_PREFER_SYMKEY, PGPSUBTYPE_PRIMARY_USERID, PGPSUBTYPE_REGEX, PGPSUBTYPE_REVOCABLE, PGPSUBTYPE_REVOKE_KEY, PGPSUBTYPE_REVOKE_REASON, PGPSUBTYPE_SIG_CREATE_TIME, PGPSUBTYPE_SIG_EXPIRE_TIME, PGPSUBTYPE_SIGNER_USERID, PGPSUBTYPE_TRUST_SIG, pgpSubTypeTbl, pgpSymkeyTbl, PGPTAG_PUBLIC_KEY, pgpDigParams_s::signid, pgpDigParams_s::tag, and pgpDigParams_s::time. Referenced by pgpPrtSig(). |
|
Definition at line 878 of file rpmpgp.c. References _digp, _print, pgpPrtNL(), pgpPrtVal(), pgpTag, pgpTagTbl, pgpDigParams_s::userid, and xmalloc(). Referenced by pgpPrtPkt(). |
|
Definition at line 296 of file rpmpgp.c. References _print, pgpValStr(), and pgpValTbl. Referenced by pgpPrtComment(), pgpPrtKey(), pgpPrtPkt(), pgpPrtSeckeyParams(), pgpPrtSig(), pgpPrtSubType(), and pgpPrtUserID(). |
|
Definition at line 1064 of file rpmpgp.c. References _free(), pgpArmor, PGPARMOR_ERROR, PGPARMOR_NONE, PGPARMOR_PUBKEY, pgpArmorKeyTbl, pgpArmorTbl, pgpCRC(), pgpGrab(), pgpIsPkt(), pgpValTok(), rpmioSlurp(), and TOKEQ. |
|
Definition at line 1106 of file rpmpgp.h. References pgpValTbl. Referenced by armorFormat(), and pgpPrtVal(). |
|
Definition at line 1119 of file rpmpgp.h. References pgpValTbl. Referenced by pgpReadPkts(). |
|
Definition at line 950 of file rpmpgp.h. Referenced by pgpReadPkts(). |
|
Definition at line 933 of file rpmpgp.h. Referenced by armorFormat(), and pgpReadPkts(). |
|
Definition at line 259 of file rpmpgp.h. Referenced by pgpPrtSubType(). |
|
Definition at line 294 of file rpmpgp.h. Referenced by pgpPrtSeckeyParams(), pgpPrtSig(), and pgpPrtSubType(). |
|
Definition at line 186 of file rpmpgp.h. Referenced by pgpPrtKey(), and pgpPrtSig(). |
|
Definition at line 144 of file rpmpgp.h. Referenced by pgpPrtSig(). |
|
Definition at line 463 of file rpmpgp.h. Referenced by pgpPrtSubType(). |
|
Definition at line 231 of file rpmpgp.h. Referenced by pgpPrtSeckeyParams(), and pgpPrtSubType(). |
|
Definition at line 70 of file rpmpgp.h. Referenced by pgpPrtComment(), pgpPrtKey(), pgpPrtPkt(), pgpPrtSig(), and pgpPrtUserID(). |