linux-kernel - Re: [PATCH v11 16/48] 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:	Fri, 16 Oct 2015 18:13:19 +0200
From:	Andreas Gruenbacher <agruenba@...hat.com>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	Alexander Viro <viro@...iv.linux.org.uk>,
	"Theodore Ts'o" <tytso@....edu>,
	Andreas Dilger <adilger.kernel@...ger.ca>,
	"J. Bruce Fields" <bfields@...ldses.org>,
	Jeff Layton <jlayton@...chiereds.net>,
	Trond Myklebust <trond.myklebust@...marydata.com>,
	Anna Schumaker <anna.schumaker@...app.com>,
	Dave Chinner <david@...morbit.com>,
	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
	xfs@....sgi.com,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Linux FS Devel <linux-fsdevel@...r.kernel.org>,
	Linux NFS Mailing List <linux-nfs@...r.kernel.org>,
	linux-cifs@...r.kernel.org, Linux API <linux-api@...r.kernel.org>
Subject: Re: [PATCH v11 16/48] richacl: Automatic Inheritance

On Fri, Oct 16, 2015 at 6:00 PM, Andy Lutomirski <luto@...capital.net> wrote:
> On Fri, Oct 16, 2015 at 8:17 AM, Andreas Gruenbacher
> <agruenba@...hat.com> wrote:
>> Automatic Inheritance works as follows:
>>
>>  - When the RICHACL_AUTO_INHERIT flag in the acl of a file or directory
>>    is not set, the file or directory is not affected by AI.
>>
>>  - When the RICHACL_AUTO_INHERIT flag in the acl of a directory is set
>>    and a file or subdirectory is created in that directory, the
>>    inherited acl will have the RICHACL_AUTO_INHERIT flag set, and all
>>    inherited aces will have the RICHACE_INHERITED_ACE flag set.  This
>>    allows user space to distinguish between aces which have been
>>    inherited and aces which have been explicitly added.
>
> What if the file or subdirectory that's created in that directory is a
> hard link?

Directories cannot have hard links.

When a file is hard linked into multiple directories with different
inheritable permissions, the permissions set last will "win". This
isn't particularly pretty, but it's the way this has worked on that
other operating system with significant marked share for the last
fifteen years.

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/