Permalink
Switch branches/tags
Nothing to show
Commits on Dec 10, 2016
  1. release 0.22

    karpet committed Dec 10, 2016
Commits on Jul 19, 2016
  1. release 0.21

    karpet committed Jul 19, 2016
  2. Merge pull request #5 from sartak/prefer-ipv6

    karpet committed Jul 19, 2016
    Prefer the IPv6 stack when possible, a la Net::LDAP
Commits on Jul 18, 2016
Commits on Jul 1, 2016
  1. prep 0.20 release

    karpet committed Jul 1, 2016
  2. tidychanges

    karpet committed Jul 1, 2016
Commits on May 1, 2013
  1. release 0.19

    karpet committed May 1, 2013
  2. clean up tests

    karpet committed May 1, 2013
Commits on Apr 25, 2013
  1. Merge pull request #3 from chorny/master

    karpet committed Apr 25, 2013
    prevent hanging on WIndows
Commits on Mar 14, 2013
  1. release 0.18

    Peter Karman
    Peter Karman committed Mar 14, 2013
Commits on Mar 13, 2013
  1. kill signal 9 (really mean it) with warning output

    Peter Karman
    Peter Karman committed Mar 13, 2013
Commits on Feb 3, 2013
Commits on Oct 25, 2012
  1. add new tests to MANIFEST

    Peter Karman
    Peter Karman committed Oct 25, 2012
  2. release 0.16

    Peter Karman
    Peter Karman committed Oct 25, 2012
  3. Merge pull request #2 from rporres/master

    karpet committed Oct 25, 2012
    ModifyDN fixes
  4. Removed part of the comments on ModifyDN. Net::LDAP encodes the messa…

    rporres committed Oct 25, 2012
    …ge with newSuperior set to undef if we don't specify it in the options of moddn. Once encoded it doesn't get to the server in the message, so it's not a hack to find the base DN to which the newrdn is relative to since we cannot assume newSuperior is going to be in the moddn. This is the expected behaviour described in RFC 2251
  5. ModifyDN was not working correctly as newSuperior attribute doesn't a…

    rporres committed Oct 25, 2012
    …lways come from decoded moddn request.
  6. bump version, note changes

    karpet committed Oct 25, 2012
  7. based on https://rt.cpan.org/Ticket/Display.html?id=80377, return err…

    karpet committed Oct 25, 2012
    …or codes using internal constants
Commits on Sep 21, 2012
Commits on Jul 28, 2012
  1. release 0.14

    karpet committed Jul 28, 2012
  2. ptidy only

    karpet committed Jul 28, 2012
  3. Merge pull request #1 from tsibley/search-scope

    karpet committed Jul 28, 2012
    Search scope bug fixes
Commits on Jul 27, 2012
  1. A scope of 'one' shouldn't include the base entry

    tsibley committed Jul 27, 2012
    From RFC 4511 section 4.5.1.2:
    
        singleLevel: The scope is constrained to the immediate
        subordinates of the entry named by baseObject.
  2. Filters should still apply with a scope of 'base'

    tsibley committed Jul 27, 2012
    From RFC 4511:
    
        4.5.1.2.  SearchRequest.scope
    
           Specifies the scope of the Search to be performed.  The semantics (as
           described in [X.511]) of the defined values of this field are:
    
              baseObject: The scope is constrained to the entry named by
              baseObject.
    
    and
    
        4.5.1.7.  SearchRequest.filter
    
           A filter that defines the conditions that must be fulfilled in order
           for the Search to match a given entry.
    
    Nowhere does the RFC specify that the baseObject is excluded from the
    filters, and doing so would render the 'base' scope not nearly as
    useful.
  3. Restore the default scope of 'sub'

    tsibley committed Jul 27, 2012
    b703620 accidentally changed the default scope from 'sub' (2) to 'base' (0).
  4. More robust depth checking for scopes of 'one' in auto_schema search

    tsibley committed Jul 27, 2012
    DNs may contain spaces which the depth checking regex didn't expect.
    Use a Net::LDAP utility method to count the depth level properly and
    compare against the base's depth.
    
    t/05-scope.t now passes the previously TODOed tests.
  5. Translate scopes of 0, 1, and 2 into base, one, and sub, as expected

    tsibley committed Jul 27, 2012
    Scope is enumerated as 0, 1, or 2 in the request data, but the
    auto_schema search method expected words.
    
    Additionally, when writing tests I discovered that a scope of 'one'
    doesn't work when the DN has spaces in it due to an incomplete regex
    pattern.  Fix to follow.