[Bug 218556] Review Request: ecryptfs-utils - Linux eCryptfs utilities

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: ecryptfs-utils - Linux eCryptfs utilities


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=218556





------- Additional Comments From mhalcrow at us.ibm.com  2007-06-20 18:39 EST -------
eCryptfs is pretty well hooked in with the kernel keyring. There could be some
modifications done in the kernel module to allow key registration via a mount
option or a sysfs handle, if that is something that users will really want, but
to date, nobody has requested such a thing. eCryptfs links against libgcrypt
mainly because it is less complicated in terms of licensing (it's all GPL). The
next-best option I would choose would be to just copy in what libecryptfs needs
from libtomcrypt.

Release 17 keeps all the linking as-is, but it also has a built-in fallback for
the passphrase key module in the event that the usr/lib/ecryptfs/ directory is
not set up as expected.

I added several new userspace utilities for managing wrapped passphrases. This
involves keeping a permanent mount passphrase wrapped by your login. This is
helpful, for instance, if you are using pam_ecryptfs.so and want to be able to
change your login passphrase without having to re-encrypt all of your data.

I added the commands to run check-rpath in my ~/.rpmmacros file, as suggested in
the packaging guidelines, and I did not see any errors generated by check-rpath.

Release 17 is here:

http://downloads.sourceforge.net/ecryptfs/ecryptfs-utils-17.tar.bz2

Along with an updated SPEC file (although I'm not sure what Kevin has done with
the SPEC file since I last changed it):

http://downloads.sourceforge.net/ecryptfs/ecryptfs-utils.spec

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.