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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Runtime Memory Patching on x86/x64

16 点作者 javinpaul超过 7 年前

1 comment

j_s超过 7 年前
Companies are popping up hoping to crowdsource temporary security patches:<p>patching a 0-day: Windows gdi32.dll memory disclosure | <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=13774397" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=13774397</a> (Mar 2017, 43 comments)<p>&gt;sst8: <i>Live patching is gaining the momentum - see Ksplice, Kpatch, kGraft, XEN and similar</i><p>&gt;dielel: <i>Our micropatch (7 of them, really, for 4 different Windows OS versions) for CVE-2017-0038 is user-mode. As are currently all our micropatches. Processes using gdi32.dll do not need to be relaunched to have it applied.</i><p>--<p>The list of hot-reloading alternatives was awesome; I sometimes wish I could &#x27;star&#x27; a single file like that README: <a href="https:&#x2F;&#x2F;github.com&#x2F;RuntimeCompiledCPlusPlus&#x2F;RuntimeCompiledCPlusPlus" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;RuntimeCompiledCPlusPlus&#x2F;RuntimeCompiledC...</a><p>This technique of manually NOP-ing out things at runtime is definitely beyond my usual approach of setting a breakpoint and then choosing where to continue execution manually!