[Bug server/30453] gdbserver cannot set breakpoints when /proc/pid/mem is not writable

["pedro at palves dot net" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=30453

--- Comment #20 from Pedro Alves <pedro at palves dot net> ---
Thanks, I've commented on the CrOS ticket.

> Eventually in 2011 the upstream kernel allowed writes to mem citing "there is no longer a security hazard" in commit [2], which was incorrect because CVEs and drama ensued [3], which apparently continues to this day.

So there was a CVE over a decade ago and it was fixed then.  Because there used
to be a bug, and it is now fixed, we should still consider allowing a debugger
to access memory using the interface bad?  That, doesn't compute to me.  Bugs
happen, and they are fixed.  There is nothing in the interface that prevents it
from being hardened, _and_ still allows debuggers to use it.

> I can't be the judge of what GDB supports or not, but perhaps if I get the kconfig 
> options to restring /proc/pid/mem upstreamed in the mainline kernel, that would help 
> settle the matter? :)

Sounds like blackmail.  :-P

-- 
You are receiving this mail because:
You are on the CC list for the bug.