Reported by German Parente:
When nsSSL3 is enabled but SSL3 is not to sslVersionMin explicitely: cn=encryption,cn=config. sslVersionMin: SSL3 nsSSL3: on It's confusing that there's a case where customer can see this: ==================== [22/Mar/2016:20:01:52 +0100] - SSL alert: Found unsecure configuration: nsSSL3: on; We strongly recommend to disable nsSSL3 in cn=encryption,cn=config. ==================== Then, he/she goes to the console to change this value and the console shows it as "off". Then, he/she does a ldapsearch and the result is also "off". But the logs tell him/her it's on.
git patch file (master) 0001-Ticket-48775-If-nsSSL3-is-on-even-if-SSL-v3-is-not-r.patch
Reviewed by Mark (Thank you!!)
Pushed to master: 10787a0..9b3c273 master -> master commit 9b3c273
Metadata Update from @nhosoi: - Issue assigned to nhosoi - Issue set to the milestone: 1.3.5.2
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/1835
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)
Login to comment on this ticket.