* Re: what happened to SECURITY_DAC? [not found] <ba89a02a-5550-689f-6609-1e8c025f5b91@infradead.org> @ 2019-03-21 16:36 ` Kees Cook 0 siblings, 0 replies; only message in thread From: Kees Cook @ 2019-03-21 16:36 UTC (permalink / raw) To: Randy Dunlap; +Cc: LKML, linux-security-module On Wed, Mar 20, 2019 at 5:39 PM Randy Dunlap <rdunlap@infradead.org> wrote: > > wow. Commit 70b62c25665f636c9f6c700b26af7df296b0887e > from last Sept. 14, 2018, total commit description says: > > LoadPin: Initialize as ordered LSM > > This converts LoadPin from being a direct "minor" LSM into an ordered LSM. > > Nowhere does it say anything like "this also deletes any notions of > DEFAULT_SECURITY and DAC." This was a mistaken merge of chunks from a larger series that Casey and I were working on. It should have been split out. > Was this deletion a (sekrit) security issue that was not being highlighted on purpose? No, just an error while refactoring to in creating CONFIG_LSM. > and what do you recommend for simple DAC-like security? See CONFIG_LSM. There are some related issues getting discussed here, too: https://lore.kernel.org/linux-security-module/f23d0fad-dc72-0e53-cac6-31abfd12a050@I-love.SAKURA.ne.jp/ -- Kees Cook ^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-03-21 16:36 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <ba89a02a-5550-689f-6609-1e8c025f5b91@infradead.org>
2019-03-21 16:36 ` what happened to SECURITY_DAC? Kees Cook
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).