public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve French <smfrench@austin.rr.com>
To: Martin Koeppe <mkoeppe@gmx.de>
Cc: linux-cifs-client@lists.samba.org,
	samba-technical@lists.samba.org, linux-kernel@vger.kernel.org
Subject: Re: support for mknod to windows now in cifs vfs
Date: Sun, 20 Nov 2005 18:52:49 -0600	[thread overview]
Message-ID: <43811A61.70405@austin.rr.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0511202323230.27607@vmdebian.local.koeppe-net.de>

Martin Koeppe wrote:

>
> For the mapping of the lower 9 mode bits to NT security entries, I 
> just found a good description from Corinna at 
> http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping
>
> I encountered the same ACE reordering in explorer with sfu files, but 
> didn't think about these deny entries enough. At least in this regard, 
> cygwin and sfu seem to be compatible. So, Steve, this may be 
> interesting to you for implementing chmod.
>
> And it might be of interest to the samba people, if they decide to 
> implement an sfu option on the server side.
>
>
> Martin
>
Martin,
Once again thank you for finding useful data on hard problems.   I don't 
think this will be too hard to code into the cifs vfs (I also wish ntfs 
already had worker functions for setfacl and chmod similar to this...) 
but now the interesting question is how fast it is worth coding and 
getting in mainline -
1)  acl and chmod mapping (ie the ntfs security descriptor like way, 
rather than Samba-only posix acl way),  and
2) Kerberos/SPNEGO session setup

are the two most common requests for the cifs vfs these days.   The 
upcall for Kerberos support is begun but not complete, and it has taken 
longer than I had hoped partly due to lack of examples - the only uses 
of the new cn.ko (Linux "connector") posted so far are simpler 
(notification up, rather than "request up /response down").

      parent reply	other threads:[~2005-11-21  0:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <437EAA7F.5050907@austin.rr.com>
     [not found] ` <1132404007.4397.3.camel@amy.flyaway.abartlet.net>
     [not found]   ` <437F8339.3060502@austin.rr.com>
2005-11-20  3:56     ` support for mknod to windows now in cifs vfs Andrew Bartlett
     [not found] ` <Pine.LNX.4.62.0511202323230.27607@vmdebian.local.koeppe-net.de>
2005-11-21  0:52   ` Steve French [this message]

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=43811A61.70405@austin.rr.com \
    --to=smfrench@austin.rr.com \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkoeppe@gmx.de \
    --cc=samba-technical@lists.samba.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox