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=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS autolearn=ham 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 CDFCFC43381 for ; Mon, 4 Mar 2019 13:29:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 7ADE620661 for ; Mon, 4 Mar 2019 13:29:53 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=coker.com.au header.i=@coker.com.au header.b="dsRDd/jF" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726643AbfCDN3w (ORCPT ); Mon, 4 Mar 2019 08:29:52 -0500 Received: from smtp.sws.net.au ([46.4.88.250]:43506 "EHLO smtp.sws.net.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726186AbfCDN3w (ORCPT ); Mon, 4 Mar 2019 08:29:52 -0500 Received: from xev.coker.com.au (localhost [127.0.0.1]) by smtp.sws.net.au (Postfix) with ESMTP id 05ACCEB9B for ; Tue, 5 Mar 2019 00:29:49 +1100 (AEDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=coker.com.au; s=2008; t=1551706190; bh=gSUNdS5yjKpq1ElgnaOyIEN5dMw3C/dFLy1RJ7DMPdA=; l=881; h=From:To:Reply-To:Subject:Date:From; b=dsRDd/jFa7bsmwYG46l9IGnKwUWjyGxl7miEot40JHX3QH+GLp2UuGV529ltMPUw1 kd/jaIiD4cC11khVycYB7C8z8hsAUnfBexoq7iMuKJxylfWr92LvvqNl0G8vx2prG9 bZikuxIoxtIPJrHNdh/n62nJYQE9nkh4eF028Srk= Received: by xev.coker.com.au (Postfix, from userid 1001) id 460CFCD173A; Tue, 5 Mar 2019 00:29:45 +1100 (AEDT) From: Russell Coker To: "selinux-refpolicy@vger.kernel.org" Reply-To: russell@coker.com.au Subject: strange daemon startup issue Date: Tue, 05 Mar 2019 00:29:45 +1100 Message-ID: <3166760.egoGarHQ6g@xev> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: selinux-refpolicy-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: selinux-refpolicy@vger.kernel.org When I boot kernel 4.9.144 (Debian/Stable kernel) with the Debian policy for Unstable (which isn't very different to the latest Git refpolicy) /usr/sbin/ ModemManager and /usr/sbin/mysqld run as init_t. When I boot the same policy with kernel 4.19.16 (Debian/Testing kernel) those daemons run in modemmanager_t and mysqld_t as desired. What is the difference between those kernels which would explain this? Would it be some interaction with systemd? I don't expect anyone to just hand me the answer (although that would be really nice), any clues as to where I should start investigating this would be great. The general aim with Debian SE Linux is that you can run the policy with the kernel from the previous version of Debian. So this is something I really want to fix. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/