No. I had not. I just did, however, install it on my test system, and it still gets the same diagnostic:
trace 5 oops, Can't contact LDAP server I was really hoping when I saw your post that you had found the problem. I wonder if there is some other combination I might have left out. It would be great if this was just a matter of my leaving out a package, or a package omitting a dependency, but people that helped me test this seemed to indicate the certificate was just not being seen. If we could know a place to put the certs where it would be seen that would fix it apparently, as the shell command openssl does the activities properly, and this only fails in the ruby package. However it would also be nice if 1) one could specify a location from the API, 2) one could see clear documentation of the proper location for the cert, 3) one could turn off the cert requirement from the API, and 4) a cert in the same directory as the script programmed was automatically seen for the purposes of testing and simple use. I highly recommen all these 4 items. If I can help I shall. Please someone recommend a next step for me to test or try. -- LDAP::SSLConn from ruby fails, probably from not seeing cert https://bugs.launchpad.net/bugs/381791 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
