** Changed in: libldap-ruby (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/381791
Title:
LDAP::SSLConn from ruby fails, probably from not seeing cert
To man
I get the same error on my Ubuntu Hardy setup on a slicehost, however I
know the gem works because when I run the exact same rails app on my
local development server, it works perfectly.
I realize it's been over a year since the last comment, but PLEASE let
me know if you found/find a way to get t
I got some comments that this might have to do with Debian/Ubuntu
linking with gnutls instead of openssl by default. I am trying to put
together an openssl build right now, but that is being difficult too.
Apparently openssl might be less difficult with certain certificates.
--
LDAP::SSLConn fr
I may misunderstand what is going on with this, but it appears there is
no definition of bind specific to my SSL usage inside the sslconn.c
source file given the preprocessor define symbol / state I am
experiencing of USE_OPENLDAP_SSLCONN, the implication seeming to be that
this version of the sour
Given further traces I installed, it appears I get an exception in the
following location right after trace 7a:
fprintf(stderr,"trace 7 rb_ldap_conn_bind_s\n");
ldapdata->err = ldap_bind_s (ldapdata->ldap, dn, passwd, method);
fprintf(stderr,"trace 7a rb_ldap_conn_bind_s\n");
Check_LDAP_Result
I just put some trace statements in all the functions with the word
'bind' in them in sslconn.c, and compiling and running that, along with
some in the initializer, I show said initializer is called, but none of
the 'bind' functions in that file are called. So my guess is the bind
method I am usin
> someone with a little energy could in fact get in and hack this
together anyway
Please feel free to do so:
apt-get source libldap-ruby1.8
You might try building ruby-ldap from source separately to see if you
can get it to behave the way you want, and then see what changes are
needed to the
Okay, this is probably important to add:
On the Ubuntu server machines I'm using, when I do a plain openssl call
like so:
openssl s_client -connect ipaddr:port
where ipaddr and port are definitely correct and shown to work in all
other ways with the ldap server we are trying to configure, we get
Can somebody tell me here if this is perhaps intentionally made not to
work? I have seen other posts that seem to indicate LDAP::SSLConn has
never worked, and perhaps is intended not to work because of the
implications for password guessing attacks. Excuse me if I impose my
pressure and political
In case this wasn't clear, the 636 port and ldap server hostname are
both used in other combinations elsewhere, so we know these are correct
for our testing.
--
LDAP::SSLConn from ruby fails, probably from not seeing cert
https://bugs.launchpad.net/bugs/381791
You received this bug notification
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
Have you tried 'apt-get install libopenssl-ruby' ?
Ubuntu separates out all of the openssl-dependent parts of Ruby into a
separate package (including things like net/https as well as openssl)
--
LDAP::SSLConn from ruby fails, probably from not seeing cert
https://bugs.launchpad.net/bugs/381791
12 matches
Mail list logo
