From: Igor Stoppa <igor.stoppa@huawei.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: <keescook@chromium.org>, <mhocko@kernel.org>, <jmorris@namei.org>,
<penguin-kernel@I-love.SAKURA.ne.jp>, <paul@paul-moore.com>,
<sds@tycho.nsa.gov>, <casey@schaufler-ca.com>,
<labbott@redhat.com>, <linux-security-module@vger.kernel.org>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<kernel-hardening@lists.openwall.com>,
"Igor Stoppa" <igor.stoppa@gmail.com>
Subject: Re: [PATCH 3/3] Make LSM Writable Hooks a command line option
Date: Wed, 28 Jun 2017 11:25:37 +0300 [thread overview]
Message-ID: <bd570517-c05f-7f37-aba0-6e4c14938dfb@huawei.com> (raw)
In-Reply-To: <20170627175118.GA14286@infradead.org>
Resending my reply, I mistakenly used the wrong mail account yesterday
and my reply didn't et to the ml.
On 27/06/17 20:51, Christoph Hellwig wrote:
> On Tue, Jun 27, 2017 at 08:33:23PM +0300, Igor Stoppa wrote:
[...]
>> The default value is disabled, unless SE Linux debugging is turned on.
>
> Can we please just force it to be read-only?
I'm sorry, I'm not quite sure I understand your comment.
I'm trying to replicate the behavior of __lsm_ro_after_init:
line 1967 @ [1] - Did I get it wrong?
thanks, igor
[1]
https://kernel.googlesource.com/pub/scm/linux/kernel/git/jmorris/linux-security/+/5965453d5e3fb425e6f9d6b4fec403bda3f33107/include/linux/lsm_hooks.h
WARNING: multiple messages have this Message-ID (diff)
From: igor.stoppa@huawei.com (Igor Stoppa)
To: linux-security-module@vger.kernel.org
Subject: [PATCH 3/3] Make LSM Writable Hooks a command line option
Date: Wed, 28 Jun 2017 11:25:37 +0300 [thread overview]
Message-ID: <bd570517-c05f-7f37-aba0-6e4c14938dfb@huawei.com> (raw)
In-Reply-To: <20170627175118.GA14286@infradead.org>
Resending my reply, I mistakenly used the wrong mail account yesterday
and my reply didn't et to the ml.
On 27/06/17 20:51, Christoph Hellwig wrote:
> On Tue, Jun 27, 2017 at 08:33:23PM +0300, Igor Stoppa wrote:
[...]
>> The default value is disabled, unless SE Linux debugging is turned on.
>
> Can we please just force it to be read-only?
I'm sorry, I'm not quite sure I understand your comment.
I'm trying to replicate the behavior of __lsm_ro_after_init:
line 1967 @ [1] - Did I get it wrong?
thanks, igor
[1]
https://kernel.googlesource.com/pub/scm/linux/kernel/git/jmorris/linux-security/+/5965453d5e3fb425e6f9d6b4fec403bda3f33107/include/linux/lsm_hooks.h
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Igor Stoppa <igor.stoppa@huawei.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: keescook@chromium.org, mhocko@kernel.org, jmorris@namei.org,
penguin-kernel@I-love.SAKURA.ne.jp, paul@paul-moore.com,
sds@tycho.nsa.gov, casey@schaufler-ca.com, labbott@redhat.com,
linux-security-module@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com,
Igor Stoppa <igor.stoppa@gmail.com>
Subject: Re: [PATCH 3/3] Make LSM Writable Hooks a command line option
Date: Wed, 28 Jun 2017 11:25:37 +0300 [thread overview]
Message-ID: <bd570517-c05f-7f37-aba0-6e4c14938dfb@huawei.com> (raw)
In-Reply-To: <20170627175118.GA14286@infradead.org>
Resending my reply, I mistakenly used the wrong mail account yesterday
and my reply didn't et to the ml.
On 27/06/17 20:51, Christoph Hellwig wrote:
> On Tue, Jun 27, 2017 at 08:33:23PM +0300, Igor Stoppa wrote:
[...]
>> The default value is disabled, unless SE Linux debugging is turned on.
>
> Can we please just force it to be read-only?
I'm sorry, I'm not quite sure I understand your comment.
I'm trying to replicate the behavior of __lsm_ro_after_init:
line 1967 @ [1] - Did I get it wrong?
thanks, igor
[1]
https://kernel.googlesource.com/pub/scm/linux/kernel/git/jmorris/linux-security/+/5965453d5e3fb425e6f9d6b4fec403bda3f33107/include/linux/lsm_hooks.h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Igor Stoppa <igor.stoppa@huawei.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: keescook@chromium.org, mhocko@kernel.org, jmorris@namei.org,
penguin-kernel@I-love.SAKURA.ne.jp, paul@paul-moore.com,
sds@tycho.nsa.gov, casey@schaufler-ca.com, labbott@redhat.com,
linux-security-module@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com,
Igor Stoppa <igor.stoppa@gmail.com>
Subject: [kernel-hardening] Re: [PATCH 3/3] Make LSM Writable Hooks a command line option
Date: Wed, 28 Jun 2017 11:25:37 +0300 [thread overview]
Message-ID: <bd570517-c05f-7f37-aba0-6e4c14938dfb@huawei.com> (raw)
In-Reply-To: <20170627175118.GA14286@infradead.org>
Resending my reply, I mistakenly used the wrong mail account yesterday
and my reply didn't et to the ml.
On 27/06/17 20:51, Christoph Hellwig wrote:
> On Tue, Jun 27, 2017 at 08:33:23PM +0300, Igor Stoppa wrote:
[...]
>> The default value is disabled, unless SE Linux debugging is turned on.
>
> Can we please just force it to be read-only?
I'm sorry, I'm not quite sure I understand your comment.
I'm trying to replicate the behavior of __lsm_ro_after_init:
line 1967 @ [1] - Did I get it wrong?
thanks, igor
[1]
https://kernel.googlesource.com/pub/scm/linux/kernel/git/jmorris/linux-security/+/5965453d5e3fb425e6f9d6b4fec403bda3f33107/include/linux/lsm_hooks.h
next prev parent reply other threads:[~2017-06-28 8:29 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 17:33 [PATCH v8 0/3] mm: LSM: ro protection for dynamic data Igor Stoppa
2017-06-27 17:33 ` [kernel-hardening] " Igor Stoppa
2017-06-27 17:33 ` Igor Stoppa
2017-06-27 17:33 ` Igor Stoppa
2017-06-27 17:33 ` [PATCH 1/3] Protectable memory support Igor Stoppa
2017-06-27 17:33 ` [kernel-hardening] " Igor Stoppa
2017-06-27 17:33 ` Igor Stoppa
2017-06-27 17:33 ` Igor Stoppa
2017-06-27 17:33 ` [PATCH 2/3] LSM: Convert security_hook_heads into explicit array of struct list_head Igor Stoppa
2017-06-27 17:33 ` [kernel-hardening] " Igor Stoppa
2017-06-27 17:33 ` Igor Stoppa
2017-06-27 17:33 ` Igor Stoppa
2017-06-27 17:33 ` [PATCH 3/3] Make LSM Writable Hooks a command line option Igor Stoppa
2017-06-27 17:33 ` [kernel-hardening] " Igor Stoppa
2017-06-27 17:33 ` Igor Stoppa
2017-06-27 17:33 ` Igor Stoppa
2017-06-27 17:51 ` Christoph Hellwig
2017-06-27 17:51 ` [kernel-hardening] " Christoph Hellwig
2017-06-27 17:51 ` Christoph Hellwig
2017-06-27 17:51 ` Christoph Hellwig
2017-06-27 20:07 ` igor.stoppa
2017-06-27 20:07 ` [kernel-hardening] " igor.stoppa
2017-06-28 8:25 ` Igor Stoppa [this message]
2017-06-28 8:25 ` Igor Stoppa
2017-06-28 8:25 ` Igor Stoppa
2017-06-28 8:25 ` Igor Stoppa
-- strict thread matches above, loose matches on Subject: below --
2017-07-10 15:06 [PATCH v10 0/3] mm: security: ro protection for dynamic data Igor Stoppa
2017-07-10 15:06 ` [PATCH 3/3] Make LSM Writable Hooks a command line option Igor Stoppa
2017-07-10 15:06 ` Igor Stoppa
2017-07-10 15:06 ` Igor Stoppa
2017-07-11 4:12 ` kbuild test robot
2017-07-11 4:12 ` kbuild test robot
2017-07-11 4:12 ` kbuild test robot
2017-07-05 13:46 [PATCH v9 0/3] mm: security: ro protection for dynamic data Igor Stoppa
2017-07-05 13:46 ` [PATCH 3/3] Make LSM Writable Hooks a command line option Igor Stoppa
2017-07-05 13:46 ` Igor Stoppa
2017-07-05 13:46 ` Igor Stoppa
2017-06-26 14:41 [PATCH v7 0/3] ro protection for dynamic data Igor Stoppa
2017-06-26 14:41 ` [PATCH 3/3] Make LSM Writable Hooks a command line option Igor Stoppa
2017-06-26 14:41 ` Igor Stoppa
2017-06-26 14:41 ` Igor Stoppa
2017-06-27 5:07 ` kbuild test robot
2017-06-27 5:07 ` kbuild test robot
2017-06-27 5:07 ` kbuild test robot
2017-06-27 6:48 ` kbuild test robot
2017-06-27 6:48 ` kbuild test robot
2017-06-27 6:48 ` kbuild test robot
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=bd570517-c05f-7f37-aba0-6e4c14938dfb@huawei.com \
--to=igor.stoppa@huawei.com \
--cc=casey@schaufler-ca.com \
--cc=hch@infradead.org \
--cc=igor.stoppa@gmail.com \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=sds@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.