Your message dated Sun, 13 Dec 2009 10:47:15 +0000
with message-id <[email protected]>
and subject line Bug#558347: fixed in cryptmount 4.0.2-1
has caused the Debian Bug report #558347,
regarding cryptmount init script should unmount and deconfigure all known
encryptedfilesystems at shutdown
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.)
--
558347: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558347
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cryptmount
Version: 4.0.1-1
Hello,
I am a mostly happy cryptmount user; however, I have one problem regarding
cryptmount: Sometimes I forget to run "cryptmount -u my_cryptmount_target"
before I shut down my computer, and because the encrypted filesystem is
not deconfigured and unmounted by the time the /etc/init.d/umountfs script
is called, my /home filesystem is not unmounted or remounted read-only
properly before the shutdown. As you can guess, this is not a good thing.
After looking at the init script of cryptmount, I saw that it unmounts and
deconfigures the cryptmount encrypted filesystems if and only if any are
declared to be set up at boot time in /etc/default/cryptmount.
Wouldn't it be sensible to unmount and deconfigure at shutdown time all
encrypted filesystems defined in /etc/cryptmount/cmtab, regardless of
whether we have some set up at boot time or not? After all, if an encrypted
filesystem is left mounted till the time we shut down, it should cleanly be
unmounted before the shutdown.
Here's a patch for the cryptmount init script which makes sure that all
currently mounted cryptmount filesystems are unmounted and deconfigured
at shutdown time even if a user (like me) forgets to run "cryptmount -u"
on them, and the user doesn't have any cryptmount filesystems declared
for setup at boot time.
=== 8< ====================================================================
--- cryptmount.orig 2009-11-27 23:24:41.000000000 -0500
+++ cryptmount 2009-11-27 23:25:11.000000000 -0500
@@ -106,8 +106,8 @@
if configured; then
echo "Stopping cryptmount ${STAGE}targets:"
doALL stop
- ${CM_EXE} --safetynet || true
fi
+ ${CM_EXE} --safetynet || true
;;
restart)
if configured; then
=== >8 ====================================================================
Regards,
M. Vefa Bicakci
--- End Message ---
--- Begin Message ---
Source: cryptmount
Source-Version: 4.0.2-1
We believe that the bug you reported is fixed in the latest version of
cryptmount, which is due to be installed in the Debian FTP archive:
cryptmount_4.0.2-1.diff.gz
to main/c/cryptmount/cryptmount_4.0.2-1.diff.gz
cryptmount_4.0.2-1.dsc
to main/c/cryptmount/cryptmount_4.0.2-1.dsc
cryptmount_4.0.2-1_amd64.deb
to main/c/cryptmount/cryptmount_4.0.2-1_amd64.deb
cryptmount_4.0.2.orig.tar.gz
to main/c/cryptmount/cryptmount_4.0.2.orig.tar.gz
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.
RW Penney <[email protected]> (supplier of updated cryptmount
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: Sun, 13 Dec 2009 08:00:00 +0000
Source: cryptmount
Binary: cryptmount
Architecture: source amd64
Version: 4.0.2-1
Distribution: unstable
Urgency: low
Maintainer: RW Penney <[email protected]>
Changed-By: RW Penney <[email protected]>
Description:
cryptmount - Management of encrypted file systems
Closes: 558347
Changes:
cryptmount (4.0.2-1) unstable; urgency=low
.
* Updated to version 4.0.2 of upstream package
.
* Closes: bug#558347 (Deconfiguring targets during system shutdown)
Checksums-Sha1:
89dcd45cf54d26b7f7ffbade80907b6718eb9b5f 1095 cryptmount_4.0.2-1.dsc
09566e78384ac315f020c6dc0ea595b0df898d30 386386 cryptmount_4.0.2.orig.tar.gz
4a20e39920d06a00f9f6e0a4e4ebc39d35261c16 17290 cryptmount_4.0.2-1.diff.gz
5483a7c78779f4171d1fc177ddd80c2befe821ac 125370 cryptmount_4.0.2-1_amd64.deb
Checksums-Sha256:
d2d89ba4420e7a259d37f650b67f53aa1341dba0e0df3261eee964e521690bd4 1095
cryptmount_4.0.2-1.dsc
60582025fbaee66f316dc06607c6e4e17fa841b2415399713c8d93d9fbfd16f7 386386
cryptmount_4.0.2.orig.tar.gz
1da08d70c45f40d60e78ed376e5bd947d79a3fcd2202ea7e64423a38a3c4c040 17290
cryptmount_4.0.2-1.diff.gz
83ee3e8af8e092801d16059996b8d33c1f00dc73e5322be91d075c353e3ba081 125370
cryptmount_4.0.2-1_amd64.deb
Files:
4dc71f6cf93c72c7c361f1e2a824272c 1095 admin extra cryptmount_4.0.2-1.dsc
8accb292742b547ac7b08f04407685d8 386386 admin extra
cryptmount_4.0.2.orig.tar.gz
bdced811515a5786c113c268c2e2a56b 17290 admin extra cryptmount_4.0.2-1.diff.gz
cb3192566a126d01fa8a4eaa12708c9f 125370 admin extra
cryptmount_4.0.2-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkskwrkACgkQMDatjqUaT91/eACgh3IYIer8na40sIDo+bj6IYDq
DzMAoJrdoW99jvxYFrJn6jfrX/LV+sLM
=vF+x
-----END PGP SIGNATURE-----
--- End Message ---
