Re: [PATCH] proc: maps protection
- From: Andy Isaacson <adi@xxxxxxxxxxxxx>
- Date: Fri, 9 Mar 2007 17:37:36 -0800
On Tue, Mar 06, 2007 at 08:22:11PM -0800, Arjan van de Ven wrote:
How about using a reduced check, as is done for fd and environ? This
would allow root-running system monitors to still do their job.
Effectively, this changes the test from "is ptracing" to just "can
If this still isn't considered safe, I'll add the maps_protect file...
btw I consider it an information leak that any user can see which
files/libraries any other user and root has mmap'd. (and with glibc's
stdio mmap feature that goes even beyond direct mmap to fopen()'d).
If root or some other user wants to watch
hillary-vs-obama-in-the-mud.avi, no other user has ANY business even
seeing that. So at minimum it's a privacy issue showing the filenames...
Sure, I would be fine with making /proc/<pid>/maps mode 0400 (so long as
root can still read it). But please don't take away my ability to debug
applications using pmap(1). It's so incredibly useful to be able to say
"ah, look, he mapped nss_nis.so rather than nss_nisplus.so".
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Prev by Date: Re: [PATCH 1/2] rcfs core patch
- Next by Date: Re: [PATCH] dvb-core: Fix several locking related problems.
- Previous by thread: Re: [PATCH] proc: maps protection
- Next by thread: [BUG] check_tsc_sync_source: using smp_processor_id() in preemptible code