We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Is this symptom still reproducible in 8.10 or a 9.04 daily-live?
** Changed in: gq (Ubuntu)
Importance: Medium = Undecided
Assignee: (unassigned) = Daniel T Chen (crimsun)
Status: New = Incomplete
--
gq reports error in SSL cert even though if tls_checkpeer no is set in ldap.conf
Thanks for the information, Sailor. From looking at the source, only the
first part of the error message comes from GQ (Couldn't bind LDAP
connection to '%s': %s). The part after the colon is the error message
from libldap. Are you sure this works with a different ldap client using
libldap?
--
This is way I love open source. Opening a 1,5 year old thread and
getting answer within 2 hours. Respect!
In this case I'm only a human...
I'm using LDAP for login on the clients via GDM - so I guess it works then.
I can for example do an ldapsearch -x with a full answer from my LDAP-server.
I don't know if it will help to bugreport in this old thread but
obviously I have the same problem as Harrison.
Running Gustsy on both server and clients. No problem using gq when ldap was
unencrypted. But when I'm using TLS with a selfsigned certificate on the server
I only got the following
Harrison, what's the exact error message that you encounter?
(I'm GQ's upstream developer, and this won't make it at least into GQ
1.2.0 next week, but I'd like to get this fixed for the 1.4 release in 6
months)
--
gq reports error in SSL cert even though if tls_checkpeer no is set in ldap.conf
** Changed in: gq (Ubuntu)
Status: Needs Info = Unconfirmed
--
gq reports error in SSL cert even though if tls_checkpeer no is set in ldap.conf
https://launchpad.net/bugs/37198
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
