We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The certificate uses Elliptic Curve Cryptography (ECC):
var ec = ECDsa.Create(ECCurve.NamedCurves.nistP256); in SharedFunctions.cs
var ec = ECDsa.Create(ECCurve.NamedCurves.nistP256);
Unfortunately in Azure App Service Elliptic Curve Cryptography (ECC) certificates are supported only with TLS 1.2.
So if we need to support TLS 1.0 and TLS 1.1 only clients we have to stick with RSA certificates.
Could you make the chiper method configurable?
The text was updated successfully, but these errors were encountered:
For safety web, TLS 1.0 / 1.1 has been disabled worldwide. I will not change this behavior.
Sorry, something went wrong.
No branches or pull requests
The certificate uses Elliptic Curve Cryptography (ECC):
var ec = ECDsa.Create(ECCurve.NamedCurves.nistP256);
in SharedFunctions.csUnfortunately in Azure App Service Elliptic Curve Cryptography (ECC) certificates are supported only with TLS 1.2.
So if we need to support TLS 1.0 and TLS 1.1 only clients we have to stick with RSA certificates.
Could you make the chiper method configurable?
The text was updated successfully, but these errors were encountered: