Your message dated Sat, 08 Nov 2008 06:17:04 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#504934: fixed in ecryptfs-utils 64-3
has caused the Debian Bug report #504934,
regarding ecryptfs-utils: Update ecryptfs-pam-doc.txt contents with
"s/Confidential/Private/"
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.)
--
504934: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504934
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: ecryptfs-utils
Version: 64-2
Severity: minor
Tags: patch
It looks like there were ecryptfs-setup-confidential (I see it on the
https://wiki.ubuntu.com/EncryptedPrivateDirectory under "Getting
Involved"). But current upstream and Debian ships with
ecryptfs-setup-private and uses ~/Private/ as the default mount point.
I think ecryptfs-utils/doc/ecryptfs-pam-doc.txt in the source needs to
be updated accordingly to reduce confusion. I attach patch here.
Please forward this to upstream.
By the way, I do not see auth-client-config package in Debian.
-- System Information:
Debian Release: lenny/sid
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 64-2 ecryptfs cryptographic filesystem
ii libgcrypt11 1.4.1-1 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
ii libpkcs11-helper1 1.05-1 library that simplifies the intera
ii libssl0.9.8 0.9.8g-14 SSL shared libraries
ii libtspi1 0.3.1-7 open-source TCG Software Stack (li
ecryptfs-utils recommends no packages.
Versions of packages ecryptfs-utils suggests:
pn auth-client-config <none> (no description available)
ii opencryptoki 2.2.6+dfsg-5 PKCS#11 implementation for Linux (
-- no debconf information
--- ecryptfs-pam-doc.txt.orig 2008-11-08 13:15:07.000000000 +0900
+++ ecryptfs-pam-doc.txt 2008-11-08 13:15:51.000000000 +0900
@@ -7,11 +7,11 @@
eCryptfs is set up in the Open Client to automatically mount on user
login. The default mount is an overlay mount on top of
-~/Confidential/, and it uses a passphrase-based key.
+~/Private/, and it uses a passphrase-based key.
eCryptfs requires that the user's mount passphrase be inserted into
the user session keyring in order to access the files under the
-~/Confidential/ mount point. The mount passphrase is wrapped
+~/Private/ mount point. The mount passphrase is wrapped
(encrypted) with the user's login passphrase and is stored in the
~/.ecryptfs/wrapped-passphrase file. When the user logs in, the
eCryptfs PAM module intercepts the user's login passphrase, uses it to
@@ -21,7 +21,7 @@
Once the user has logged in, his ~/.bash_profile script is executed by
the Bash shell. A segment of code in ~/.bash_profile checks for the
existence of a ~/.ecryptfs/auto-mount file. If this file exists, then
-code is executed to mount ~/Confidential/ via eCryptfs.
+code is executed to mount ~/Private/ via eCryptfs.
When the user changes his login credentials, the eCryptfs PAM module
unwraps the mount passphrase in ~/.ecryptfs/wrapped-passphrase with
@@ -38,7 +38,7 @@
In order for these operations to complete successfully, the eCryptfs
PAM module needs to be inserted into the PAM stack in
/etc/pam.d/system-auth, an entry needs to be in /etc/fstab for the
-user's ~/Confidential/ directory, the ~/.ecryptfs/auto-mount and
+user's ~/Private/ directory, the ~/.ecryptfs/auto-mount and
~/.ecryptfs/wrapped-passphrase files need to exist, and the mount code
needs to be in the user's ~/.bash_profile script.
@@ -75,7 +75,7 @@
The following line needs to be added to /etc/fstab:
-/home/user/Confidential /home/user/Confidential ecryptfs rw,ecryptfs_sig=deadbeefbaadf00d,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,user,noauto, 0 0
+/home/user/Private /home/user/Private ecryptfs rw,ecryptfs_sig=deadbeefbaadf00d,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,user,noauto, 0 0
Where 'user' is the username and 'deadbeefbaadf00d' is the mount
passphrase signature/identifier value. This signature is in /etc/mtab
@@ -85,9 +85,9 @@
~/.bash_profile:
if test -e $HOME/.ecryptfs/auto-mount; then
- mount | grep "$HOME/Confidential type ecryptfs"
+ mount | grep "$HOME/Private type ecryptfs"
if test $? != 0; then
- mount -i $HOME/Confidential
+ mount -i $HOME/Private
fi
fi
ecryptfs-zombie-kill
@@ -112,18 +112,18 @@
Troubleshooting
- Problem: The ~/Confidential/ directory is not being mounted on login.
- Problem: The ~/Confidential/ directory is mounted on login, but
- the files under the ~/Confidential/ directory cannot be read.
+ Problem: The ~/Private/ directory is not being mounted on login.
+ Problem: The ~/Private/ directory is mounted on login, but
+ the files under the ~/Private/ directory cannot be read.
Solution: Your ~/.ecryptfs/wrapped-passphrase file may be
incorrect. Run ecryptfs-wrap-passphrase to recreate it if
that is the case. Otherwise, the PAM stack is not set up
correctly. Otherwise, the code to mount your
- ~/Confidential directory is not in your ~/.bash_profile
+ ~/Private directory is not in your ~/.bash_profile
file.
- Problem: The ~/Confidential/ directory mounts on console login
+ Problem: The ~/Private/ directory mounts on console login
but not on GDM login.
Solution: Make sure you have the most recent
@@ -139,7 +139,7 @@
Problem: How to I backup my encrypted files?
- Solution: Unmount your ~/Confidential directory so that
+ Solution: Unmount your ~/Private directory so that
the lower filesystem files (in encrypted state) show up at
that path location, and then copy the files in that
directory to another storage device.
--- End Message ---
--- Begin Message ---
Source: ecryptfs-utils
Source-Version: 64-3
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_64-3.diff.gz
to pool/main/e/ecryptfs-utils/ecryptfs-utils_64-3.diff.gz
ecryptfs-utils_64-3.dsc
to pool/main/e/ecryptfs-utils/ecryptfs-utils_64-3.dsc
ecryptfs-utils_64-3_i386.deb
to pool/main/e/ecryptfs-utils/ecryptfs-utils_64-3_i386.deb
libecryptfs-dev_64-3_i386.deb
to pool/main/e/ecryptfs-utils/libecryptfs-dev_64-3_i386.deb
libecryptfs0_64-3_i386.deb
to pool/main/e/ecryptfs-utils/libecryptfs0_64-3_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: Sat, 8 Nov 2008 07:01:00 +0100
Source: ecryptfs-utils
Binary: ecryptfs-utils libecryptfs0 libecryptfs-dev
Architecture: source i386
Version: 64-3
Distribution: unstable
Urgency: low
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: 504370 504930 504934
Changes:
ecryptfs-utils (64-3) unstable; urgency=low
.
* Replacing obsolete dh_clean -k with dh_prep.
* Adding patch from Osamu Aoki <[EMAIL PROTECTED]> to update
ecryptfs-pam-doc.txt contents with s/Confidential/Private/
(Closes: #504934).
* Updating homepage and download location in control and copyright
(Closes: #504930).
* Updating author information in copyright.
* Installing desktop shortcut and readme to /usr/share/ecryptfs-utils.
Together with the fixes of upstream version 64, this interactively prompts
for passwords now (Closes: #504370).
Checksums-Sha1:
d12d005ef6c973e27f23aa3e8fab122b25bae1da 1536 ecryptfs-utils_64-3.dsc
7fe80691f8b4b8529f03f483d82e0edf17b8fa90 6318 ecryptfs-utils_64-3.diff.gz
87f34c2931e15d24f9dde5c727e6373f05e9092e 102058 ecryptfs-utils_64-3_i386.deb
7a9792533cefc2a7fe809bb6f64b397d90cffbf0 39536 libecryptfs0_64-3_i386.deb
f6f68daeffb30cbc540d7e9ccb5db46338470487 47898 libecryptfs-dev_64-3_i386.deb
Checksums-Sha256:
f58d992bb72deef88848ae8e2c412f67fee333dcf90afa578fc9248bfe8fd5ba 1536
ecryptfs-utils_64-3.dsc
271667bb58db12c786dd29fc4ac794b8acc947d005ba762b7006d97e2fa3b72f 6318
ecryptfs-utils_64-3.diff.gz
b5e9c12c6449385610638b683620033e624831b7b6dfc95517e5d2ad4dda661d 102058
ecryptfs-utils_64-3_i386.deb
97508bf207dd47cdb67a23ceaadf77d976f2667057d441cce7923244d9b0b026 39536
libecryptfs0_64-3_i386.deb
385fa092bf2fb22677a14add5ffcf72347923b42bd0a43d3dea1541fe510d2b8 47898
libecryptfs-dev_64-3_i386.deb
Files:
8727802292c88c74fa43701300244938 1536 misc optional ecryptfs-utils_64-3.dsc
29bb0de62cb986c7a48b5f383161ff65 6318 misc optional ecryptfs-utils_64-3.diff.gz
622e14eedaeab5359880407b15c633d1 102058 misc optional
ecryptfs-utils_64-3_i386.deb
3d7be7dc6fceba31ddba7a98c3e8df93 39536 libs optional libecryptfs0_64-3_i386.deb
4e50994d234669b53dbf1e3e5e0f51c5 47898 libdevel optional
libecryptfs-dev_64-3_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkkVK30ACgkQ+C5cwEsrK5439QCgzmVMYJKDzbRFS4h6k4k5pTn4
HPMAn3zoTud/APTP0PqZsG2cw59CkWB1
=i/eE
-----END PGP SIGNATURE-----
--- End Message ---
