All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dan Rosenberg <drosenberg@vsecurity.com>,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	kees.cook@canonical.com
Subject: Re: [PATCH v2] Restrict unprivileged access to kernel syslog
Date: Wed, 10 Nov 2010 19:10:00 +0100	[thread overview]
Message-ID: <20101110181000.GC22410@elte.hu> (raw)
In-Reply-To: <20101110072638.b0e5473d.akpm@linux-foundation.org>


* Andrew Morton <akpm@linux-foundation.org> wrote:

> OK by me, apart from ...
> 
> a) I'd question the need for the config option.  Are distros really
>    so lame that they can't trust themselves to poke a number into
>    procfs at boot time?

When it comes to security i personally prefer 'permanent' defaults that is a 
property of the booting image. I'd even change the default for the x86 defconfig for 
example - and we could make this option default-y in the future. (We cannot ever 
make the sysctl default itself default-1, it would break compatibility with old 
behavior.)

> b) we have "dmesg_restrict" and "CONFIG_RESTRICT_DMESG".  Less
>    dyslexia, please.

Good point. CONFIG_DMESG_RESTRICT is the proper hierarchical naming i suspect.

Thanks,

	Ingo

  parent reply	other threads:[~2010-11-10 18:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10  0:18 [PATCH v2] Restrict unprivileged access to kernel syslog Dan Rosenberg
2010-11-10  8:25 ` Ingo Molnar
2010-11-10 15:26   ` Andrew Morton
2010-11-10 17:50     ` Dave Jones
2010-11-10 18:13       ` Ingo Molnar
2010-11-10 18:10     ` Ingo Molnar [this message]
2010-11-10 16:32 ` Kees Cook

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=20101110181000.GC22410@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=drosenberg@vsecurity.com \
    --cc=kees.cook@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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.