[Bug 6629] userPassword Support not available, because it is not build with libssl-dev

[Benjamin Montgomery]

Public bug report changed:
https://launchpad.net/malone/bugs/6629

Comment:
Guido Trotter wrote:
>>I'm working on a bug that was reported in the Ubuntu bug tracker[1]
>>regarding encryption of userPassword entries.  I have also been using a
>>local package of gq that is built with libsasl2.  I have been using my
>>package of gq to do GSSAPI binds with my ldap server.  It also appears
>>that the userPassword encryption works correctly.  I looked through the
>>BTS and noticed that you have disabled these features on purpose, but
>>I'm not clear on the reason why.  Are there problems with these features?
> 
> Yeah, upstream (when he was still active) esplicitely said they were completely
> broken and unsupported... So I preferred to disable them!

Just to make sure, you are refering to both the OpenSSL and SASL
features?  Did upstream give examples of what was broken?

Have you done any testing with the userPassword encryption turned on?
Do you know if it produces the correct output?  I can verify that SASL
GSSAPI binds work correctly on my network.

>>A related issue is that of linking against OpenSSL.  It seems the
>>authors of gq have allowed an exception to the GPL to get around the
>>OpenSSL license issues described here [2].  I think if the features that
>>OpenSSL enables work correctly, the OpenSSL attribution statement needs
>>to be added to the copyright file.
> 
> That can surely be done! No problem!

This isn't an issue if the OpenSSL code in gq is broken and not enabled.


Attachment: signature.asc
Type:       application/pgp-signature; name="signature.asc"
URL:        http://librarian.launchpad.net/1520342/signature.asc