Package: ecryptfs-utils Version: 67-1 Severity: minor I was wondering why mouning operation causing message such as no "rw" option etc...
Since there is no upstream changelog included (not even URL pointer) it is quite difficult to find what does it mean by | ecryptfs-utils (67-1) unstable; urgency=low | | * Merging upstream version 67. | | -- Daniel Baumann <[EMAIL PROTECTED]> Wed, 3 Dec 2008 09:54:00 +0100 This package seem to use tar ball from Ubuntu. It has no changelog in it not mention of git repository URL. Thus I have easy way to find what is the change here. Upstream records its changes in thier git log. http://git.kernel.org/?p=linux/kernel/git/mhalcrow/ecryptfs-utils.git;a=commit;h=c7cb7795689857d2ef6ef678e57cf1abf6ac7e72 | Release version 67 | | This version adds support for a new bootstrapping mechanism to create | encrypted home directories. This certainly sounds major change. Its history tells me: http://git.kernel.org/?p=linux/kernel/git/mhalcrow/ecryptfs-utils.git;a=commit;h=d6a8ce44288233955cbf920e022a5eb9e3f3b0da | encrypted home dir bootstrapping | | This non-trivial patch adds some bootstrapping code necessary for adding | a new user to a system, and setting up their home directory for | encryption. | | The ecryptfs code expects the following call to take place, after the | user and their home directory have been created, but before the | /etc/skel has been copied to the homedir and the password established: | # ecryptfs-setup-private -b -u $USER | | To accomplish this, the following changes are necessary: | - src/include/ecryptfs.h: add the ecryptfs_wrap_passphrase_file() | function | - src/libecryptfs/key_management.c: implement the function | ecryptfs_wrap_passphrase_file(); this function will take a cleartext | mount passphrase file and wrap it appropriately | - src/pam_ecryptfs/pam_ecryptfs.c: call ecryptfs_wrap_passphrase_file() | when an unwrapped passphrase file owned by the user exists, and the | wrapped-passphrase file does not exist, if the user is changing | their password (ie, the first passwd call that establishes the users | password) | - src/utils/ecryptfs-setup-private: add support for bootstrapping an | encrypted home directory, when called from adduser; | * abstract ciper and keybytes to variables | * add a -b|--bootstrap option | * if bootstrapping, make sure we're running as root | * redirect error messages to stderr | * create a random_passphrase() callable function, since we will be | calling this from multiple places now | * if we're bootstrapping, we need .ecryptfs to live in | /var/lib/ecryptfs, and linked back to ~/.ecryptfs | * remove the --all-home functionality; it's superceded by this | bootstrapping mechanims | * when counting files in existing directories, ignore sym links | * if bootstrapping, write mount passphrase to shm temp file | * use safer mktemp/mv mechanism for writing config files | * if bootstrapping, chown created files back to the user, since | we're running as root If it is too much to download git changelog with git-log, please include git location URL somewhere. Git URL git://git.kernel.org/pub/scm/linux/kernel/git/mhalcrow/ecryptfs-utils.git http://www.kernel.org/pub/scm/linux/kernel/git/mhalcrow/ecryptfs-utils.git Or browsable one: http://git.kernel.org/?p=linux/kernel/git/mhalcrow/ecryptfs-utils.git;a=summary Current copyright has only reference to Download: https://launchpad.net/ecryptfs/trunk Current control has: Homepage: https://launchpad.net/ecryptfs When you fixed my bug report, you did not put homepage as I rote but chose launchpad.net where you get tar ball. This made it quite tediout to find upstream changes. I think you should include VCS header at least. If possible, please add URLs to the copyright too. Osamu -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (800, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ecryptfs-utils depends on: ii libc6 2.7-16 GNU C Library: Shared libraries ii libecryptfs0 67-1 ecryptfs cryptographic filesystem ii libgcrypt11 1.4.1-2 LGPL Crypto library - runtime libr ii libgpg-error0 1.4-2 library for common error values an ii libgpgme11 1.1.6-2 GPGME - GnuPG Made Easy ii libkeyutils1 1.2-9 Linux Key Management Utilities (li ii libpam0g 1.0.1-4+b1 Pluggable Authentication Modules l Versions of packages ecryptfs-utils recommends: ii keyutils 1.2-9 Linux Key Management Utilities Versions of packages ecryptfs-utils suggests: ii opencryptoki 2.2.6+dfsg2-1 PKCS#11 implementation for Linux ( -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
