force option (-f) of umount.ecryptfs_private no longer works
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eCryptfs |
Fix Released
|
Medium
|
Tyler Hicks |
Bug Description
According to the mount.ecryptfs_
/* Determine if mounting or unmounting by looking at the invocation */
if (strstr(argv[0], "umount") == NULL) {
} else {
/* Determine if unmounting is forced */
if (argv[1] != NULL && strncmp(argv[1], "-f", 2) == 0) {
} else {
}
}
However, the alias support broke that option when it took over the argv[1] variable in r526. This results in an error when you try to force an unmount:
$ /sbin/umount.
Bad file
Error reading configuration file
Related branches
- eCryptfs: Pending requested
-
Diff: 205 lines (+96/-22)4 files modifieddebian/changelog (+17/-0)
src/pam_ecryptfs/pam_ecryptfs.c (+1/-1)
src/utils/ecryptfs-umount-private (+2/-0)
src/utils/mount.ecryptfs_private.c (+76/-21)
This fix was released in ecryptfs-utils version 108.