<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[[Dr Brian R. Callahan]]]></title><description><![CDATA[<h2>(06/10)</h2>
<p dir="auto">⇒ A Final Return for OpenBSD Anti-Return-Oriented Programming Mitigations</p>
<blockquote>
<p dir="auto">Return-Oriented Programming (ROP) continues to be a serious attack taking advantage of flaws in memory unsafe languages, particularly buffer overflows, to launch arbitrary code execution attacks by chaining together pieces of already existing code in loaded binaries and shared libraries, called gadgets. With the continued reliance on x86_64 CPUs in cloud and personal servers, mitigations that can meaningfully reduce the success of ROP attacks without significant overhead continue to be attractive. We propose the porting of one such software-based anti-ROP mitigation proposed by OpenBSD: compile-time instruction rewriting to avoid opportunities for ROP exploitation. We bring this mitigation, originally developed for the custom OpenBSD implementation of the LLVM compiler suite, to GCC by way of a standalone utility that sits in between the compiler and the assembler and rewrites potential gadget instructions before assembly into object code. Our utility provides a minimal reduction in gadgets with some penalties in binary sizes and performance impacts. We compare our GCC-ported standalone utility to the original OpenBSD LLVM mitigation and discovered that our standalone utility is weaker compared to the original LLVM-based mitigation. However, due to the overall weak reduction in gadgets for both the LLVM-based and GCC-based implementations, we conclude that seemingly obvious mitigations may prove to be anything but, and caution providing security improvements without significant testing and evaluation.</p>
</blockquote>
<ul>
<li><a href="https://www.researchgate.net/publication/405728967_A_Final_Return_for_OpenBSD_Anti-Return-Oriented_Programming_Mitigations" rel="nofollow ugc">https://www.researchgate.net/publication/405728967_A_Final_Return_for_OpenBSD_Anti-Return-Oriented_Programming_Mitigations</a></li>
</ul>
<hr />
<p dir="auto"><em>ping: <a href="https://bsd.network/@bcallah/116725877009964245" rel="nofollow ugc">https://bsd.network/@bcallah/116725877009964245</a></em></p>
<hr />
<p dir="auto"><em>It seems to be my 200th post here</em>… <img src="https://billboard.bsd.cafe/assets/plugins/nodebb-plugin-emoji/emoji/android/1f609.png?v=11028b321f5" class="not-responsive emoji emoji-android emoji--wink" style="height:23px;width:auto;vertical-align:middle" title=";)" alt="😉" /></p>
]]></description><link>https://billboard.bsd.cafe/topic/236/dr-brian-r.-callahan</link><generator>RSS for Node</generator><lastBuildDate>Sun, 16 Aug 2026 01:53:23 GMT</lastBuildDate><atom:link href="https://billboard.bsd.cafe/topic/236.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 10 Jun 2026 14:43:10 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to [Dr Brian R. Callahan] on Wed, 12 Aug 2026 08:16:39 GMT]]></title><description><![CDATA[<h2>26/08/11</h2>
<p dir="auto">⇒ <strong>Cleaning costs, or, examining the OpenBSD -fret-clean flag</strong></p>
<blockquote>
<p dir="auto">I start with apologies to williewillus, calvin, and reezer on <a href="http://Lobste.rs" rel="nofollow ugc">Lobste.rs</a>. Prior to July 9, I would have agreed with you all. But it appears I was wrong. There is no need to further engage; it is clear that critique-from-within is undesirable. Which is perfectly OK, because I stepped away from being on the inside. So let's just keep evaluating OpenBSD's mitigations and we'll continue to learn interesting things along the way.</p>
</blockquote>
<ul>
<li><a href="https://briancallahan.net/blog/20260811.html" rel="nofollow ugc">https://briancallahan.net/blog/20260811.html</a></li>
</ul>
]]></description><link>https://billboard.bsd.cafe/post/941</link><guid isPermaLink="true">https://billboard.bsd.cafe/post/941</guid><dc:creator><![CDATA[CiotBSD]]></dc:creator><pubDate>Wed, 12 Aug 2026 08:16:39 GMT</pubDate></item></channel></rss>