public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	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 12:50:42 -0500	[thread overview]
Message-ID: <20101110175042.GB1923@redhat.com> (raw)
In-Reply-To: <20101110072638.b0e5473d.akpm@linux-foundation.org>

On Wed, Nov 10, 2010 at 07:26:38AM -0800, Andrew Morton wrote:
 
 > 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?

short answer: yes.

* /etc/sysctl.conf is for users to override decisions distros have made,
  rather than a catalog of those decisions.

* Sometimes we change our mind on those decisions. Flipping a config option
  in the kernel means we push out an update, and forget about it.
  Users /etc/sysctl.conf's contain all kinds of crazyness. ask Davem about
  the stale TCP 'tuning' crap that lingered for years in Fedora users configs
  before anyone noticed.
  (We could update the sysctl.conf at post-install of the kernel package,
   but if you've ever seen a distro kernel packaging schema, you'd understand
   why adding more magic like this isn't desirable)

There's a bunch of patches we carry in Fedora that change defaults because there's
no CONFIG option for them, which I've been meaning to get around to
hacking up into options so we can carry a few less patches.

	Dave


  reply	other threads:[~2010-11-10 17:51 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 [this message]
2010-11-10 18:13       ` Ingo Molnar
2010-11-10 18:10     ` Ingo Molnar
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=20101110175042.GB1923@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=drosenberg@vsecurity.com \
    --cc=kees.cook@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox