-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
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
[FEATURE REQUEST] - order of "ecccurvebindings" #1058
Comments
Hey @adc-nerd |
The curve binding order is security and performance related. It's like cipher order. https://support.citrix.com/article/CTX205289/ |
Hello @adc-nerd We recommend you to use |
Thanks for the info but we use "citrixadc_sslparameter" with "defaultprofile" enabled. Is it already fixed for "citrixadc_sslprofile"? Because documentation states "The default ecccurvebindings will be DELETED and only the explicitly given ecccurvebindings will be retained". https://registry.terraform.io/providers/citrix/citrixadc/latest/docs/resources/sslprofile Is "X_25519" also supported? |
Hello @adc-nerd So, In the documentation of I did check with the internal team regrading the support for |
This is a request for ecc binding order in ssl-profiles. It's no longer recommended to use ssl settings per service. |
Feature Request
Is your feature request related to a problem? Please describe.
ECC curve binding order should be honored.
There is a difference between:
resource "citrixadc_sslprofile" "my_sslprofile" { ecccurvebindings = ["P_256", "P_384", "P_521"] ... }
and
resource "citrixadc_sslprofile" "my_sslprofile" { ecccurvebindings = ["P_521", "P_384", "P_256"] ... }
Describe the solution you'd like
Ecc curve binding order should be observed.
Provider need to unbind/bind ecc curves to accomblish binding order.
Additional context
ECC curve order is security and performance related.
The text was updated successfully, but these errors were encountered: