Your message dated Tue, 23 Dec 2008 07:32:03 +0000
with message-id <[email protected]>
and subject line Bug#507942: fixed in ecryptfs-utils 68-1
has caused the Debian Bug report #507942,
regarding ecryptfs-utils: Missing upstream change information
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
507942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507942
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: ecryptfs-utils
Source-Version: 68-1
We believe that the bug you reported is fixed in the latest version of
ecryptfs-utils, which is due to be installed in the Debian FTP archive:
ecryptfs-utils_68-1.diff.gz
to pool/main/e/ecryptfs-utils/ecryptfs-utils_68-1.diff.gz
ecryptfs-utils_68-1.dsc
to pool/main/e/ecryptfs-utils/ecryptfs-utils_68-1.dsc
ecryptfs-utils_68-1_i386.deb
to pool/main/e/ecryptfs-utils/ecryptfs-utils_68-1_i386.deb
ecryptfs-utils_68.orig.tar.gz
to pool/main/e/ecryptfs-utils/ecryptfs-utils_68.orig.tar.gz
libecryptfs-dev_68-1_i386.deb
to pool/main/e/ecryptfs-utils/libecryptfs-dev_68-1_i386.deb
libecryptfs0_68-1_i386.deb
to pool/main/e/ecryptfs-utils/libecryptfs0_68-1_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Baumann <[email protected]> (supplier of updated ecryptfs-utils package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Tue, 23 Dec 2008 08:04:00 +0100
Source: ecryptfs-utils
Binary: ecryptfs-utils libecryptfs0 libecryptfs-dev
Architecture: source i386
Version: 68-1
Distribution: unstable
Urgency: high
Maintainer: Daniel Baumann <[email protected]>
Changed-By: Daniel Baumann <[email protected]>
Description:
ecryptfs-utils - ecryptfs cryptographic filesystem (utilities)
libecryptfs-dev - ecryptfs cryptographic filesystem (development)
libecryptfs0 - ecryptfs cryptographic filesystem (library)
Closes: 507942 509339
Changes:
ecryptfs-utils (68-1) unstable; urgency=high
.
* Merging upstream version 68:
- Contains upstream changelog (Closes: #507942).
- Fixes syntax error in ecryptfs-setup-private (Closes: #509339).
* Updating rules to install changelog.
Checksums-Sha1:
58c6c7d962f7bd4fd65bb6f6253640fbe3899f50 1526 ecryptfs-utils_68-1.dsc
3614416ea4e989793c1f13dfb4d150d714f81b17 484723 ecryptfs-utils_68.orig.tar.gz
4c313da479adb09a5cab9af7451b802a1fe32bf0 5392 ecryptfs-utils_68-1.diff.gz
72b65701443b26f09024669b6f807706bbeb4059 81928 ecryptfs-utils_68-1_i386.deb
5d13afd21e3f0693ea7190339d1ed106d947077b 59438 libecryptfs0_68-1_i386.deb
952664e35c19da174025fed679e37ecafbf5aabd 49698 libecryptfs-dev_68-1_i386.deb
Checksums-Sha256:
8576853a7b748a2cf57ecc909a29a3b703773a01845598f43ada31107cf3e659 1526
ecryptfs-utils_68-1.dsc
c26b109cd54b82033699727a455069bd9130c3be2e67573f5ebcdfb8f0d9b67e 484723
ecryptfs-utils_68.orig.tar.gz
043b1cec607e337876e6f47fc131e4883ab526fc0a17159eb9d953c568549218 5392
ecryptfs-utils_68-1.diff.gz
99b06fecef14549bcbd2a29da744743a17e3b1661f16e560146af6d9626320ec 81928
ecryptfs-utils_68-1_i386.deb
bc046bd7ccb309753c374851eecb5a37d6178c13806aef62ec28afe9871a3430 59438
libecryptfs0_68-1_i386.deb
177debf06cc540a3beedbf2380cffec97cabad6e19ea363e949faeaa862b45fe 49698
libecryptfs-dev_68-1_i386.deb
Files:
18a053130fc52bbbccbba12a744b0b5a 1526 misc optional ecryptfs-utils_68-1.dsc
57428a8bf128bc1f076412c7b6478ca0 484723 misc optional
ecryptfs-utils_68.orig.tar.gz
87fd06349d155c9c51928e288886b0d7 5392 misc optional ecryptfs-utils_68-1.diff.gz
766faa8391f557d2d4b804fbeb025bf9 81928 misc optional
ecryptfs-utils_68-1_i386.deb
f9e3b87be97c2f6434309474e9e25704 59438 libs optional libecryptfs0_68-1_i386.deb
294ba3d91eff53a0db74798795748384 49698 libdevel optional
libecryptfs-dev_68-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAklQkPIACgkQ+C5cwEsrK55v6wCfVyrlP8FF5ztF18NEjnVDtF3k
f8YAoMstHnXcu9dCC9LHUMrPeDqh//W7
=2fV4
-----END PGP SIGNATURE-----
--- End Message ---
