Re: No appropriate error message ("rlm_ldap: could not start TLS Connect error")

2005-09-23 Thread Linus van Geuns
Alan DeKok wrote: > Linus van Geuns <[EMAIL PROTECTED]> wrote: > >>3.) Did I claim someone _has_ to fix it, because I don't 'like' it? > > > Pretty much, yes. And you then got upset when I said you could fix it. Hm, AFAIR... ah, maybe I got upset by this one: ---8<---

Re: No appropriate error message ("rlm_ldap: could not start TLS Connect error")

2005-09-23 Thread Alan DeKok
Linus van Geuns <[EMAIL PROTECTED]> wrote: > 3.) Did I claim someone _has_ to fix it, because I don't 'like' it? Pretty much, yes. And you then got upset when I said you could fix it. > 4.) I think, the error message from freeradius does obviously contain no > useful degub information. Sur

Re: No appropriate error message ("rlm_ldap: could not start TLS Connect error")

2005-09-23 Thread Linus van Geuns
Alan DeKok wrote: > Linus van Geuns <[EMAIL PROTECTED]> wrote: > >>Did I forget to tell you, I'm very sorry for intending to help others >>and mentioning that the error message is not appropriate? It was my >>fault, I should not even think of saving other peoples' time without >>getting payed for

Re: No appropriate error message ("rlm_ldap: could not start TLS Connect error")

2005-09-23 Thread Alan DeKok
Linus van Geuns <[EMAIL PROTECTED]> wrote: > Did I forget to tell you, I'm very sorry for intending to help others > and mentioning that the error message is not appropriate? It was my > fault, I should not even think of saving other peoples' time without > getting payed for it. The issue was t

Re: No appropriate error message ("rlm_ldap: could not start TLS Connect error")

2005-09-23 Thread Linus van Geuns
Alan DeKok wrote: > Linus van Geuns <[EMAIL PROTECTED]> wrote: > >>> Please mail it to the list when it's ready. >> >>I'm sorry, but I am bound to another software project atm. > > > That's terrible! > > When can we expect a fix? I'm working on a daemon that aims to implement PXE 2.1 and

Re: No appropriate error message ("rlm_ldap: could not start TLS Connect error")

2005-09-23 Thread Alan DeKok
Linus van Geuns <[EMAIL PROTECTED]> wrote: > > Please mail it to the list when it's ready. > > I'm sorry, but I am bound to another software project atm. That's terrible! When can we expect a fix? Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.h

Re: No appropriate error message ("rlm_ldap: could not start TLS Connect error")

2005-09-23 Thread Linus van Geuns
Alan DeKok wrote: > Linus van Geuns <[EMAIL PROTECTED]> wrote: > >>_And_ maybe this mail inspires some of the developers to report the >>appropriate error message instead of "rlm_ldap: could not start TLS >>Connect error". > > > You just volunteered to write the patch. > > Please mail it t

Re: No appropriate error message ("rlm_ldap: could not start TLS Connect error")

2005-09-22 Thread Alan DeKok
Linus van Geuns <[EMAIL PROTECTED]> wrote: > _And_ maybe this mail inspires some of the developers to report the > appropriate error message instead of "rlm_ldap: could not start TLS > Connect error". You just volunteered to write the patch. Please mail it to the list when it's ready. Ala

No appropriate error message ("rlm_ldap: could not start TLS Connect error")

2005-09-22 Thread Linus van Geuns
Hi! I've tried to establish a TLS-secured connection between freeradius-1.0.1-3 (Red Hat Enterprise Linux 4) and a openldap server. I tried every combination of tls_mode, start_tls and tls_require_cert, but I never got more than this error: (/etc/raddb/radiusd.conf) ---8<-