similar to: nfsv4 acl's on zfs

Hi all, I would like to try to start up a conversation about the "proper" handling of usernames by samba/winbind. I know our current active directory setup is not really considered supported via samba and I would like to know if the samba developers think this might change, or if there are any recommendations for my issues. *** Since this came out rather long, here is a quick

We have a situation where we have two domains that can authenticate users. One for students, one for faculty/staff, both with rfc2307 attributes. Winbind does lookups properly to the domain that samba is joined to, but claims it cannot lookup sids in the other domain. There is an explicit trust relationship, and wbinfo -g and -u can see the users just fine. However, getent passwd still can

Hey all. I am working on getting solaris 10 and 9 clients authenticating to active directory. We have a test setup with windows 2003 r2 and the unix fields filled out. All was going well with a combination of pam_krb5 and nss_ldap and ldap mappings, including working automouting of home directories. This included orginally, set up instructions from microsoft where they said to create a user

I developed some code that called subroutines from the Port3 Library (http://www-out.bell-labs.com/project/PORT/). I?m thinking about making it available as an R package. But I?m not sure if their NON-EXCLUSIVE SOURCE CODE LICENSE AGREEMENT ( http://www-out.bell-labs.com/topic/swdist/licenses/nesource.txt ) permits this. I tried contacting the contact person listed on the website. Not

Author: marks Repository: /hg/zfs-crypto/gate Revision: d3160869d28dca623e514dc1f38e84d9335c2a55 Log message: 6362908 nfsv4-test: RENAME does not check PERM with NFSv4/ZFS 6372549 nfsv4 server returns OK for SETATTR of size on a symlink over ZFS, INVAL is expected Files: update: usr/src/uts/common/fs/zfs/zfs_acl.c update: usr/src/uts/common/fs/zfs/zfs_vnops.c

I am trying calculate a probability using numerical integration. The first program I ran spit out an answer in a very short time. The program is below: ## START PROGRAM trial <- function(input) { pmvnorm(lower = c(0,0), upper = c(2, 2), mean = input, sigma = matrix(c(.1, 0, 0, .1), nrow = 2, ncol = 2, byrow = FALSE)) } require(mvtnorm) require(adapt) bottomB <- -5*sqrt(.1) topB <-

Hi I am accessing files in a ZFS file system via NFSv4. I am not logged in a root. File permissions look as expected when I inspect them with ls -v and ls -V I only have owner and group ACLs...nothing for everyone. bash-3.00$ id uid=100(timt) gid=10001(ccbcadmins) bash-3.00$ groups ccbcadmins staff bash-3.00$ ls -v testacl -rwxrwx---+ 1 timt ccbcadmins 0 Jan 31 16:24 testacl

Author: marks Repository: /hg/zfs-crypto/gate Revision: 30d7e3669aa20772767cb9726d60c32659192c23 Log message: 6395977 unpack dump core when run over NFSv4 over ZFS Files: update: usr/src/cmd/compress/compress.c update: usr/src/cmd/pack/pack.c update: usr/src/cmd/unpack/unpack.c

Author: thurlow Repository: /hg/zfs-crypto/gate Revision: 1713bd2d1b7b2466298721235c1f98e4e01b0be8 Log message: 6344186 NFSv3 needs to support .zfs (like NFSv4 already does) Files: update: usr/src/cmd/fs.d/nfs/mountd/mountd.c update: usr/src/cmd/fs.d/nfs/mountd/mountd.h update: usr/src/cmd/fs.d/nfs/nfslog/fhtab.h update: usr/src/cmd/fs.d/nfs/nfslog/nfslog_elf.c update:

Author: marks Repository: /hg/zfs-crypto/gate Revision: 49eca6287e6a581e3e46ada9d34a54b7665027b1 Log message: 6434606 getfacl/setfacl of files/dirs over NFSv4 with ZFS underneath fail Files: update: usr/src/uts/common/fs/fs_subr.c

Good morning, folks. I'm involved in a project to enforce NFSv4 ACL's across a variety of storage platforms, in particular NetApps sharing NFS. That works fiine with the NetApp NFS qtrees, but we'd like to share those with CIFS clients as well. This works, and restricts access the way we expect NFSv4 ACL's to work, but the Windows clients cannot view any of the security settings

This is a PoC patch for NFSv4/ZFS ACLs. The objective of the patch is that rsync --acls support NFSv4/ZFS ACLs without requiring a new command line option NFSv4 ACLs can't be represented using POSIX draft ACLs, if an NFSv4 ACL is present a separate POSIX draft ACL will not be present and there are new APIs to access NFSv4 ACLs. So we need to distinguish between NFSv4 ACLs and POSIX ACLs in

Hi people, I'm testing Samba 4.0.17 running as classic pdc mode under FreeBSD 10 and 9.2 , all shares are on ZFS volumes, i would like to use UFS instead of ZFS , but according the wiki page https://wiki.freebsd.org/NFSv4_ACLs nfsv4 inheritance flags works only with ZFS , i tried the parameters inherit acls and inherit permissions with module vfs_zfsacl on the UFS shares but got no success

>From what I've read so far Samba supports POSIX ACLs, correct? If so, will they work over NFSv4 exports? The reason I'm asking is as follows: We're considering redoing our storage systems which currently also house Samba servers. These are currently running on Linux boxes with NFS exports to the rest of our networks. Many machines with massive amounts of storage, one Samba

Dear list, I have a freebsd 10 server with a ZFS pool, where data is shared with samba. ZFS ACLs are compliant with NFSv4 ACL. ZFS acl mode and inherit are set to passthrough (not sure it's really relevant here). The server is a domain member, and "standard" file service works well. I had the same setup with samba 3.5, where I was able to have a single share for all groups, so I

I have a situation where I need to share, via Samba, a filesystem mounted via NFSv4. I'm struggling with the best way to make Samba see the NFSv4 ACLs and enumerate them to provide the proper SMB/CIFS access to the files, instead of "Access Denied" errors that I currently get. Looking at the Samba source, the only obvious NFSv4 stuff appears to be the following: - zfsacl, available

Right now, FreeBSD supports one type of ACLs - so called POSIX.1e ACLs. They are natural extension of the traditional Unix permissions, and for a long time were the only nonproprietary ACL type in Unix systems. Times change, and now there are several problems with them: they never actually become standard (the draft they are based on was withdrawn); this results in minor incompatibilities

> On Dec 3, 2015, at 17:24, Jeremy Allison <jra at samba.org> wrote: > >> On Thu, Dec 03, 2015 at 03:54:21PM -0700, Nick Couchman wrote: >> I have a situation where I need to share, via Samba, a filesystem mounted via NFSv4. I'm struggling with the best way to make Samba see the NFSv4 ACLs and enumerate them to provide the proper SMB/CIFS access to the files, instead

Greetings I'm running Red Hat 6.2. Both smbd and nmbd are up and running. I can see my Linux box from PCs in my LAN. Problem is, I can't access them. I tried the troubleshooting guide found at http://us2.samba.org/samba/docs/DIAGNOSIS.html, and got as far as the second step. When I do "smbclient -L myserver," I get the following error message: session request to ODYSSEUS

On Thu, Dec 03, 2015 at 03:54:21PM -0700, Nick Couchman wrote: > I have a situation where I need to share, via Samba, a filesystem mounted via NFSv4. I'm struggling with the best way to make Samba see the NFSv4 ACLs and enumerate them to provide the proper SMB/CIFS access to the files, instead of "Access Denied" errors that I currently get. > > Looking at the Samba source,