Feature description
The default algorithm used for web certificate is the prime256v1 and it could be increased, but it would impact on the CPU; for compatibility, that is probably the best as of today.
The signature algorithm used (for web certificate only) is based on the SHA256; the SHA1 has been flagged as insecure; to be "future proof" would be possible to move to SHA512?
Problem or use case
Just to be future proof, using the immediate next Hash Signature Algo level.
Alternatives or workarounds
Leave everything as it is. It has none known security issue as of today.
Feature description
The default algorithm used for web certificate is the
prime256v1and it could be increased, but it would impact on the CPU; for compatibility, that is probably the best as of today.The signature algorithm used (for web certificate only) is based on the SHA256; the SHA1 has been flagged as insecure; to be "future proof" would be possible to move to SHA512?
Problem or use case
Just to be future proof, using the immediate next Hash Signature Algo level.
Alternatives or workarounds
Leave everything as it is. It has none known security issue as of today.