Re: (ITS#9023) crash using ppolicy chaining from slave to master

[ondra@mistotebe.net]

On Mon, May 20, 2019 at 10:29:02AM +0000, AYANIDES, JEAN-PHILIPPE wrote:
> Yes, it serves traffic. It doesn't crash until I run a bind with a
> wrong password.
> 
>> (gdb) cont
>> Continuing.
> 
> [LDAP search with wrong password]
> 
>> [New Thread -1237541968 (LWP 29380)]
> 
>> Program exited with code 0177.
>> (gdb) thread apply all bt full
> 
> Yes sorry, It runs on an old version of debian: 4:0 32 bits that I am
> not authorised to upgrade.
> 
> It the first time we record that sort of issue on that platformâ?¦

Hi Jean-Philippe,
are you able to reproduce this on a different system, if not, can you
get a more recent gdb on that system?

I have tried to reproduce with a config similar to the one you describe
didn't manage to provoke a segfault with re24 nor master.

On a side note, I don't think running the chain overlay with mode=self
will work to propagate the ppolicy information the way you want. The
same failing credentials will be used to contact the upstream server and
so the initial bind will be rejected again, not allowing the
modification to be performed.

Regards,

-- 
OndÅ?ej Kuzník
Senior Software Engineer
Symas Corporation                       http://www.symas.com
Packaged, certified, and supported LDAP solutions powered by OpenLDAP