Johan Hovold <[email protected]> writes: > Fix a '/dev/kmsg' reference which got replaced with '/proc/kmsg' (which > is not accessible to regular users). > > Fixes: a03ef333fbd6 ("Documentation: security-bugs: explain what is and is > not a security bug") > Signed-off-by: Johan Hovold <[email protected]> > --- > Documentation/process/threat-model.rst | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/process/threat-model.rst > b/Documentation/process/threat-model.rst > index a68be888ce8e..04e5df6a6f78 100644 > --- a/Documentation/process/threat-model.rst > +++ b/Documentation/process/threat-model.rst > @@ -84,7 +84,7 @@ possibilities of user namespaces are not covered in this > document. > The kernel also offers a lot of troubleshooting and debugging facilities, > which > can constitute attack vectors when placed in wrong hands. While some of them > are designed to be accessible to regular local users with a low risk (e.g. > -kernel logs via ``/proc/kmsg``), some would expose enough information to > +kernel logs via ``/dev/kmsg``), some would expose enough information to > represent a risk in most places and the decision to expose them is under the
Applied, thanks. jon
