There is a combination of default ciphers and ciphers set by then nss3ciphers attribute which determines the enabled ciphers. It is possible to log the enabled ciphers after startup, but it would be nice to get then in a search for the "cn=encryption,cn=config" entry. The list of available ciphers is already returned by default as: nsSSLSupportedCiphers
git patch file (master) 0003-Ticket-47880-provide-enabled-ciphers-as-search-resul.patch
git patch file (master) -- CI test: added test cases for ticket 47880 0004-Ticket-47880-CI-test-added-test-cases-for-ticket-478.patch
Reviewed by Mark (Thank you!!)
Pushed to master: 50820f8..ce73789 master -> master commit c675243e018a89291760161998944c04ea04b12f commit ce7378990855abe1a5b52cd4fbe78ffc33365dcb
Pushed to 389-ds-base-1.3.3: ab36560..b922e5d 389-ds-base-1.3.3 -> 389-ds-base-1.3.3 commit 8de80533cbfdb22166f5595839307a6a6db5a636 commit b922e5d8387535a8bd71bbcea821ba08608d27c2
git patch file (1.2.11) -- Back-ported commit c675243e018a89291760161998944c04ea04b12f 0003-Ticket-47880-provide-enabled-ciphers-as-search-resul.2.patch
Pushed to 389-ds-base-1.2.11: 099d1ce..8550aaf 389-ds-base-1.2.11 -> 389-ds-base-1.2.11 commit 8550aaf90870e75b78bb6f393f9fd4aedb68d612
Pushed to 389-ds-base-1.3.1: 0680446..51714d8 389-ds-base-1.3.1 -> 389-ds-base-1.3.1 commit 51714d8768c335617abbb06d0a6f5023a985c616
Pushed to 389-ds-base-1.3.2: 712d8eb..d598ed5 389-ds-base-1.3.2 -> 389-ds-base-1.3.2 commit d598ed59179748f9f8a0ddda37ff3d714e063de0
Metadata Update from @nhosoi: - Issue assigned to nhosoi - Issue set to the milestone: 1.2.11.33
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1211
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)