restore language of table but fix layout

This commit is contained in:
Tammi L. Coles 2023-11-25 11:04:59 +01:00
parent 8e81ed6b36
commit 8fe5dfcf33

View file

@ -308,12 +308,12 @@ Additionally, the expiration date can be altered for individual User IDs (detail
To bind a User ID to an OpenPGP certificate, the signature should have the following structure: To bind a User ID to an OpenPGP certificate, the signature should have the following structure:
| Subpacket | Area | Critical | Mandatory | Notes | | Subpacket | Area | Critical | Mandatory | Notes |
|-------------------------|--------|----------------|-------------------|---------------------------------------| |-------------------------|--------|----------------|-------------------|-------------------------------------------------|
| Signature Creation Time | Hashed | True | True | Current time | | Signature Creation Time | Hashed | True | True | Current time |
| Issuer Fingerprint | Hashed | True or False | Strongly Recommended | Identifies the primary key as the issuer | | Issuer Fingerprint | Hashed | True or False | Strongly Recommended | The primary key is the issuer |
| Primary User ID | Hashed | True | False | Optional | | Primary User ID | Hashed | True | False | Optional |
| Signature Expiration Time | Hashed | True | False | Optional | | Signature Expiration Time | Hashed | True | False | Optional |
In addition to these subpackets, self-certifications for User IDs can include others such as key flags, features, and algorithm preferences as shown in the previous table. This enables the specification of unique capabilities and preferences for each identity associated with the certificate. In addition to these subpackets, self-certifications for User IDs can include others such as key flags, features, and algorithm preferences as shown in the previous table. This enables the specification of unique capabilities and preferences for each identity associated with the certificate.