-
Notifications
You must be signed in to change notification settings - Fork 18.4k
Open
Labels
FeatureRequestIssues asking for a new feature that does not need a proposal.Issues asking for a new feature that does not need a proposal.NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Description
I've checked #19974.
And, I am aware of comment #19974 (comment).
SignPSS/VerifyPSS have almost the same problem as that issue.
I wanted to call SignPSS using RSASSA-PSS with SHA-256 with MGF1SHA1 because server which is hosted by third party needs that, but I couldn't.
It seems good to simply add option MGF1Hash
to PSSOptions. It is not invasing, and keep backwards compatibility.
If there are no counter-proposals, I' ll create a patch.
// PSSOptions contains options for creating and verifying PSS signatures.
type PSSOptions struct {
SaltLength int
Hash crypto.Hash
// ADD OPTION HERE
// MGF1Hash is the hash function used for MGF1 .
// If zero, hash function used to generate the message digest will be used.
MGF1Hash crypto.Hash
}
hmmftg, Numenorean and terrafrost
Metadata
Metadata
Assignees
Labels
FeatureRequestIssues asking for a new feature that does not need a proposal.Issues asking for a new feature that does not need a proposal.NeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.