Bug 120400 - can't setup user mountable cifs shares
Summary: can't setup user mountable cifs shares
Alias: None
Product: Fedora
Classification: Fedora
Component: samba   
(Show other bugs)
Version: 6
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Simo Sorce
QA Contact:
Keywords: Reopened
Depends On:
TreeView+ depends on / blocked
Reported: 2004-04-08 13:34 UTC by massimo
Modified: 2007-11-30 22:10 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-29 17:39:20 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description massimo 2004-04-08 13:34:16 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b)
Gecko/20040319 Epiphany/1.2.1

Description of problem:
I've configured in /etc/fstab a line like this:

// /mnt/net cifs
noauto,username=xxxxxx,pass=xxxxxx,uid=500,gid=100     0 0

and from root I can 'mount /mnt/net' without problems, but if I try to
add 'user' to the options to be able to mount from a regular user, I
receive the error 'invalid or missing username' when I do 'mount /mnt/net'

looks a lot like it misinterpret the 'user' option as as the username

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. setup a cifs share in fstab with the option 'user'
2. do 'mount <mountpoint>'


Additional info:


Comment 1 Richard Hughes 2004-05-17 15:47:22 UTC
I have talked to Steven French about this problem, and he has updated
mount.cifs to allow user mounting.

Email from Steve:
... I changed it so it now ignores "user" when specified with no
value (which mount took to mean user mount) because the mount tool can
insert that in the mount options in the example that Richard mentioned...

A svn pull of SAMBA_3_0 should work - this has the newest (and
working) mount.cifs.c code.

Comment 2 Richard Hughes 2004-09-19 13:09:09 UTC
Latest rawhide includes updated /sbin/mount.cifs
Update "samba-client" from rawhide to fix problem. 

Comment 3 Richard Hughes 2004-09-19 13:11:35 UTC
Nearly forgot. You'll need to do a # chmod +s /sbin/mount.cifs to make
the file setuid. This bug can be closed now. 

Comment 4 Bastien Nocera 2004-12-17 10:51:44 UTC
I'll keep this bug opened. Normal users can't mount cifs shares if
/sbin/mount.cifs isn't setuid root.
Jay, is there any reason why mount.cifs isn't setuid?

Comment 5 arch harris 2006-06-15 21:35:39 UTC
This problem (still?) exists in RH Enterprise WS 4.  The version number returned
by mount.cifs is 1.5.

Comment 6 Matthew Miller 2006-07-10 22:40:37 UTC
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!

Comment 7 John Thacker 2006-10-29 21:24:27 UTC
Closing per lack of response to previous request for information.  Note that FC3
and FC4 are only supported by Fedora Legacy for security fixes.  If this is a
security issue, please assign to Fedora Legacy.  Otherwise, please retest with
FC5 or FC6, and if it still occurs, please reopen and assign to the correct
version.  Many changes have occurred since this bug was first filed and it may
be fixed in a more recent version.  We apologize for not fixing this bug
earlier.  Thanks!

Comment 8 Bastien Nocera 2006-10-29 22:42:38 UTC
Reopening, still current with FC6.(In reply to comment #5)

> This problem (still?) exists in RH Enterprise WS 4.  The version number returned
> by mount.cifs is 1.5.

Arch, please file a bug directly against RHEL4 if this is still a problem, or
better, open a support request.

Comment 9 Simo Sorce 2007-10-20 01:15:47 UTC
Should be ok in F-7/F-8 can you confirm?

Comment 10 Simo Sorce 2007-10-29 17:39:20 UTC
Had no reply to the last question, I assume it is fixed.

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