From: Vivek Goyal <vgoyal@redhat.com>
To: "Kasatkin, Dmitry" <dmitry.kasatkin@intel.com>
Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ima: Support appraise_type=imasig_optional
Date: Wed, 13 Feb 2013 09:38:07 -0500 [thread overview]
Message-ID: <20130213143807.GC3540@redhat.com> (raw)
In-Reply-To: <CALLzPKbj33dQ36tcwip_LKCOXgA6GcBDbSc5s4y4cYyv2=s=nw@mail.gmail.com>
On Wed, Feb 13, 2013 at 03:36:45PM +0200, Kasatkin, Dmitry wrote:
> It should not be the only line in the policy.
> Can you share full policy?
I verified by putting some printk. There is only single rule in
ima_policy_rules list after I have updated the rules through "policy"
file.
echo "appraise fowner=0 func=BPRM_CHECK appraise_type=imasig_optional" >
/sys/kernel/security/policy
Thanks
Vivek
next prev parent reply other threads:[~2013-02-13 14:38 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 20:11 [RFC PATCH 0/2] ima: Support a mode to appraise signed files only Vivek Goyal
2013-02-11 20:11 ` [PATCH 1/2] ima: Do not try to fix hash if file system does not support security xattr Vivek Goyal
2013-02-12 11:45 ` Mimi Zohar
2013-02-12 14:27 ` Vivek Goyal
2013-02-11 20:11 ` [PATCH 2/2] ima: Support appraise_type=imasig_optional Vivek Goyal
2013-02-11 22:10 ` Mimi Zohar
2013-02-12 14:26 ` Vivek Goyal
2013-02-12 17:14 ` Mimi Zohar
2013-02-12 18:52 ` Vivek Goyal
2013-02-12 18:57 ` Vivek Goyal
2013-02-13 12:14 ` Kasatkin, Dmitry
2013-02-13 13:29 ` Vivek Goyal
2013-02-13 13:36 ` Kasatkin, Dmitry
2013-02-13 13:49 ` Vivek Goyal
2013-02-13 14:03 ` Mimi Zohar
2013-02-13 14:38 ` Vivek Goyal [this message]
2013-02-13 15:26 ` Kasatkin, Dmitry
2013-02-13 15:29 ` Kasatkin, Dmitry
2013-02-13 15:39 ` Vivek Goyal
2013-02-13 15:30 ` Vivek Goyal
2013-02-13 22:27 ` Mimi Zohar
2013-02-14 15:03 ` Vivek Goyal
2013-02-14 15:30 ` Mimi Zohar
2013-02-18 18:21 ` Vivek Goyal
2013-02-19 21:54 ` Mimi Zohar
2013-02-13 15:51 ` Mimi Zohar
2013-02-12 20:05 ` Mimi Zohar
2013-02-13 12:31 ` Kasatkin, Dmitry
2013-02-13 12:56 ` Mimi Zohar
2013-02-13 13:13 ` Kasatkin, Dmitry
2013-02-13 13:44 ` Mimi Zohar
2013-02-13 16:59 ` Vivek Goyal
2013-02-14 12:57 ` Mimi Zohar
2013-02-14 15:23 ` Vivek Goyal
2013-02-14 15:35 ` Mimi Zohar
2013-02-14 16:17 ` Vivek Goyal
2013-02-14 16:31 ` Vivek Goyal
2013-02-14 19:49 ` Mimi Zohar
2013-02-14 20:54 ` Vivek Goyal
2013-02-14 20:57 ` Vivek Goyal
2013-02-14 21:54 ` Mimi Zohar
2013-02-13 17:33 ` Kasatkin, Dmitry
2013-02-13 17:51 ` Vivek Goyal
2013-02-13 18:20 ` Kasatkin, Dmitry
2013-02-13 21:45 ` Mimi Zohar
2013-02-14 14:40 ` Vivek Goyal
2013-02-14 15:48 ` Mimi Zohar
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=20130213143807.GC3540@redhat.com \
--to=vgoyal@redhat.com \
--cc=dmitry.kasatkin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=zohar@linux.vnet.ibm.com \
/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