TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

An Evil Copy: How the Loader Betrays You [pdf]

2 点作者 secure超过 8 年前

1 comment

CalChris超过 8 年前
TL;DR <i>when instantiating a process, constant external variables that are referenced in executables are forcefully relocated to a writable memory segment without warning</i><p>So my first reaction was to add a check to see that my constants are in fact mapped read-only.<p><pre><code> const int constant_int = 42; </code></pre> It&#x27;d be nice to validate this read-only property and refuse to run but while <i>mprotect()</i> will set the memory protections there seems to be no associated getter. How do you check this in a reasonably portably manner?