On 6/17/19 2:58 PM, Florian Obser wrote:
Let's Encrypt accepts P-256 and P-384 ECDSA keys for both account keys and certificate keys. But there is no point using P-256 when you can do P-384.What would be the correct calculation for a GF2m field? Should I maybe just ignore it? RFC 7518 only lists P-256, P-384 and P-521 (and I think Let's Encrypt only supports P-384 anyway), and they are all GFp, no?
Maybe it would be best to skip the whole degree calculation and hardcode bn_len as 48.
That's probably the easiest since we would only support P-384
smime.p7s
Description: S/MIME Cryptographic Signature
