<html style="direction: ltr;">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<style type="text/css">body p { margin-bottom: 0cm; margin-top: 0pt; } </style>
</head>
<body bidimailui-charset-is-forced="true" style="direction: ltr;"
text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 12/01/2019 15:19, Lev Olshvang
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:589971547299140@myt5-f9d71769b752.qloud-c.yandex.net">
<pre class="moz-quote-pre" wrap="">Hi All,
The fact that the text segment could be modified is bad news from the security standpoint.
For example, in order to set a breakpoint GDB should map a text segment with MAP_PRIVATE flag which allows kernel to ignore the dirty bit that MMU sets on this page.
Somewhere in the middle of this mapping, perhaps in mprotect, permission bits of page's PTE entry are modified as well from their original RO+X to RWX
I am not sure whether it is actually happening, perhaps instead new pages are allocated, sort of COW (copy on write).
And here I am getting to the point :
Is there any way to disable the change of permission bits of PTE? Is it possible in the hardware (ARM) or should kernel be patched?
Regards to All,
Happy new year.
Lev.
</pre>
</blockquote>
<p>I am 86.3%<sup>1</sup> certain that this change will not bring
about what you want this change to do. For example, if protecting
against ptrace is what you're after, please note that fakeroot-ng
completely changes what a process is running without making any
changes to the text segment at all.</p>
<p><br>
</p>
<p>Anyways, it is not the kernel that maps the text segment into
memory using private mapping. It is the dynamic linker. If you
need to change that to shared mapping, change the dynamic linker.</p>
<p><br>
</p>
<p>Shachar</p>
<p><br>
</p>
<p>1- Following the 80% rule, which states that 92.7% of statistics
people quote are made up on the spot.<br>
</p>
</body>
</html>