Re: [PATCH] Enable writing to /proc/PID/mem.

[KOSAKI Motohiro]

> For a long time /proc/PID/mem has provided a read-only interface, at least since
> 2.4.0.  However, a write capability has existed "forever" in tree via the
> function mem_write, disabled with an #ifdef along with the comment "this is a
> security hazard".  Charles Wright, back in 2006, gave some history on the
> subject:
> 
>     http://lkml.org/lkml/2006/3/10/224
> 
> Later, in commit 638fa202c, Roland McGrath updated mem_write to call
> check_mem_permission which ensures an identical security policy for
> /proc/PID/mem as for ptrace().  IOW, the proc interface provides a simpler, more
> efficient, but otherwise equivalent mechanism for probing a processes memory as
> available via ptrace.
> 
> There is no longer a security hazard and the world can safely use read/write
> instead of ptrace PEEK/POKE's.  Remove the #ifdef.
> 
> Signed-off-by: Stephen Wilson <wilsons@xxxxxxxx>

I haven't found any problem in this patch. But, I really believe we need
to understand why it was marked "security hazard". Al, I guess you know it,
right? So, can you please talk us your mention?



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