https://bugs.openldap.org/show_bug.cgi?id=9540
--- Comment #4 from Michael Ströder <[email protected]> --- On 5/3/21 5:00 PM, [email protected] wrote: > However, I feel it does not answer the question how OpenLDAP can > provide reasonable compatibility? Can you clearly define what "reasonable compatibility" really means in this case? > Forgive me, but IMHO, it's not a good answer to real-world problems to insist > on "it's not our problem". Thanks for re-considering. Could you please elaborate on which LDAP client is affected? And are you and the developers of this LDAP client aware that originally this attribute was meant to carry a signed S/MIME message with empty body to also carry the S/MIME capabilities of a client? The only client I know of which supported this was Netscape Communicator 4.x back in '98 last century. This was a user self-service action (because it involved signing with the user's private key which was protected with passphrase). After that I never saw a client making correct use of this attribute. Ciao, Michael. -- You are receiving this mail because: You are on the CC list for the issue.
