<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Posts on A lazy blog</title><link>https://latedeployment.github.io/posts/</link><description>Recent content in Posts on A lazy blog</description><generator>Hugo -- 0.146.0</generator><language>en-us</language><lastBuildDate>Wed, 11 Mar 2026 12:00:00 +0200</lastBuildDate><atom:link href="https://latedeployment.github.io/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>oci2bin: Docker Images as Single Executables</title><link>https://latedeployment.github.io/posts/oci2bin-docker-images-as-executables/</link><pubDate>Wed, 11 Mar 2026 12:00:00 +0200</pubDate><guid>https://latedeployment.github.io/posts/oci2bin-docker-images-as-executables/</guid><description>&lt;h1 id="overview">Overview&lt;/h1>
&lt;p>&lt;a href="https://github.com/latedeployment/oci2bin">oci2bin&lt;/a> converts any Docker (OCI) container image into a single, self-contained executable. It doesn&amp;rsquo;t require any Docker daemon, no container runtime, and no installation on the target machine as the binary is static. Just copy the file over and run it.&lt;/p></description></item><item><title>Encrypting and Chunking Data in RSA Public Keys</title><link>https://latedeployment.github.io/posts/encrypting-and-chunking-data-in-rsa-keys/</link><pubDate>Thu, 29 Jan 2026 10:00:00 +0200</pubDate><guid>https://latedeployment.github.io/posts/encrypting-and-chunking-data-in-rsa-keys/</guid><description>&lt;p>&lt;em>This is part two of the RSA Public Key Manipulation series&lt;/em>.&lt;/p>
&lt;p>See also &lt;a href="https://latedeployment.github.io/posts/hiding-data-in-rsa-public-keys/">Part 1: How to Hide Data Inside RSA Public Keys&lt;/a>&lt;/p></description></item><item><title>How to Hide Data Inside RSA Public Keys</title><link>https://latedeployment.github.io/posts/hiding-data-in-rsa-public-keys/</link><pubDate>Thu, 29 Jan 2026 09:00:00 +0200</pubDate><guid>https://latedeployment.github.io/posts/hiding-data-in-rsa-public-keys/</guid><description>&lt;p>&lt;em>This is part one of the RSA Public Key Manipulation series&lt;/em>.&lt;/p>
&lt;p>See also &lt;a href="https://latedeployment.github.io/posts/encrypting-and-chunking-data-in-rsa-keys/">Part 2: Encrypting and Chunking Data in RSA Keys&lt;/a>&lt;/p></description></item><item><title>SBOM as Messaging System</title><link>https://latedeployment.github.io/posts/sbom-as-messaging-system/</link><pubDate>Wed, 28 Jan 2026 12:27:51 +0200</pubDate><guid>https://latedeployment.github.io/posts/sbom-as-messaging-system/</guid><description>&lt;p>&lt;em>This is part four of the Certificate Transparency series&lt;/em>.&lt;/p>
&lt;p>See also previous parts:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://latedeployment.github.io/posts/certificate-transparency-101/">Part 1: Certificate Transparency 101&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://latedeployment.github.io/posts/certificate-transparency-info-leaks/">Part 2: Certificate Transparency Info Leaks&lt;/a>&lt;/li>
&lt;li>&lt;a href="https://latedeployment.github.io/posts/certificate-transparency-as-communication-channel/">Part 3: Certificate Transparency as Communication Channel&lt;/a>&lt;/li>
&lt;/ul>
&lt;h1 id="introduction">Introduction&lt;/h1>
&lt;p>Described here is a way to leverage the infrastructure used to store SBOM (&lt;code>Software Bill of Materials&lt;/code>) certificates in order to distribute messages via the sigstore database.&lt;/p></description></item><item><title>Certificate Transparency as Communication Channel</title><link>https://latedeployment.github.io/posts/certificate-transparency-as-communication-channel/</link><pubDate>Sun, 25 Jan 2026 10:00:00 +0000</pubDate><guid>https://latedeployment.github.io/posts/certificate-transparency-as-communication-channel/</guid><description>&lt;p>&lt;em>This is part three of the Certificate Transparency series&lt;/em>.&lt;/p>
&lt;h1 id="introduction">Introduction&lt;/h1>
&lt;p>Described here is a way to leverage the infrastructure used to validate certificates in order to distribute messages through the Certificate Transparency Logs.&lt;/p></description></item><item><title>Certificate Transparency Info Leaks</title><link>https://latedeployment.github.io/posts/certificate-transparency-info-leaks/</link><pubDate>Mon, 19 Jan 2026 09:00:00 +0000</pubDate><guid>https://latedeployment.github.io/posts/certificate-transparency-info-leaks/</guid><description>&lt;p>&lt;em>This is part two of the Certificate Transparency series&lt;/em>.&lt;/p>
&lt;p>Crtificate Transparency logs are leaking valuable information about companies due to either unfamiliarity or obliviousness from companies&amp;rsquo; IT or DevOps teams.&lt;/p></description></item><item><title>Certificate Transparency 101</title><link>https://latedeployment.github.io/posts/certificate-transparency-101/</link><pubDate>Mon, 19 Jan 2026 08:00:00 +0000</pubDate><guid>https://latedeployment.github.io/posts/certificate-transparency-101/</guid><description>&lt;p>&lt;em>This is part one of the Certificate Transparency series&lt;/em>.&lt;/p>
&lt;p>Certificate Transparency (CT) is a public, append-only logging system for TLS
certificates. It was created to make certificate issuance observable so that
mis-issuance can be detected quickly and independently. Instead of relying
only on trust, CT lets anyone audit which certificates were issued
for a domain and when they appeared in a public log.&lt;/p></description></item><item><title>6 Things to Do With Docker</title><link>https://latedeployment.github.io/posts/6-things-to-do-with-docker/</link><pubDate>Tue, 12 Mar 2024 13:24:47 +0200</pubDate><guid>https://latedeployment.github.io/posts/6-things-to-do-with-docker/</guid><description>&lt;h2 id="1-operate-on-root-files-without-sudo-password">1. Operate on root files without sudo password&lt;/h2>
&lt;p>We all know that docker access &lt;strong>is basically root access&lt;/strong>, but examples are critical to understanding.&lt;/p></description></item><item><title>Thoughts on shell tools</title><link>https://latedeployment.github.io/posts/thought_on_tools/</link><pubDate>Wed, 07 Feb 2024 18:41:07 +0200</pubDate><guid>https://latedeployment.github.io/posts/thought_on_tools/</guid><description>&lt;p>Below a list of points I believe should be handled when writing shell tools.&lt;/p>
&lt;h1 id="exit-status">Exit Status&lt;/h1>
&lt;p>Exit status (&lt;code>exit(0)&lt;/code> or &lt;code>exit(1)&lt;/code>) is the way for letting the caller know the execution has failed.&lt;/p></description></item><item><title>Long Time Ago Refactoring Ideas</title><link>https://latedeployment.github.io/posts/refactoring/</link><pubDate>Wed, 07 Feb 2024 16:13:26 +0200</pubDate><guid>https://latedeployment.github.io/posts/refactoring/</guid><description>&lt;p>&lt;em>Refactoring ideas suggested long time ago from previous jobs&lt;/em>&lt;/p>
&lt;h1 id="libraries-are-too-tightly-coupled-with-each-other">Libraries are too tightly coupled with each other&lt;/h1>
&lt;p>Libraries should not depend on each other too much, otherwise you have to update all libraries which misses the entire idea of decoupling.&lt;/p></description></item><item><title>Linux User Time</title><link>https://latedeployment.github.io/posts/linux-user-time/</link><pubDate>Tue, 18 Apr 2017 19:50:53 +0200</pubDate><guid>https://latedeployment.github.io/posts/linux-user-time/</guid><description>&lt;p>Say we want to measure the number of &lt;strong>user space&lt;/strong> instructions a process is spending at a function. There are number of ways to do so: &lt;code>gettimeofday&lt;/code>, &lt;code>times&lt;/code>, &lt;code>clock&lt;/code> and &lt;code>getrusage&lt;/code>, but they give you time and not CPU cycles and not very accurate.&lt;/p></description></item><item><title>Old macOS kernel debugging with LLDB</title><link>https://latedeployment.github.io/posts/lldb_kernel_debug/</link><pubDate>Fri, 04 Nov 2016 15:36:58 +0200</pubDate><guid>https://latedeployment.github.io/posts/lldb_kernel_debug/</guid><description>&lt;p>&lt;strong>Note: This won&amp;rsquo;t work anymore, Apple has pretty much disabled any ability to work with kernel extensions. This is just an old blog post.&lt;/strong>
&lt;strong>Kext are no longer supported, use System Extensions and similar approach&lt;/strong>&lt;/p></description></item><item><title>Crashing Compilers</title><link>https://latedeployment.github.io/posts/crashing-compilers/</link><pubDate>Wed, 11 Nov 2015 19:51:04 +0200</pubDate><guid>https://latedeployment.github.io/posts/crashing-compilers/</guid><description>&lt;h1 id="the-compilers">The compilers&lt;/h1>
&lt;p>Let&amp;rsquo;s see if we can crash some compilers.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>python3 -c &lt;span style="color:#e6db74">&amp;#34;print(&amp;#39;{&amp;#39; * 99999)&amp;#34;&lt;/span> &amp;gt; test.c &lt;span style="color:#f92672">&amp;amp;&amp;amp;&lt;/span> clang test.c&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>
&lt;p>&lt;code>Clang&lt;/code> &lt;strong>SEGFAULT&lt;/strong> but &lt;code>GCC&lt;/code> has made it :)&lt;/p></description></item><item><title>Static Inline Mess</title><link>https://latedeployment.github.io/posts/static-inline-mess/</link><pubDate>Sat, 19 Sep 2015 19:50:58 +0200</pubDate><guid>https://latedeployment.github.io/posts/static-inline-mess/</guid><description>&lt;p>It&amp;rsquo;s a known fact (at least to me), that &lt;code>static inline&lt;/code> functions in C++ will generate multiple instances of a function if used in a different translation unit (a file, why call it differently?).&lt;/p></description></item><item><title>OSX kernel simple operations</title><link>https://latedeployment.github.io/posts/osx-simple-kernel-operations/</link><pubDate>Thu, 19 Feb 2015 19:50:33 +0200</pubDate><guid>https://latedeployment.github.io/posts/osx-simple-kernel-operations/</guid><description>&lt;h2 id="getting-current-information">Getting current information&lt;/h2>
&lt;p>Get current &lt;code>task&lt;/code> with:&lt;/p>
&lt;pre>&lt;code>#include &amp;lt;kern/task.h&amp;gt;
task_t cur_task = current_task();
&lt;/code>&lt;/pre>
&lt;p>Get current &lt;code>thread&lt;/code> with:&lt;/p></description></item><item><title>OSX IOKit sleep notification</title><link>https://latedeployment.github.io/posts/osx-iokit-sleep-notifications/</link><pubDate>Thu, 19 Feb 2015 19:50:21 +0200</pubDate><guid>https://latedeployment.github.io/posts/osx-iokit-sleep-notifications/</guid><description>&lt;h2 id="get-sleep-notification-in-your-iokit-kext">Get sleep notification in your IOKit kext&lt;/h2>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-cpp" data-lang="cpp">&lt;span style="display:flex;">&lt;span>IOReturn yourIOKitDriverClass&lt;span style="color:#f92672">::&lt;/span>powerStateHandler(&lt;span style="color:#66d9ef">void&lt;/span> &lt;span style="color:#f92672">*&lt;/span>target, &lt;span style="color:#66d9ef">void&lt;/span> &lt;span style="color:#f92672">*&lt;/span>refCon, UInt32 messageType, IOService &lt;span style="color:#f92672">*&lt;/span>service, &lt;span style="color:#66d9ef">void&lt;/span> &lt;span style="color:#f92672">*&lt;/span>messageArgs, vm_size_t argSize)
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>{
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> IOPMSystemCapabilityChangeParameters &lt;span style="color:#f92672">*&lt;/span> params;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#66d9ef">if&lt;/span> ( messageType &lt;span style="color:#f92672">!=&lt;/span> kIOMessageSystemCapabilityChange )
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> {
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#75715e">// We are not interested in anything other than cap change.
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e">&lt;/span> &lt;span style="color:#66d9ef">return&lt;/span> kIOReturnSuccess;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> }
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> params &lt;span style="color:#f92672">=&lt;/span> (IOPMSystemCapabilityChangeParameters &lt;span style="color:#f92672">*&lt;/span>) messageArgs;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#66d9ef">if&lt;/span> ((params&lt;span style="color:#f92672">-&amp;gt;&lt;/span>changeFlags &lt;span style="color:#f92672">&amp;amp;&lt;/span> kIOPMSystemCapabilityWillChange) &lt;span style="color:#f92672">&amp;amp;&amp;amp;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> (params&lt;span style="color:#f92672">-&amp;gt;&lt;/span>fromCapabilities &lt;span style="color:#f92672">&amp;amp;&lt;/span> kIOPMSystemCapabilityGraphics) &lt;span style="color:#f92672">&amp;amp;&amp;amp;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> (params&lt;span style="color:#f92672">-&amp;gt;&lt;/span>toCapabilities &lt;span style="color:#f92672">&amp;amp;&lt;/span> kIOPMSystemCapabilityGraphics) &lt;span style="color:#f92672">==&lt;/span> &lt;span style="color:#ae81ff">0&lt;/span>)
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> {
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#75715e">// caught a sleep
&lt;/span>&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#75715e">&lt;/span> }
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#66d9ef">return&lt;/span> kIOReturnSuccess;
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>}
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>&lt;span style="color:#66d9ef">bool&lt;/span> yourIOKitDriverClass&lt;span style="color:#f92672">::&lt;/span>start(IOService &lt;span style="color:#f92672">*&lt;/span>provider)
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>{
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> IOService &lt;span style="color:#f92672">*&lt;/span>rootDomain &lt;span style="color:#f92672">=&lt;/span> (IOService &lt;span style="color:#f92672">*&lt;/span>)getPMRootDomain();
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#66d9ef">if&lt;/span> (rootDomain)
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> rootDomain&lt;span style="color:#f92672">-&amp;gt;&lt;/span>registerInterestedDriver(&lt;span style="color:#66d9ef">this&lt;/span>);
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> registerPrioritySleepWakeInterest(powerStateHandler, &lt;span style="color:#66d9ef">this&lt;/span>, &lt;span style="color:#ae81ff">0&lt;/span>);
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>}&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>
&lt;p>Actually it&amp;rsquo;s not a sleep notification exactly but it&amp;rsquo;s good enough if you don&amp;rsquo;t need to handle power in your kext (and you probably don&amp;rsquo;t want to handle power in your kext)&lt;/p></description></item><item><title>OSX Firewire kernel debugging</title><link>https://latedeployment.github.io/posts/osx-firewire-debugging/</link><pubDate>Wed, 18 Feb 2015 16:13:26 +0200</pubDate><guid>https://latedeployment.github.io/posts/osx-firewire-debugging/</guid><description>&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>If you ever need to debug a newly (Yosemite) OSX kernel using firewire here is a small tutorial to help you through.&lt;/p></description></item></channel></rss>