MCPcopy Create free account
hub / github.com/SecurityInnovation/PGPy / PGPKey

Class PGPKey

pgpy/pgp.py:1296–2676  ·  view source on GitHub ↗

11.1. Transferable Public Keys OpenPGP users may transfer public keys. The essential elements of a transferable public key are as follows: - One Public-Key packet - Zero or more revocation signatures - One or more User ID packets - After each User ID packet, ze

Source from the content-addressed store, hash-verified

1294
1295
1296class PGPKey(Armorable, ParentRef, PGPObject):
1297 """
1298 11.1. Transferable Public Keys
1299
1300 OpenPGP users may transfer public keys. The essential elements of a
1301 transferable public key are as follows:
1302
1303 - One Public-Key packet
1304
1305 - Zero or more revocation signatures
1306 - One or more User ID packets
1307
1308 - After each User ID packet, zero or more Signature packets
1309 (certifications)
1310
1311 - Zero or more User Attribute packets
1312
1313 - After each User Attribute packet, zero or more Signature packets
1314 (certifications)
1315
1316 - Zero or more Subkey packets
1317
1318 - After each Subkey packet, one Signature packet, plus optionally a
1319 revocation
1320
1321 The Public-Key packet occurs first. Each of the following User ID
1322 packets provides the identity of the owner of this public key. If
1323 there are multiple User ID packets, this corresponds to multiple
1324 means of identifying the same unique individual user; for example, a
1325 user may have more than one email address, and construct a User ID
1326 for each one.
1327
1328 Immediately following each User ID packet, there are zero or more
1329 Signature packets. Each Signature packet is calculated on the
1330 immediately preceding User ID packet and the initial Public-Key
1331 packet. The signature serves to certify the corresponding public key
1332 and User ID. In effect, the signer is testifying to his or her
1333 belief that this public key belongs to the user identified by this
1334 User ID.
1335
1336 Within the same section as the User ID packets, there are zero or
1337 more User Attribute packets. Like the User ID packets, a User
1338 Attribute packet is followed by zero or more Signature packets
1339 calculated on the immediately preceding User Attribute packet and the
1340 initial Public-Key packet.
1341
1342 User Attribute packets and User ID packets may be freely intermixed
1343 in this section, so long as the signatures that follow them are
1344 maintained on the proper User Attribute or User ID packet.
1345
1346 After the User ID packet or Attribute packet, there may be zero or
1347 more Subkey packets. In general, subkeys are provided in cases where
1348 the top-level public key is a signature-only key. However, any V4
1349 key may have subkeys, and the subkeys may be encryption-only keys,
1350 signature-only keys, or general-purpose keys. V3 keys MUST NOT have
1351 subkeys.
1352
1353 Each Subkey packet MUST be followed by one Signature packet, which

Callers 8

test_reg_bug_56Function · 0.90
test_empty_key_actionMethod · 0.90
test_load_blobMethod · 0.90
pubkeyMethod · 0.85
newMethod · 0.85
parseMethod · 0.85

Calls

no outgoing calls

Tested by 5

test_reg_bug_56Function · 0.72
test_empty_key_actionMethod · 0.72
test_load_blobMethod · 0.72

Used in the wild real call sites across dependent graphs

searching dependent graphs…