The current ldclt on master fails to connect to the server via SSL since the server side disables SSLv3 by default.
[..] conn=134 fd=64 slot=64 SSL connection from ::1 to ::1 [..] conn=134 op=-1 fd=64 closed - Cannot communicate securely with peer: no common encryption algorithm(s).
git patch file (master) 0001-Ticket-47996-ldclt-needs-to-support-SSL-Version-rang.patch
Reviewed by Rich (Thank you!!)
Pushed to master: 67177a2..7c30e11 master -> master commit 7c30e11
Pushed to 389-ds-base-1.3.3: 45ee5cb..6431142 389-ds-base-1.3.3 -> 389-ds-base-1.3.3 commit 6431142
Pushed to 389-ds-base-1.3.2: 4b914f2..cef5810 389-ds-base-1.3.2 -> 389-ds-base-1.3.2 commit cef5810
Pushed to 389-ds-base-1.2.11: 340b9dc..d26ed48 389-ds-base-1.2.11 -> 389-ds-base-1.2.11 commit d26ed48
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1185025
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/1327
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.