/bin/fusermount lost setuid bit, breaking all FUSE filesystems
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fuse (Ubuntu) |
Fix Released
|
High
|
Dimitri John Ledkov |
Bug Description
$ sshfs linerva: /tmp/m
fusermount: mount failed: Operation not permitted
$ ls -l /bin/fusermount
-rwxr-xr-x 1 root root 30800 May 24 08:18 /bin/fusermount
$ dpkg -c fuse_2.
-rwxr-xr-x root/root 30800 2013-05-24 08:18 ./bin/fusermount
(fuse 2.9.0-1ubuntu3 from raring is not affected.)
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: fuse 2.9.2-4ubuntu1
ProcVersionSign
Uname: Linux 3.9.0-3-generic x86_64
NonfreeKernelMo
ApportVersion: 2.10.2-0ubuntu1
Architecture: amd64
Date: Wed May 29 22:07:16 2013
EcryptfsInUse: Yes
InstallationDate: Installed on 2010-12-05 (906 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
MarkForUpload: True
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: fuse
UpgradeStatus: Upgraded to saucy on 2012-11-15 (195 days ago)
Changed in fuse (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Dmitrijs Ledkovs (xnox) |
This bug was fixed in the package fuse - 2.9.2-4ubuntu2
---------------
fuse (2.9.2-4ubuntu2) saucy; urgency=low
* Correct call in debian/rules to use DEB_HOST_ARCH_OS to set setuid bit
on /bin/fusermount, which got lost in the previous upload (LP:
#1185622).
-- Dmitrijs Ledkovs <email address hidden> Thu, 30 May 2013 10:28:27 +0100