masarati@aero.polimi.it wrote:

...

masarati@aero.polimi.it wrote:

...

I'd appreciate it very much if it would be exactly behave in the same way like all other string-valued options.

On a somewhat related issue, I note that LDAP_OPT_X_SASL_MECHLIST returns a pointer to an array of chars that apparently cannot be mucked with.

Assuming my understanding is correct, I wonder if this behavior is desirable or not, given the fact that if another mech is added, e.g. by adding a dynamic module, I expect this list to change.

These are SASL mechs with the plugin modules. Right?

From an operational standpoint: If a SASL plugin module for a mech was added I

think it's acceptable that a software which queries this option is restarted before this SASL mech is known to the software. Probably one has to add additional configuration for this SASL mech.

Now the question is what happens if a SASL plugin module is removed and the software trys to use the removed SASL mech. Clearly removing plugin modules in a running system is asking for trouble anyway...

Having said this I would not care too much about this list going to change...

Ciao, Michael.