linux-kernel - Re: [Security] [PATCH] kernel: make /proc/kallsyms mode 400 to reduce ease of attacking

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 7 Nov 2010 12:27:09 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Willy Tarreau <w@....eu>
Cc:	Marcus Meissner <meissner@...e.de>, security@...nel.org,
	mort@....com, Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	fweisbec@...il.com, "H. Peter Anvin" <hpa@...or.com>,
	linux-kernel@...r.kernel.org, jason.wessel@...driver.com,
	tj@...nel.org, Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [Security] [PATCH] kernel: make /proc/kallsyms mode 400 to
 reduce ease of attacking


* Willy Tarreau <w@....eu> wrote:

> Hi Ingo,
> 
> On Sun, Nov 07, 2010 at 09:50:16AM +0100, Ingo Molnar wrote:
> > 
> > * Willy Tarreau <w@....eu> wrote:
> > 
> > > On Thu, Nov 04, 2010 at 10:51:57PM +0100, Ingo Molnar wrote:
> > > > > Quite honnestly, it's the worst idea I've ever read to protect the kernel. Kernel 
> > > > > version is needed at many places, when building some code which relies on presence 
> > > > > of syscall X or Y depending on a version, etc... [...]
> > > > 
> > > > Actually that's not true, since we have a kernel ABI, and since there's many 
> > > > backports of newer kernel features into older kernels that it's generally not
> > > > needed nor meaningful to know the kernel version for syscalls.
> > > > 
> > > > Returning -ENOSYS is the general standard we use to communicate syscall 
> > > > capabilities.
> > > > 
> > > > In fact using kernel version to switch around library functionality is a bug i'd 
> > > > argue.
> > > 
> > > I'm sorry Ingo, but I still don't agree. We've had several versions of epoll, 
> > > several (some even buggy) versions of splice() which cannot even be detected 
> > > without checking the kernel release. And those are just two that immediately come 
> > > to my mind. If we've been providing a version for the last 19 years, it surely had 
> > > some valid uses.
> > 
> > I'm sorry Willy, but you are mostly wrong - and there's no need to speculate here 
> > really. Just try the patch below :-)
> > 
> > If your claim that 'kernel version is needed at many places' is true then why am i 
> > seeing this on a pretty general distro box bootup:
> > 
> >  [root@...ebaran ~]# uname -a
> >  Linux aldebaran 2.6.99-tip-01574-g6ba54c9-dirty #1 SMP Sun Nov 7 10:24:38 CET 2010 x86_64 x86_64 x86_64 GNU/Linux
> 
> I don't understand the point you're trying to make with this patch. [...]

It was a simple experiement to support my rather simple argument which you disputed.

> [...] Obviously we can pretend to be any version, [...]

Ok, it's a pretty cavalier style of arguing that you now essentially turn around 
your earlier claim that the 'kernel version is needed at many places' and say what 
i've been saying, prefixed with 'obviously' ;-)

Yes, it's obvious that the kernel version is not needed for many functional purposes 
on a modern distro - and that was my exact point.

I cannot think of a single valid case where the proper user-space solution to some 
ABI compatibility detail is a kernel version check. I'd even argue that we want to 
keep unprivileged user-space from being able to implement such crappy version checks 
...

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/