linux-kernel - Re: [RFC 00/21] Richacls

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: <20150227224846.GB8750@fieldses.org>
Date:	Fri, 27 Feb 2015 17:48:46 -0500
From:	bfields@...ldses.org (J. Bruce Fields)
To:	Andreas Gruenbacher <andreas.gruenbacher@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	linux-nfs@...r.kernel.org
Subject: Re: [RFC 00/21] Richacls

Thanks for this!

On Thu, Feb 26, 2015 at 12:41:21AM +0100, Andreas Gruenbacher wrote:
> At this point, I would like to ask for your feedback as to what should
> be changed before these patches can be merged, even if merging these
> patches alone doesn't make a while lot of sense.  I will follow up
> with additional pieces to the puzzle like the nfsv4 support as I get
> them into shape again.

I remember my main concern being how we collapse the ACL and mask bits
to map a richacl to an NFSv4 (or Samba) ACL.  I can't remember what the
compromise there ended up being.  I guess I'll watch for that when it
comes.

--b.
--
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/