linux-kernel - Re: [RFC v3 20/45] richacl: Automatic Inheritance

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 May 2015 23:15:50 +0200
From:	Andreas Grünbacher <andreas.gruenbacher@...il.com>
To:	Jeremy Allison <jra@...ba.org>
Cc:	Frank Filz <ffilzlnx@...dspring.com>, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, linux-nfs@...r.kernel.org
Subject: Re: [RFC v3 20/45] richacl: Automatic Inheritance

2015-05-13 22:55 GMT+02:00 Jeremy Allison <jra@...ba.org>:
> Hmm. Just realized we may be talking about different things :-).
>
> In SMB/Samba the clients can create a file with no ACL, and
> the directory ACL is auto inherited. *That* we fake in
> Samba by creating then updating.

Yes, that's what I was trying to say in the commit message of this
patch. Samba will have to continue doing that.

> But in Windows there are the concept of "inherited" ACE
> entries, which can come from parents of parents of parents
> (etc.) objects.

Fair enough, even if from the child's point of view, all inherited
entries come from the direct parent no matter where the parent
has gotten them from.

> When a client modifies one of these on an
> upper level directory, the server doesn't do the auto
> updating that the vision of the file system might lead
> you to expect - that updating is done by a tree walk
> by the client.

Good, then we're on the same page.

Thanks,
Andreas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/