[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101129180429.GB14046@elte.hu>
Date: Mon, 29 Nov 2010 19:04:29 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Sarah Sharp <sarah.a.sharp@...ux.intel.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Marcus Meissner <meissner@...e.de>,
linux-kernel@...r.kernel.org, tj@...nel.org,
akpm@...ux-foundation.org, hpa@...or.com, w@....eu,
alan@...rguk.ukuu.org.uk
Subject: Re: [PATCH] kernel: make /proc/kallsyms mode 400 to reduce ease of
attacking
* Sarah Sharp <sarah.a.sharp@...ux.intel.com> wrote:
> On Fri, Nov 26, 2010 at 08:48:09AM +0100, Ingo Molnar wrote:
> >
> > * Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> >
> > > On Fri, Nov 19, 2010 at 11:19 AM, Sarah Sharp
> > > <sarah.a.sharp@...ux.intel.com> wrote:
> > > >
> > > > .config and dmesg are attached. The box is running klogd 1.5.5ubuntu3
> > > > (from Jaunty). Yes, I know that's old. I read the bit in the commit
> > > > about changing the permissions of kallsyms after boot, but if I can't
> > > > boot that doesn't help. Perhaps this can be made a configuration
> > > > option?
> > >
> > > It's not worth a config option.
> > >
> > > If it actually breaks user-space, I think we should just revert it.
> >
> > Sarah,
> >
> > Does your system boot fine if we make /proc/kallsyms simply an empty file to
> > unprivileged users? Something like the (untested ...) patch below.
>
> Yes, that works. The system boots as normal. `cat /proc/kallsyms`
> returns an empty file, and `sudo cat /proc/kallsyms` does not.
Great! Marcus, mind respinning your patch with that approach?
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists