diff options
author | jhb <jhb@FreeBSD.org> | 2006-03-14 16:13:55 +0000 |
---|---|---|
committer | jhb <jhb@FreeBSD.org> | 2006-03-14 16:13:55 +0000 |
commit | aaa33da2edd23682521bc1bbbfa6ec1f33e6a9b6 (patch) | |
tree | 0e61856284edddd0e7369f6a41db457339ab7dc3 /lib/libc/stdlib/strtonum.3 | |
parent | baf4d3f4f12d3b17c7d2e9d7223d00263845e846 (diff) | |
download | FreeBSD-src-aaa33da2edd23682521bc1bbbfa6ec1f33e6a9b6.zip FreeBSD-src-aaa33da2edd23682521bc1bbbfa6ec1f33e6a9b6.tar.gz |
Don't allow userland to set hardware watch points on kernel memory at all.
Previously, we tried to allow this only for root. However, we were calling
suser() on the *target* process rather than the current process. This
means that if you can ptrace() a process running as root you can set a
hardware watch point in the kernel. In practice I think you probably have
to be root in order to pass the p_candebug() checks in ptrace() to attach
to a process running as root anyway. Rather than fix the suser(), I just
axed the entire idea, as I can't think of any good reason _at all_ for
userland to set hardware watch points for KVM.
MFC after: 3 days
Also thinks hardware watch points on KVM from userland are bad: bde, rwatson
Diffstat (limited to 'lib/libc/stdlib/strtonum.3')
0 files changed, 0 insertions, 0 deletions