#47880 provide enabled ciphers as search result
Closed: wontfix None Opened 7 years ago by lkrispen.

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) -- CI test: added test cases for ticket 47880

Reviewed by Mark (Thank you!!)

Pushed to master:
50820f8..ce73789 master -> master
commit c675243
commit ce73789

Pushed to 389-ds-base-1.3.3:
ab36560..b922e5d 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
commit 8de8053
commit b922e5d

Pushed to 389-ds-base-1.2.11:
099d1ce..8550aaf 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit 8550aaf

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 d598ed5

Metadata Update from @nhosoi:
- Issue assigned to nhosoi
- Issue set to the milestone:

4 years ago

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.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

a year ago

Login to comment on this ticket.