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]
Message-ID: <CAHpGcM+h6NmJ8F5B+bPAtaNXVeLUiGh-BetpjQLcU_-1Zwbd=Q@mail.gmail.com>
Date:	Thu, 14 May 2015 01:52:52 +0200
From:	Andreas Grünbacher <andreas.gruenbacher@...il.com>
To:	Frank Filz <ffilzlnx@...dspring.com>
Cc:	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-14 0:56 GMT+02:00 Frank Filz <ffilzlnx@...dspring.com>:
> I'm not clear what the RICHACL_PROTECTED flag actually does. It looks like it's
> only tested in chmod, and then only if the mode matches the mask (at least if I'm
> understanding the code right).

User space may propagate automatically inherited permissions to files
which are subject to automatic inheritance (RICHACL_AUTO_INHERIT) and
which are not protected from being modified (RICHACL_PROTECTED).

In richacl_chmod(), we simply detect when a chmod has no effect on the
acl: this is when the file masks are already correct, when the acl is
already masked, and when Automatic Inheritance won't affect the acl.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ