From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: Harald Hoyer <harald@redhat.com>, initramfs@vger.kernel.org
Cc: linux-ima-user@lists.sourceforge.net,
systemd-devel@lists.freedesktop.org,
Stefan Berger <stefanb@us.ibm.com>
Subject: Re: [PATCH v2] 98integrity: Use /etc/ima as dir for IMA policy and config file
Date: Wed, 30 Nov 2016 11:03:48 -0500 [thread overview]
Message-ID: <b7241cd7-6cce-67d9-d48e-420fbc80dfc1@linux.vnet.ibm.com> (raw)
In-Reply-To: <a377c12b-6ece-804c-8aae-218b09e67590@redhat.com>
On 11/30/2016 10:52 AM, Harald Hoyer wrote:
> On 30.11.2016 16:24, Stefan Berger wrote:
>> On 11/30/2016 10:16 AM, Harald Hoyer wrote:
>>> On 30.11.2016 16:10, Stefan Berger wrote:
>>>> From: Stefan Berger <stefanb@us.ibm.com>
>>>>
>>>> To sync with systemd, use the filepath /etc/ima/ima-policy as
>>>> the file location for the IMA policy. At the same time we
>>>> move the ima config file location to /etc/ima/ima. Adapt the
>>>> documentation to the new path.
>>>>
>>>> Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
>>> One more thing: Do you want to be backwards compatible and also read the old files, if they exist?
>> I had thought about that and can certainly add it. Neither Fedora, RHEL, nor SUSE are packaging these files so far. So likely
>> there aren't many users out there. Considering that, what would you suggest?
>>
> Hmm, I'll add it to the dracut NEWS file
Let me send a v3 of the patch with backwards compatibility. I'll have it
look for the new location first, then fall back to the old files.
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
next prev parent reply other threads:[~2016-11-30 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 15:10 [PATCH v2] 98integrity: Use /etc/ima as dir for IMA policy and config file Stefan Berger
[not found] ` <1480518634-31897-1-git-send-email-stefanb-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2016-11-30 15:16 ` Harald Hoyer
[not found] ` <5526de6b-c774-f94b-30ce-065e03d28ce3-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-11-30 15:24 ` Stefan Berger
2016-11-30 15:52 ` Harald Hoyer
2016-11-30 16:03 ` Stefan Berger [this message]
2016-11-30 16:04 ` Dracut GitHub Import Bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b7241cd7-6cce-67d9-d48e-420fbc80dfc1@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=harald@redhat.com \
--cc=initramfs@vger.kernel.org \
--cc=linux-ima-user@lists.sourceforge.net \
--cc=stefanb@us.ibm.com \
--cc=systemd-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox