linux-kernel - Re: [PATCH] pipefs unique inode numbers

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]

Message-ID: <Pine.LNX.4.64.0701301454400.3611@woody.linux-foundation.org>
Date:	Tue, 30 Jan 2007 14:55:56 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Bodo Eggert <7eggert@....de>
cc:	akpm@...l.org, Jeff Layton <jlayton@...hat.com>, dev@...ru,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	torvalds@...l.org
Subject: Re: [PATCH] pipefs unique inode numbers



On Tue, 30 Jan 2007, Bodo Eggert wrote:
>
> change pipefs to use a unique inode number equal to the memory
> address unless it would be truncated.

I *really* wouldn't want to expose kernel addresses to user space, it just 
ends up being a piece of data that they shouldn't have. If we have some 
security issue, this is just too much kernel information that a bad user 
could get at.

		Linus
-
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/