NFSv4 ACLs
Subsystems (2)
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): 20120420185553.GB32622@samba2
Quoted 11 lines · Jeremy Allison
Quoted 7 lines · Ondrej Valousek
Hi List,
I know this has been asked many times, but I will ask one more time:
I would like to export NFSv4 mounted filesystem with Samba and would like to be able to use windows "security tab" in explorer to modify these ACLs.
Do I have any chance with Samba on RHEL-5/6?Does Linux have local API's to manipulate mounted NFSv4 ACLs ?
Quoted 7 lines
Samba has VFS modules to cope with mapping Windows ACLs onto NFSv4 ACLs but currently they only work on AIX, Linux with IBM's gpfs and Solaris right now.
If you can point me a docs showing the library APIs for Linux to allow programatic manipulation of NFSv4 ACLs then I can make it work on Linux too.
It's a bit idiosyncratic, but should be easy enough to handle if you want, I think: on the linux client, on an nfs4 filesystem, the "system.nfs4_acl" xattr contains the xdr-encoded ACL as it came in on the wire (network-byte-order and all). See the definition of fattr4_acl in rfc 3530.
--b.
Quoted 20 lines · J. Bruce Fields
Quoted 11 lines · Jeremy Allison
Quoted 7 lines · Ondrej Valousek
Hi List,
I know this has been asked many times, but I will ask one more time:
I would like to export NFSv4 mounted filesystem with Samba and would like to be able to use windows "security tab" in explorer to modify these ACLs.
Do I have any chance with Samba on RHEL-5/6?Does Linux have local API's to manipulate mounted NFSv4 ACLs ?
Quoted 7 lines
Samba has VFS modules to cope with mapping Windows ACLs onto NFSv4 ACLs but currently they only work on AIX, Linux with IBM's gpfs and Solaris right now.
If you can point me a docs showing the library APIs for Linux to allow programatic manipulation of NFSv4 ACLs then I can make it work on Linux too.
Quoted 5 lines
It's a bit idiosyncratic, but should be easy enough to handle if you want, I think: on the linux client, on an nfs4 filesystem, the "system.nfs4_acl" xattr contains the xdr-encoded ACL as it came in on the wire (network-byte-order and all). See the definition of
fattr4_aclin rfc 3530.
I'm sorry, but that *really* *really* sucks. There needs to be an API on the Linux side that implements both RichACLs and NFSv4 ACLs (as they're the same thing essentially).
Both GPFS and ZFS have defined API's to get and set ACLs. Just sticking them on a "system.nfs4_acl" xattr is a cop-out of monstrous proportions (and the kind of crap that we have to pull :-).
Jeremy.
Quoted 27 lines · Jeremy Allison
Quoted 20 lines · J. Bruce Fields
Quoted 11 lines · Jeremy Allison
Quoted 7 lines · Ondrej Valousek
Hi List,
I know this has been asked many times, but I will ask one more time:
I would like to export NFSv4 mounted filesystem with Samba and would like to be able to use windows "security tab" in explorer to modify these ACLs.
Do I have any chance with Samba on RHEL-5/6?Does Linux have local API's to manipulate mounted NFSv4 ACLs ?
Quoted 7 lines
Samba has VFS modules to cope with mapping Windows ACLs onto NFSv4 ACLs but currently they only work on AIX, Linux with IBM's gpfs and Solaris right now.
If you can point me a docs showing the library APIs for Linux to allow programatic manipulation of NFSv4 ACLs then I can make it work on Linux too.
Quoted 5 lines
It's a bit idiosyncratic, but should be easy enough to handle if you want, I think: on the linux client, on an nfs4 filesystem, the "system.nfs4_acl" xattr contains the xdr-encoded ACL as it came in on the wire (network-byte-order and all). See the definition of
fattr4_aclin rfc 3530.
Quoted 3 lines
I'm sorry, but that *really* *really* sucks. There needs to be an API on the Linux side that implements both RichACLs and NFSv4 ACLs (as they're the same thing essentially).
Yes, that's the eventual plan.
The richacl patches still need a little more work, and alas there's noone working on them currently as far as I know.
So if you wanted something that would work now, you could use system.nfs4_acl now and later replace that by something that tried richacls and then fell back.
The xdr isn't hard to parse or create--the main problem would be figuring out what to do with the names....
(By the way, is reexporting nfs with samba really going to work well anyway?)
--b.
Quoted 37 lines · J. Bruce Fields
Quoted 27 lines · Jeremy Allison
Quoted 20 lines · J. Bruce Fields
Quoted 11 lines · Jeremy Allison
Quoted 7 lines · Ondrej Valousek
Hi List,
I know this has been asked many times, but I will ask one more time:
I would like to export NFSv4 mounted filesystem with Samba and would like to be able to use windows "security tab" in explorer to modify these ACLs.
Do I have any chance with Samba on RHEL-5/6?Does Linux have local API's to manipulate mounted NFSv4 ACLs ?
Quoted 7 lines
Samba has VFS modules to cope with mapping Windows ACLs onto NFSv4 ACLs but currently they only work on AIX, Linux with IBM's gpfs and Solaris right now.
If you can point me a docs showing the library APIs for Linux to allow programatic manipulation of NFSv4 ACLs then I can make it work on Linux too.
Quoted 5 lines
It's a bit idiosyncratic, but should be easy enough to handle if you want, I think: on the linux client, on an nfs4 filesystem, the "system.nfs4_acl" xattr contains the xdr-encoded ACL as it came in on the wire (network-byte-order and all). See the definition of
fattr4_aclin rfc 3530.Quoted 3 lines
I'm sorry, but that *really* *really* sucks. There needs to be an API on the Linux side that implements both RichACLs and NFSv4 ACLs (as they're the same thing essentially).
Yes, that's the eventual plan.
The richacl patches still need a little more work, and alas there's noone working on them currently as far as I know.
Quoted 6 lines
So if you wanted something that would work now, you could use system.nfs4_acl now and later replace that by something that tried richacls and then fell back.
The xdr isn't hard to parse or create--the main problem would be figuring out what to do with the names....
Samba does handle id mapping in general and name mapping shouldn't be too hard to add, SIDs would be easier for us though :-)
Quoted 2 lines
(By the way, is reexporting nfs with samba really going to work well anyway?)
Not really, it is generally unsupported, except for read only shares. It will work in most of the simple cases for writing .. until it breaks :)
Simo.
Signature · 3 lines
Simo Sorce Samba Team GPL Compliance Officer <[email protected]> Principal Software Engineer at Red Hat, Inc. <[email protected]>
Quoted 9 lines · simo
Quoted 6 lines · J. Bruce Fields
Quoted 5 lines · Jeremy Allison
Quoted 4 lines · J. Bruce Fields
Quoted 3 lines · Jeremy Allison
Quoted 2 lines · Ondrej Valousek
Hi List,
Quoted 6 lines
Quoted 2 lines
(By the way, is reexporting nfs with samba really going to work well anyway?)
Not really, it is generally unsupported, except for read only shares. It will work in most of the simple cases for writing .. until it breaks :)
Hi
That's worrying.
We been rw'ing nfs/samba for years. Maybe we're the only ones. nfs3 for our Linux clients and samba for the rest. Same shared data. Only Posix acl's though. Maybe that's the simple bit? Cheers,
Steve
Quoted 17 lines · steve
Quoted 9 lines · simo
Quoted 6 lines · J. Bruce Fields
Quoted 5 lines · Jeremy Allison
Quoted 4 lines · J. Bruce Fields
Quoted 3 lines · Jeremy Allison
Quoted 2 lines · Ondrej Valousek
Hi List,
Quoted 6 lines
Quoted 2 lines
(By the way, is reexporting nfs with samba really going to work well anyway?)
Not really, it is generally unsupported, except for read only shares. It will work in most of the simple cases for writing .. until it breaks :)
Quoted 8 lines
Hi
That's worrying.We been rw'ing nfs/samba for years. Maybe we're the only ones. nfs3 for our Linux clients and samba for the rest. Same shared data. Only Posix acl's though. Maybe that's the simple bit?
Cheers,
Steve
Are Samba and NFSd running on the same server, exporting the same data? That is what is expected to work. See 'kernel oplocks' (the default of which will change for 4.0) to allow NFS and Samba to break each other's oplocks.
What Simo cautions about is where an NFS server (say a NAS server) exports to some direct NFS clients, and then a 'proxy' Samba server is an NFS client and a Samba server for Windows clients. This 'proxy' setup is considered dangerous.
Andrew Bartlett
Signature · 2 lines
Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org
Quoted 27 lines · Andrew Bartlett
Quoted 17 lines · steve
Quoted 9 lines · simo
Quoted 6 lines · J. Bruce Fields
Quoted 5 lines · Jeremy Allison
Quoted 4 lines · J. Bruce Fields
Quoted 3 lines · Jeremy Allison
Quoted 2 lines · Ondrej Valousek
Hi List,
Quoted 6 lines
Quoted 2 lines
(By the way, is reexporting nfs with samba really going to work well anyway?)
Not really, it is generally unsupported, except for read only shares. It will work in most of the simple cases for writing .. until it breaks :)
Quoted 8 lines
Hi
That's worrying.We been rw'ing nfs/samba for years. Maybe we're the only ones. nfs3 for our Linux clients and samba for the rest. Same shared data. Only Posix acl's though. Maybe that's the simple bit?
Cheers,
Steve
Quoted 5 lines
Are Samba and NFSd running on the same server, exporting the same data? That is what is expected to work. See 'kernel oplocks' (the default of which will change for 4.0) to allow NFS and Samba to break each other's oplocks.
s3 and nfs work fine (maybe others are doing it too?)
We are testing Samba4 and nfs now and yes same data, same box. As yet, we've not been able to break it no matter what we throw at it.
When will the oplocks default change? Will it affect us?
Cheers,
Steve