From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 90F84C10F00 for ; Thu, 21 Mar 2019 16:36:28 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 62C57218E2 for ; Thu, 21 Mar 2019 16:36:28 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="iuX4F0h+" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728586AbfCUQgZ (ORCPT ); Thu, 21 Mar 2019 12:36:25 -0400 Received: from mail-vk1-f195.google.com ([209.85.221.195]:34191 "EHLO mail-vk1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727922AbfCUQgZ (ORCPT ); Thu, 21 Mar 2019 12:36:25 -0400 Received: by mail-vk1-f195.google.com with SMTP id k64so1501448vke.1 for ; Thu, 21 Mar 2019 09:36:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kdcQTlIAINGPVpPkA6d3wrWVhVTfoib9Yhk+JeGxrB4=; b=iuX4F0h+7qHBvHmEtwtWnWuuVjqJ6L3uyzNWcanZIHrie0GU5HEpnrcrLDgcDhRp9V uKez1XkoJ9YJrrY0pbbCbNY27YdntuK7OLaiuWn/acYbjtksiLYQ3hcQ3tR9I/aEHOpO ctWoQV0umPUr9+XC57B07nXotO9JJrbMJoYJU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kdcQTlIAINGPVpPkA6d3wrWVhVTfoib9Yhk+JeGxrB4=; b=sNCMcKddndCD6xaLtf6zTFeS9+ubwDmmuzCZF6aEJSwuAtS6eb1093TcDbzp9N+lcx oSfhlVgspc2zK0dC9jtyQSv4KhdIbHw7dWAgBb73MX4RaViLu4IcWCqRTkROvUTkYu9N mReya9QMYi3O0N/4bwZGMrTnx9Pikr5kwqJ8MY938Q2Kgf79qJHPjuPbN/ZwHlOjgV3j X06fBLhMxsEjEfUbBTj7VUu+BeN1GiHsZE68HQu/CRspWMMflN9o5Si1cRnKHAEq3dDA rb+bs5yPtSp1q+VsVpgm4zzg9SqPNOzIkOm4mqcsA96XSW6EcKVQSAp3jgnDJCpgwT8i AM4Q== X-Gm-Message-State: APjAAAU3evrkfjD9tiyNmmk+XyWOoIpDrP87t3BPhz+8m/xc3lvwJua/ hSJsUk6CBRQJ7YzMxfhX5m0/+/npZnphOw== X-Google-Smtp-Source: APXvYqzP1itSVS4SaxLaxn2cWNtX/3ZrTsTlG5HoY/V8aC6W4KOGzpJVLld0dMoIKmod2PQ7jFonkw== X-Received: by 2002:a1f:2ccb:: with SMTP id s194mr2812855vks.20.1553186182925; Thu, 21 Mar 2019 09:36:22 -0700 (PDT) Received: from mail-vs1-f47.google.com (mail-vs1-f47.google.com. [209.85.217.47]) by smtp.gmail.com with ESMTPSA id c129sm3343456vka.6.2019.03.21.09.36.21 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Mar 2019 09:36:22 -0700 (PDT) Received: by mail-vs1-f47.google.com with SMTP id i207so4043696vsd.10 for ; Thu, 21 Mar 2019 09:36:21 -0700 (PDT) X-Received: by 2002:a67:fa94:: with SMTP id f20mr2623709vsq.172.1553186181626; Thu, 21 Mar 2019 09:36:21 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kees Cook Date: Thu, 21 Mar 2019 09:36:09 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: what happened to SECURITY_DAC? To: Randy Dunlap Cc: LKML , linux-security-module Content-Type: text/plain; charset="UTF-8" Sender: owner-linux-security-module@vger.kernel.org Precedence: bulk List-ID: On Wed, Mar 20, 2019 at 5:39 PM Randy Dunlap 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