22 Nov, 2013

2 commits


21 Nov, 2013

1 commit


20 Nov, 2013

5 commits


19 Nov, 2013

4 commits


18 Nov, 2013

1 commit


15 Nov, 2013

1 commit


14 Nov, 2013

1 commit


13 Nov, 2013

1 commit


12 Nov, 2013

1 commit


11 Nov, 2013

2 commits


10 Nov, 2013

1 commit


09 Nov, 2013

1 commit


08 Nov, 2013

2 commits


07 Nov, 2013

1 commit


06 Nov, 2013

4 commits


05 Nov, 2013

4 commits


04 Nov, 2013

1 commit

  • - Database name may contain characters which are not shell friendly
    - Database password could contain the same
    - While we at it there is no harm in escaping generated paths too
    - Refactored 2-line system(command)
    
    Signed-off-by: Nigel Kukard <nkukard@lbsd.net>
    Nigel Kukard
     

03 Nov, 2013

1 commit

  • The blocked? method is used to check whether a user exists in LDAP. Prior to this change, if the LDAP server had more objects below the one pointed to by the DN, those objects would also be picked up by the search, causing the method to determine the user should be blocked.
    
    One case where this can happen is when using Active Directory and a user have a mobile phone assigned. In this case, Exchange will add an entry called ExchangeActiveSyncDevices under the users entry. The user-visible behaviour is then that a user loses Gitlab access when he enables a mobile device.
    
    This fix sets the search scope to BaseObject in order to ensure that only the user itself is returned.
    Elias Mårtenson
     

01 Nov, 2013

4 commits


31 Oct, 2013

2 commits