Allow to override supportedCOSEAlgorithmIdentifiers
See original GitHub issueIt would be useful to be able to override supportedCOSEAlgorithmIdentifiers
here: https://github.com/MasterKale/SimpleWebAuthn/blob/master/packages/server/src/attestation/generateAttestationOptions.ts#L85-L88
For example to support only -7
ES256 and -257
RS256.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
override identifier in C++ - GeeksforGeeks
override identifier in C++ Function overriding is a redefinition of the base class function in its derived class with the same signature i.e. ......
Read more >Overriding algorithms (GnuTLS 3.7.8)
This function will register a cipher algorithm to be used by gnutls. Any algorithm registered will override the included algorithms and by convention...
Read more >RFC 3279 - Algorithms and Identifiers for the Internet X.509 ...
Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile (RFC 3279, May 2002)
Read more >Restrict cryptographic algorithms and protocols - Microsoft Learn
Discusses how to restrict the use of certain cryptographic algorithms and protocols in Schannel.dll.
Read more >crypto/x509: inner and outer signature algorithm identifiers ...
An awful lot of work to go to just in order to get it to accept a non-ideal certificate, whereas a web browser...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Alright, no ID’s will be filtered out of custom arrays of ID’s passed in as
supportedAlgorithmIDs
when callinggenerateAttestationOptions()
🎉This is fixed as of @simplewebauthn/server v0.8.1
Okay, I’ll admit I see the argument for letting implementers specify even deprecated algorithms when passing in their own list of supported values. I suppose it’s painless to move the
.filter()
to the initialization of the default array of algorithms…