SI: Unsupported Elliptic Curve
See original GitHub issue@DragoMlakar SI’s certificates signing algorithm use this elliptic curve c2tnb191v1: X9.62 curve over a 191 bit binary field
according to ASN1 decoding. Are we supposed to support it or you are planning to change it to something like prime256v1
?
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
TLS Elliptic Curve not supported - Server Fault
i.e. The device provides a list of curves it supports, yet the server returns a cert chain with a non-supported EC in the...
Read more >Efficient ephemeral elliptic curve cryptographic keys
Abstract. We show how any pair of authenticated users can on-the-fly agree on an el liptic curve group that is unique to their...
Read more >Exploiting dummy codes in Elliptic Curve Cryptography ... - Sstic
With the growing interest of Elliptic Curve Cryptography, ... Given n ECDSA signatures (ri,si) with their corresponding messages.
Read more >Elliptic Curve Cryptography Functions - Intel
Intel IPP Cryptography supports some elliptic curves with fixed parameters, the so-called standard or recommended curves.
Read more >010717e6:3: EC key contains unsupported curve - AskF5
This error message indicates the system attempted to load an SSL object with an unsupported ECC curve. This would most likely be seen...
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 FreeTop 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
Top GitHub Comments
@vanton1 I’ve added that to the list : https://github.com/eu-digital-green-certificates/dgc-testdata/blob/main/BasicDgcTestsList.md#issuer-quality-checks
@jozemlakar this seems to be fixed, but please see #220, the PR introduced new issues