ecryptfs-utils does not link against openssl

[dinexi]

Binary package hint: ecryptfs-utils

Man reads:
              Parameters that apply to individual key modules have the alias
              for the key module in the prefix of the parameter name. Key
              modules are pluggable, and which key modules are available on
              any given system is dependent upon whatever happens to be
              installed in /usr/lib*/ecryptfs/. By default, this includes, at
              a minimum, "passphrase" and "openssl."

Great. I have done `sudo aptitude install ecryptfs-utils libecryptfs-dev libecryptfs0` and ran `ls /usr/lib*/ecryptfs/` and what I see?

[stanis@dinexi ~] % ls /usr/lib*/ecryptfs/ [5:20:39]
/usr/lib64/ecryptfs/:
libecryptfs_key_mod_passphrase.so

/usr/lib/ecryptfs/:
libecryptfs_key_mod_passphrase.so

I see the passphrase here. I don't see openssl, which, as the man states, should be available "at a minimum". Why?

[Dustin Kirkland  (kirkland)]

Right, we're not allowed to link GPL code against OpenSSL.

Details are here:
 * http://people.gnome.org/~markmc/openssl-and-the-gpl.html

That said, I can *try* to track down the ecryptfs-utils copyright holders, and get explicit permission from each of them to add the OpenSSL clause to our license.

No promises, but I'll keep this bug open until I get an answer. Thanks!