-
Notifications
You must be signed in to change notification settings - Fork 151
Should key usages be tracked as a HashSet instead? #265
Open
Description
In #264 code is pretty ugly because we're keeping track of whether an EKU already exists in the Vec that we hold. Should CertificateParams::key_usages and extended_key_usages be HashSet instead?
- Does the order matter?
- Is there a valid use case for having the same usage twice?
(I guess it could even be more like a bitset similar to what x509-parser apparently does.)
Metadata
Metadata
Assignees
Type
Fields
Give feedbackNo fields configured for issues without a type.