All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steve French (smfltc)" <smfltc@us.ibm.com>
To: linux-cifs-client@lists.samba.org
Cc: linux-fsdevel@vger.kernel.org, samba-technical@lists.samba.org,
	stefan.rijnhart@milieudefensie.nl
Subject: Re: Acls and cifs mounted shares
Date: Fri, 04 Jan 2008 12:23:42 -0600	[thread overview]
Message-ID: <477E79AE.8010000@us.ibm.com> (raw)

> There seems to be a lot of activity in the cifs development team with
> respect to acls. Does this mean that we can look forward to functional
> acl permissions in a recent or forthcoming kernel?

Yes.  2.6.24 will have support for returning a more accurate mode for a file on a cifs mount based on its cifs ACL.  This requires mounting with the new "cifsacl" mount option and it requires that the Linux cifs module be configured/built with CONFIG_CIFS_EXPERIMENTAL.  This is not needed for Samba and other servers which support the CIFS Unix extensions to the protocol since they already support returning the mode of a file from the server (and they also support getting and setting POSIX ACLs).

The current cifs development tree (which is also picked up by -mm) includes code to allow users to change the mode of a file via changing the cifs ACL (when mounted with the "cifsacl" mount option), but additional testing is needed on that before it will be ready to merge into mainline.

The next step is to allow getting and changing the CIFS ACL directly - today that can be done via the samba client utility "smbcacls" for example but it may be helpful to allow changes to CIFS/NTFS/NFSv4 ACLs (which are similar) from a tool like setfacl so that CIFS and NFS and NTFS modules can use similar tool on the client.   Andreas Gruenbacher has had some proposals for this (e.g. see http://www.suse.de/~agruen/agruen-nfs4acl.pdf)


                 reply	other threads:[~2008-01-04 18:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=477E79AE.8010000@us.ibm.com \
    --to=smfltc@us.ibm.com \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=samba-technical@lists.samba.org \
    --cc=stefan.rijnhart@milieudefensie.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.