Last Modified: May 01, 2019
See more info
Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 13.1.1, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11
Opened: Sep 05, 2017
Changes to a cipher group, even indirect changes such as changing an underlying cipher rule, will not be propagated to the SSL profiles until the configuration is reloaded.
The available ciphers on an SSL profile might not be as expected.
-- An SSL profile is using cipher groups (instead of the cipher string). -- Some changes are made to that group.
You can use either of the following workarounds: -- Always reload the configuration after changing a cipher group. -- Use the existing cipher string mechanism instead.
With this change, changes to a cipher group are correctly propagated to the SSL profiles, so no configuration reload is required.