vanitasvitae/openpgp-notes
1
0
Fork 0
mirror of https://codeberg.org/openpgp/notes.git synced 2025-09-10 19:59:40 +02:00
Code Issues Projects Releases Packages Wiki Activity

Normalize term: effective -> in effect

Browse source
This commit is contained in:
Heiko Schaefer 2023-11-18 22:31:23 +01:00
parent 04ae1fb0a8
commit 1ee3024056
No known key found for this signature in database
GPG key ID: DAE9A9050FCCF1EB
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
book/source/09-verification.md
View file

@ -44,7 +44,7 @@ A signature is valid only for a constrained period of time:
When checking a signature for validity, a reference time is used.
This can be the current time during validation, or a point in time that relates to the signature that is getting checked.
For example, when checking a signature in an email, the reference time might be the signature creation time, or the time of receipt for the email.
For the signature to qualify as valid, it needs to be effective. In other words, the reference time must fall into the period between signature creation and signature expiration.
For the signature to qualify as valid, it needs to be in effect. In other words, the reference time must fall into the period between signature creation and signature expiration.
The same reference time must be used when verifying additional qualifying signatures.
@ -94,8 +94,8 @@ Note: Attribute shadowing should only be used for algorithm preferences, since t
### Signature shadowing
When inspecting signatures on a component of an OpenPGP certificate, only the newest, effective signature for each function is considered.
In other words; If there are three binding signatures `A, B, C` for a subkey, where `A` was created at `t0`, `B` at `t1` and `C` at `t3` with `t0 < t1 < t2 < t3`, at `t2` an implementation only needs to consider `B`, as `C` is not yet effective. `A` is shadowed, because it is older than `B`.
When inspecting signatures on a component of an OpenPGP certificate, of the signatures that are in effect for each function, only the newest is considered.
In other words; If there are three binding signatures `A, B, C` for a subkey, where `A` was created at `t0`, `B` at `t1` and `C` at `t3` with `t0 < t1 < t2 < t3`, at `t2` an implementation only needs to consider `B`, as `C` is not yet in effect. `A` is shadowed, because it is older than `B`.
```{figure} drawio/cert-validity-subkey.png