Age | Commit message (Collapse) | Author |
|
|
|
|
|
Currently, it is difficult to diagnose LDAP authentication failures,
since the logs do not provide sufficient information about what is
actually being queried and what actually failed.
This increases logging details so that information about the LDAP query
is included, for example:
Fri Mar 06 2020 08:02:59 ANNOUNCEMENT: Error binding as manager to LDAP
server: Invalid credentials (bind dn=cn=adminz,dc=nodomain)
Rather than:
Fri Mar 06 2020 08:02:59 ANNOUNCEMENT: Error binding as manager to LDAP
server: Invalid credentials
Same with connection logging:
Fri Mar 06 2020 07:59:53 CONNECT: Forbidden connection from
jsing!jsing@192.168.200.1 (Invalid credentials (bind
dn=uid=jsing,dc=nodomain))
Fri Mar 06 2020 08:01:19 CONNECT: Successful connection from
jsing!jsing@192.168.200.1 (dn=uid=jsing,dc=nodomain)
|
|
|
|
This is a lot safer and handles users changing servers properly.
|
|
|
|
|
|
Thanks to @StevenVanAcker for reporting and testing this
|
|
|
|
substr() returns a new string while erase() and assign() modify the existing one
|
|
|
|
|
|
|
|
|
|
|
|
git-svn-id: http://svn.inspircd.org/repository/trunk/inspircd@9078 e03df62e-2008-0410-955e-edbf42e46eb7
|
|
Carsten Valdemar Munk based on m_sqlauth.
git-svn-id: http://svn.inspircd.org/repository/trunk/inspircd@9077 e03df62e-2008-0410-955e-edbf42e46eb7
|