Recent changes to bugs

Can't install gem on Windows

Aaron Mueller — Thu, 19 Jan 2012 15:05:51 -0000

I tried to install ruby-ldap (version 0.9.12) and get this error message:

make install
/usr/bin/install -c -m 0755 ldap.so /usr/lib/ruby/gems/1.8/gems/ruby-ldap-0.9.12/lib
/usr/bin/install -c -m 644 ./lib/ldap/control.rb /usr/lib/ruby/gems/1.8/gems/ruby-ldap-0.9.12/lib/ldap
/usr/bin/install: `./lib/ldap/control.rb' and `/usr/lib/ruby/gems/1.8/gems/ruby-ldap-0.9.12/lib/ldap/control.rb' are the same file
Makefile:130: recipe for target `/usr/lib/ruby/gems/1.8/gems/ruby-ldap-0.9.12/lib/ldap/control.rb' failed
make: *** [/usr/lib/ruby/gems/1.8/gems/ruby-ldap-0.9.12/lib/ldap/control.rb] Error 1

Gem files will remain installed in /usr/lib/ruby/gems/1.8/gems/ruby-ldap-0.9.12 for inspection.
Results logged to /usr/lib/ruby/gems/1.8/gems/ruby-ldap-0.9.12/./gem_make.out

I use Windows an CygWin :(
Are there some paths wrong? Other gems can install smoothly.

LDAP::LDIF.mods_to_ldif fails in ruby1.9

Anonymous — Tue, 05 Oct 2010 09:14:58 -0000

The following unit test fails with ruby1.9 while works with ruby1.8.7:

#!/usr/bin/env ruby
#encoding: UTF-8

require 'rubygems'
gem 'test-unit'
require 'test/unit'
require 'ldap'
require 'ldap/ldif'

p RUBY_VERSION

def test_ldap_mod_to_ldif
mod = LDAP::Mod.new(LDAP::LDAP_MOD_REPLACE, "uid", ["tizio", "caio"])
assert mod
assert LDAP::LDIF.mods_to_ldif("uid=tizio,ou=people,dc=test,dc=com", mod)
end
end

as far as I can see, it looks it relies on String.respond_to? :each which works on ruby1.8.7 and not in ruby1.9

New patch for LDAP::Mod data corruption

Aprotim Sanyal — Tue, 23 Sep 2008 21:35:39 -0000

This is a patch to fix the same bug as 1846626, but uses the existing macros to help avoid error.

This is a significant and pressing problem for any long-running Ruby process which needs to modify LDAP entries.

Passwords won't authenticate with special characters like ñ

Anonymous — Thu, 19 Jun 2008 19:21:14 -0000

I have a situation in which I use LDAP to authenticate my users via active directory. Unfortunately, I believe I've found a bug. When a use submits his username and password he is unable to authenticate successfully because his password has a ñ character in it. I use this code in mexico, US and America, so I'm concerned that I'll have several others running into this problem. Any suggestions for a fix?

Modify mod_type dangling pointer corruption

Anonymous — Sat, 08 Dec 2007 02:48:44 -0000

For valid attribute types, we were experiencing this error message:
/usr/lib/ruby/1.8/activeldap/base.rb:776:in `write': Could not update LDAP entry: Undefined attribute type (ActiveLDAP::WriteError)

It looks like mod.c:rb_ldap_new_mod() sets mod->mod_type (the attribute name) to the address of a string that is passed in. The caller does not guarantee that this string will be retained, and it is freed. Depending on the behaviour of subsequent mallocs, mod_type can be overwritten.

We have had success with the attached patch against Ruby Ldap 0.9.7. It creates a copy of the string in rb_ldap_new_mod() and frees it in ldap_modify_s rb_ldap_mod_free().

schema.rb invalid regular expression line 38

bidon — Tue, 11 Sep 2007 08:19:08 -0000

In ruby-ldap 0.9.7, the file schema.rb contain a regular expression that give the following error when reached.

Exception `RegexpError' at /opt/local/lib/ruby/site_ruby/1.8/ldap/schema.rb:38 - invalid regular expression; can't use character class as an end value of range: /MUST\s+$([\w\d_-\s\$]+)$/

The error comes from the dash that was added in 0.9.7 in the middle of of the character class in the regex. In the middle that dash mean a character range instead of the dash character. To correct the problem, the dash should be put at the end of the character class regex. So
[\w\d_-\s\$]
should become
[\w\d_\s\$-]

I'll try to submit a patch.

More info
ruby-ldap 0.9.7
ruby 1.8.6
Mac OS X 10.4.10

Crashes with BUS ERROR on OS X / intel, when used with rails

Anonymous — Fri, 08 Dec 2006 17:50:55 -0000

$ script/console
Loading development environment.
>> require 'ldap'
=> true
>> LDAP::Conn.open
(irb):4: [BUG] Bus Error
ruby 1.8.4 (2005-12-24) [i686-darwin8.8.1]

However from plain irb, it runs fine. I presume it's clashing with some other code Rails pulls in. Bit of a show-stopper as far as I'm concerned.

LDAP::SCHEMA limitation

Romain GEORGES — Wed, 06 Sep 2006 08:26:51 -0000

LDAP::Schema.names(key) cannot get the attributes alias
informations in the attributeTypes key , because of a
too restrictive regexp
(don't see some stupids parenthesis ;) )

i'have commit an exemple of the method
LDAP::Schema.alias(at) who could give the list in an Array

But i think the regexp of names(key) have to be modified

Friendly, Romain

InvalidEntryError exceptions are being obfuscated

Bogdano Arendartchuk — Tue, 05 Sep 2006 17:30:49 -0000

InvalidEntryError exceptions are being obfuscated by
another exception:

`inspect': stack level too deep (SystemStackError)

This is happening because rb_inspect is being called to
an invalidated Entry object even when is going to
complain about it is invalidated.

if( ! ptr->msg ){
rb_raise(rb_eLDAP_InvalidEntryError, "%s is not a
valid entry", \ STR2CSTR(rb_inspect(obj))); \
}; \

Docs should refer about LDAP::Entry lifecycle

Bogdano Arendartchuk — Tue, 05 Sep 2006 17:00:32 -0000

The documentation (the rdoc is the only I've found) is
not clear about the need to use the entry object only
inside the block given to conn.search.

It would be nice if this behavior was mentioned in the
documentation of conn.search*.