Bug 217075 - File ownership on fusermount wrong
Summary: File ownership on fusermount wrong
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: fuse
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 217173 217183 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-23 19:42 UTC by jlbartos
Modified: 2007-11-30 22:11 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-11-26 07:37:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description jlbartos 2006-11-23 19:42:20 UTC
Description of problem:
The file permissions and ownership of /usr/bin/fusermount are wrong.
They used to be -rwsr-xr--  and are now -rwxr-xr-x .
They used to be root.fuse but are now root.root.

Version-Release number of selected component (if applicable):
fuse-2.6.0-1.fc6

How reproducible:
fuse-sshfs doesn't seem to work with the new permissions and ownership. User is
member of fuse group. 


Steps to Reproduce:
$ sshfs computer.home.lan local_directory/


  
Actual results:
fusermount: mount failed: Operation not permitted

Expected results:
Connection.

Additional info:
Using latest selinux-policy.
Reverting to previous permissions and ownership solved problem.
Didn't change the selinux contex which is:
system_u:object_r:mount_exec_t

Comment 1 jlbartos 2006-11-23 19:48:31 UTC
The command should have been:
sshfs computer.home.lan: local_directory/

Comment 2 jlbartos 2006-11-24 18:36:07 UTC
Bug 217173 is a double.

Comment 3 Peter Lemenkov 2006-11-25 06:46:25 UTC
*** Bug 217183 has been marked as a duplicate of this bug. ***

Comment 4 Peter Lemenkov 2006-11-25 06:46:51 UTC
*** Bug 217173 has been marked as a duplicate of this bug. ***

Comment 5 Peter Lemenkov 2006-11-25 10:09:47 UTC
Will be fixed in next release. Right now you may use quick and dirty workaround:

$ sudo chmod 4755 /usr/bin/fusermount

Comment 6 Peter Lemenkov 2006-11-26 07:37:29 UTC
Fixed in 2.6.0-2

Please, upgrade.


Note You need to log in before you can comment on or make changes to this bug.