hc
2023-12-08 01573e231f18eb2d99162747186f59511f56b64d
kernel/Documentation/admin-guide/LSM/Yama.rst
....@@ -19,9 +19,10 @@
1919 etc) to extract additional credentials and continue to expand the scope
2020 of their attack without resorting to user-assisted phishing.
2121
22
-This is not a theoretical problem. SSH session hijacking
23
-(http://www.storm.net.nz/projects/7) and arbitrary code injection
24
-(http://c-skills.blogspot.com/2007/05/injectso.html) attacks already
22
+This is not a theoretical problem. `SSH session hijacking
23
+<https://www.blackhat.com/presentations/bh-usa-05/bh-us-05-boileau.pdf>`_
24
+and `arbitrary code injection
25
+<https://c-skills.blogspot.com/2007/05/injectso.html>`_ attacks already
2526 exist and remain possible if ptrace is allowed to operate as before.
2627 Since ptrace is not commonly used by non-developers and non-admins, system
2728 builders should be allowed the option to disable this debugging system.
....@@ -64,8 +65,8 @@
6465 Using ``PTRACE_TRACEME`` is unchanged.
6566
6667 2 - admin-only attach:
67
- only processes with ``CAP_SYS_PTRACE`` may use ptrace
68
- with ``PTRACE_ATTACH``, or through children calling ``PTRACE_TRACEME``.
68
+ only processes with ``CAP_SYS_PTRACE`` may use ptrace, either with
69
+ ``PTRACE_ATTACH`` or through children calling ``PTRACE_TRACEME``.
6970
7071 3 - no attach:
7172 no processes may use ptrace with ``PTRACE_ATTACH`` nor via