Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Signatures (CSAF 2.1) #729

Merged
merged 1 commit into from
May 12, 2024
Merged

Signatures (CSAF 2.1) #729

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions csaf_2.1/prose/edit/src/distributing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -419,6 +419,16 @@ File name of signature file: esa-2022-02723.json.asc

If a ROLIE feed exists, each signature file MUST be listed in it as described in requirement 15.

At all times, signatures MUST remain valid for a minimum of 30 days and ideally for at least 90 days. When executing
CSAF document signatures, the signing party SHOULD adhere to or surpass the prevailing best practices and recommendations
regarding key length.
Tools SHOULD treat the violation of the rules given in the first sentence as:

* warning if the signature is only valid for 90 days or less at the time of the verification,
* error, which MAY be ignored by the user per option, if the signature is only valid for 30 days or less at the time of
the verification and
* error if the signature is expired at the time of the verification.

### Requirement 20: Public OpenPGP Key

The public part of the OpenPGP key used to sign the CSAF documents MUST be available.
Expand Down
Loading