Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am having exactly the same error using RHEL 6.3 and OpenDJ 2.4.5.
RedHat support has been no help.
All of my RHEL 5 LDAP clients have no trouble at all connecting either in the clear, using startTLS, or using LDAPS.
On RHEL 6, id, getent, and ldapsearch all give errors when attempting to connect using startTLS or LDAPS. The only way I've found to get RHEL 6 to play even sort-of nice with OpenDJ/LDAP is to use the option "ldap_auth_disable_tls_never_use_in_production = TRUE" in /etc/sssd/sssd.conf, which (thank god) won't allow a change to a password since it's not an encrypted channel.
The OpenDJ server gives a log message about "no cipher suites in common", which isn't very helpful, as that seems to be the "default" message when something goes wrong with SSL negotiation.
I know my certificates are good, since they work for all the RHEL 5 clients. I also know that startTLS works on the LDAP server, since all the RHEL 5 clients can do that successfully as well.
Any thoughts, anyone?
Last edited by sjhauer; 11-09-2012 at 12:11 PM.
Reason: fix typos and additional informartion