Open ruslandoga opened 3 weeks ago
Certbot and some other ACME clients have switched to ECDSA
It would make sense to use the same defaults as the other clients.
Thoughts on making it configurable
Also sounds sensible.
even better, guessed from the private key provided
Which provided key? IIRC we don't accept any key as the input.
Anyway, contributions in this are are welcome :-)
Which provided key? IIRC we don't accept any key as the input.
I was thinking about the account_key here https://github.com/sasa1977/site_encrypt/blob/735105d88bfd319ba8e7692c205433c34b7d246f/lib/site_encrypt/acme/client/api.ex#L87 but yeah, it would need to be configured for SiteEncrypt anyway so we can just get alg
from the config instead of guessing it from the key. I'll try to prepare a PR tomorrow this weekend early later next week!
Certbot and some other ACME clients have switched to ECDSA by default some time ago. Currently,
alg
is hardcoded in SiteEncrypt's native client. Thoughts on making it configurable or even better, guessed from the private key provided?Some notable discussions: