Permissions problem with cifs.mount

Operating Systems Linux Red Hat Permissions problem with cifs.mount

01-18-2013

Registered User

1, 0

Join Date: Jan 2013

Last Activity: 18 January 2013, 9:34 AM EST

Posts: 1

Thanks Given: 0

Thanked 0 Times in 0 Posts

Permissions problem with cifs.mount

hi,

I have the following permission problems with cifs.mount : a share on a VNXe (EMC NAS) is accessed by two RHEL 5.9 accounts (authenticated by Active Directory); One account has read+wite permission to the share , the second one has only read permission. Both accounts uses the following mount command:

mount -t cifs --verbose -o sec=krb5,cifsacl,multiuser //NAS/share/mount_point

First, the multiuser option is rejected (but the mounting is done). Moreover both accounts can write to the share, ignoring the NTFS permissions. What is going on ?

Zarake

View Public Profile for Zarake

Find all posts by Zarake

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Help with cifs/smbfs mount on Solaris

I have a Linux server with a cifsmount, the entry in /etc/fstab looks like this: //windows_server_name/xyz /opt/xyz cifs credentials=/etc/creds/xyz.creds,uid=abc,gid=abc,noserverino,directio,_netdev 0 0 The username and password are stored in /etc/creds/xyz.creds This works fine.:wall: How...

2. AIX

AIX available cifs mount options

Hi, I can't find any documentation of all available mount options of mount -v cifs Unfortunately you can specify any fantasy options, no complains, and the mount command shows this option In particular I want to know if there is a possibility to completely disable cifs caching in aix,...

3. AIX

Mount CIFS on AIX

Hello AIX gurus, I am trying to mount a CIFS share on AIX and I could use some help. Here are the environment details: AIX - 6100-05-01-1016 Domain Controller - WIN2K8R2 (authentication takes place here) CIFS share is stored on a NetApp storage array that is joined to the domain I have...

4. UNIX and Linux Applications

Slackware: mount cifs with kerberos

On Slackware14.0 Compiled cifs-utils with kerberos support on request-key.conf added create cifs.spnego * * /usr/sbin/cifs.upcall %k %d But when i try mount -o sec=krb5 -t cifs //SLACK64//Users /media/users mount error(38): Function not implemented Refer to the...

5. Linux

new file group permission of CIFS mount

After switching from smbfs mount, the dmask/dir_mode and fmask/file_mode no longer have an effect on the newly created files. It seems to use the system umask instead. I need the group to have write permissions without changing the root umask on the system. Any ideas? example fstab: ...

6. AIX

AIX cifs mount to Windows Server 2008 R2

Hi i have some problem to mount a Windows Server 2008 R2 share on AIX. I found the artikel 157701-aix-cifs-mount-windows-server-2008-share on the Forum (cant post the Link) witch decribe my situation but there is no solution. I can mount a share to a Windows 2003 SP2 Server but not to 2008 R2...

7. AIX

CIFS Mount not mounting on my AIX server

Dear Experts, Im facing a unique situation. We got a windows server folder cifs mounted on my AIX server. Before restarting the win server I tried unmounting the cifs mount. It got hanged and win server was restarted however. Now Im trying to mount the same. It prompts for password...

8. AIX

CIFS Mount Problem in AIX 5.3 TL12 SP-01-1016

Hi all, We are experiencing below mentioned error on mounting windows Share on AIX 5.3 when we migrate our TL from 8 to TL12-SP01, we also checked the allowed password length for mounting CIFS which is fine(10 characters in our case). On IBM fix central site there is a fix IZ63140 for...

9. UNIX for Advanced & Expert Users

mount -t cifs permission denied by mount -t smbfs works fine

I am having trouble mounting with cifs, but mounting the exact same command with smbfs works fine. The share is on another samba server and is set to full public guest access. # mount -t cifs //servername/sharename /mnt/temp -o password="" mount error 13 = Permission denied Refer to the...

10. HP-UX

mount with CIFS

hi everyone months ago i installed software on hp-ux box. So instead of going to the server room (which is far and cold :) ), I put the DVD in my windows xp box and mount it using CIFS, it was successful. Now I want to install another software on the same hp-ux box using the same windows...

LEARN ABOUT LINUX

cifs.upcall

CIFS.UPCALL(8)						    System Administration tools 					    CIFS.UPCALL(8)

NAME

       cifs.upcall - Userspace upcall helper for Common Internet File System (CIFS)

SYNOPSIS

       cifs.upcall [--trust-dns|-t] [--version|-v] [--legacy-uid|-l] [--krb5conf=/path/to/krb5.conf|-k /path/to/...] {keyid}

DESCRIPTION

       This tool is part of the cifs-utils suite.

       cifs.upcall is a userspace helper program for the linux CIFS client filesystem. There are a number of activities that the kernel cannot
       easily do itself. This program is a callout program that does these things for the kernel and then returns the result.

       cifs.upcall is generally intended to be run when the kernel calls request-key(8) for a particular key type. While it can be run directly
       from the command-line, it's not generally intended to be run that way.

OPTIONS

       -c
	   This option is deprecated and is currently ignored.

       --krb5conf=/path/to/krb5.conf|-k /path/to/krb5.conf
	   This option allows administrators to set an alternate location for the krb5.conf file that cifs.upcall will use.

       --trust-dns|-t
	   With krb5 upcalls, the name used as the host portion of the service principal defaults to the hostname portion of the UNC. This option
	   allows the upcall program to reverse resolve the network address of the server in order to get the hostname.

	   This is less secure than not trusting DNS. When using this option, it's possible that an attacker could get control of DNS and trick
	   the client into mounting a different server altogether. It's preferable to instead add server principals to the KDC for every possible
	   hostname, but this option exists for cases where that isn't possible. The default is to not trust reverse hostname lookups in this
	   fashion.

       --legacy-uid|-l
	   Traditionally, the kernel has sent only a single uid= parameter to the upcall for the SPNEGO upcall that's used to determine what
	   user's credential cache to use. This parameter is affected by the uid= mount option, which also governs the ownership of files on the
	   mount.

	   Newer kernels send a creduid= option as well, which contains what uid it thinks actually owns the credentials that it's looking for. At
	   mount time, this is generally set to the real uid of the user doing the mount. For multisession mounts, it's set to the fsuid of the
	   mount user. Set this option if you want cifs.upcall to use the older uid= parameter instead of the creduid= parameter.

       --version|-v
	   Print version number and exit.

CONFIGURATION FOR KEYCTL

       cifs.upcall is designed to be called from the kernel via the request-key callout program. This requires that request-key be told where and
       how to call this program. The current cifs.upcall program handles two different key types:

       cifs.spnego
	   This keytype is for retrieving kerberos session keys

       dns_resolver
	   This key type is for resolving hostnames into IP addresses. Support for this key type may eventually be deprecated (see below).

       To make this program useful for CIFS, you'll need to set up entries for them in request-key.conf(5). Here's an example of an entry for each
       key type:

	   #OPERATION  TYPE	      D C PROGRAM ARG1 ARG2...
	   #=========  =============  = = ================================
	   create      cifs.spnego    * * /usr/sbin/cifs.upcall %k
	   create      dns_resolver   * * /usr/sbin/cifs.upcall %k

       See request-key.conf(5) for more info on each field.

       The keyutils package has also started including a dns_resolver handling program as well that is preferred over the one in cifs.upcall. If
       you are using a keyutils version equal to or greater than 1.5, you should use key.dns_resolver to handle the dns_resolver keytype instead
       of cifs.upcall. See key.dns_resolver(8) for more info.

SEE ALSO

       request-key.conf(5), mount.cifs(8), key.dns_resolver(8)

AUTHOR

       Igor Mammedov wrote the cifs.upcall program.

       Jeff Layton authored this manpage.

       The maintainer of the Linux CIFS VFS is Steve French.

       The Linux CIFS Mailing list is the preferred place to ask questions regarding these programs.

cifs-utils							    02/07/2010							    CIFS.UPCALL(8)

Red Hat