-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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.
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
common: add more RSA-PSS algorithm id definitions #9412
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -234,6 +234,22 @@ pub const PSS_SHA1_HASH_ALG: AlgorithmIdentifier<'_> = AlgorithmIdentifier { | |
params: AlgorithmParameters::Sha1(Some(())), | ||
}; | ||
|
||
// RSA-PSS ASN.1 hash algorithm definitions specified under the CA/B Forum BRs. | ||
pub const PSS_SHA256_HASH_ALG: AlgorithmIdentifier<'_> = AlgorithmIdentifier { | ||
oid: asn1::DefinedByMarker::marker(), | ||
params: AlgorithmParameters::Sha256(Some(())), | ||
}; | ||
|
||
pub const PSS_SHA384_HASH_ALG: AlgorithmIdentifier<'_> = AlgorithmIdentifier { | ||
oid: asn1::DefinedByMarker::marker(), | ||
params: AlgorithmParameters::Sha384(Some(())), | ||
}; | ||
|
||
pub const PSS_SHA512_HASH_ALG: AlgorithmIdentifier<'_> = AlgorithmIdentifier { | ||
oid: asn1::DefinedByMarker::marker(), | ||
params: AlgorithmParameters::Sha512(Some(())), | ||
}; | ||
|
||
// This is defined as an AlgorithmIdentifier in RFC 4055, | ||
// but the mask generation algorithm **must** contain an AlgorithmIdentifier | ||
// in its params, so we define it this way. | ||
|
@@ -249,6 +265,22 @@ pub const PSS_SHA1_MASK_GEN_ALG: MaskGenAlgorithm<'_> = MaskGenAlgorithm { | |
params: PSS_SHA1_HASH_ALG, | ||
}; | ||
|
||
// RSA-PSS ASN.1 mask gen algorithms defined under the CA/B Forum BRs. | ||
pub const PSS_SHA256_MASK_GEN_ALG: MaskGenAlgorithm<'_> = MaskGenAlgorithm { | ||
oid: oid::MGF1_OID, | ||
params: PSS_SHA256_HASH_ALG, | ||
}; | ||
|
||
pub const PSS_SHA384_MASK_GEN_ALG: MaskGenAlgorithm<'_> = MaskGenAlgorithm { | ||
oid: oid::MGF1_OID, | ||
params: PSS_SHA384_HASH_ALG, | ||
}; | ||
|
||
pub const PSS_SHA512_MASK_GEN_ALG: MaskGenAlgorithm<'_> = MaskGenAlgorithm { | ||
oid: oid::MGF1_OID, | ||
params: PSS_SHA512_HASH_ALG, | ||
}; | ||
Comment on lines
+268
to
+282
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. NB: No coverage needed since these are just data, but for maximum correctness I could also test these against the exact expected DER encodings supplied by the CABF rules. |
||
|
||
// From RFC 4055 section 3.1: | ||
// RSASSA-PSS-params ::= SEQUENCE { | ||
// hashAlgorithm [0] HashAlgorithm DEFAULT | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this comment really correct? It's not really defined by CABF, these come from the RFCs, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that's right, although CABF doesn't make reference to the RFCs for their definitions of these. Want me to dig them up regardless?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://www.rfc-editor.org/rfc/rfc8017 looks like the right RFC, although it doesn't explicitly parametrize these the way CABF does.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, really? I just assumed that these were all natural consequences of how it worked, and didn't need to be explicitly specified (same as SHA1)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, CABF specifies the precise set that can be used (and provides their exact DER encodings as well) -- both are on page 97 of the PDF I linked in the top.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok