From: Nick Kralevich <nnk@google.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Theodore Ts'o <tytso@mit.edu>, Laura Abbott <labbott@redhat.com>,
Kees Cook <keescook@chromium.org>,
Daniel Micay <danielmicay@gmail.com>,
kernel-hardening@lists.openwall.com,
lkml <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [kernel-hardening] Re: [PATCHv3 2/2] extract early boot entropy from the passed cmdline
Date: Wed, 30 Aug 2017 06:27:40 -0700 [thread overview]
Message-ID: <CAFJ0LnEduPL4RJLyJv-pZdrncfwS0r1mQ_26tKASDB4nf-Xjjw@mail.gmail.com> (raw)
In-Reply-To: <20170830095735.GB31503@amd>
On Wed, Aug 30, 2017 at 2:57 AM, Pavel Machek <pavel@ucw.cz> wrote:
> The command line is visible to unpriviledged userspace (/proc/cmdline,
> dmesg). Is that a problem?
These files are not exposed to untrusted processes on Android.
--
Nick Kralevich | Android Security | nnk@google.com | 650.214.4037
--
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>
prev parent reply other threads:[~2017-08-30 13:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 23:14 [PATCHv3 0/2] Command line randomness Laura Abbott
2017-08-16 23:14 ` [PATCHv3 1/2] init: Move stack canary initialization after setup_arch Laura Abbott
2017-08-16 23:14 ` [PATCHv3 2/2] extract early boot entropy from the passed cmdline Laura Abbott
2017-08-16 23:23 ` Kees Cook
2017-08-17 3:31 ` Theodore Ts'o
2017-08-17 4:23 ` Daniel Micay
2017-08-17 20:57 ` Daniel Micay
2017-08-17 21:44 ` Theodore Ts'o
2017-08-30 9:57 ` Pavel Machek
2017-08-30 13:27 ` Nick Kralevich [this message]
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=CAFJ0LnEduPL4RJLyJv-pZdrncfwS0r1mQ_26tKASDB4nf-Xjjw@mail.gmail.com \
--to=nnk@google.com \
--cc=akpm@linux-foundation.org \
--cc=danielmicay@gmail.com \
--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=pavel@ucw.cz \
--cc=tytso@mit.edu \
/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