fix date

Author: ryan nemeth

config.toml

@@ -100,11 +100,3 @@ name = "Tags"
 url = "/tags/"
 weight = 5
 
-# [module]
-#   [[module.imports]]
-#     path = "github.com/alex-shpak/hugo-book"
-#
-#   [[module.imports.mounts]]
-#     source = "themes/book/layouts"
-#     target = "layouts/notes"
-#

content/posts/2025-11-23-modify-machine-code.md

@@ -1,6 +1,6 @@
 ---
 title: "Modify Machine Code in Executables"
-date: '2025-11-26T16:01:00+00:00'
+date: '2025-11-23T16:01:00+00:00'
 author: Ryan
 layout: post
 draft: false

public/categories/assembly/index.xml

@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
+  <channel>
+    <title>Assembly on GeekyRyan</title>
+    <link>http://localhost:1313/categories/assembly/</link>
+    <description>Recent content in Assembly on GeekyRyan</description>
+    <generator>Hugo</generator>
+    <language>en</language>
+    <lastBuildDate>Sun, 23 Nov 2025 16:01:00 +0000</lastBuildDate>
+    <atom:link href="http://localhost:1313/categories/assembly/index.xml" rel="self" type="application/rss+xml" />
+    <item>
+      <title>Modify Machine Code in Executables</title>
+      <link>http://localhost:1313/posts/2025-11-23-modify-machine-code/</link>
+      <pubDate>Sun, 23 Nov 2025 16:01:00 +0000</pubDate>
+      <guid>http://localhost:1313/posts/2025-11-23-modify-machine-code/</guid>
+      <description>&lt;h1 id=&#34;modifying-machine-code-in-executables&#34;&gt;Modifying Machine Code in Executables&lt;/h1&gt;&#xA;&lt;p&gt;In this post, we’ll walk through a simple but fun reverse-engineering exercise: taking a compiled C program, locating the machine instructions responsible for printing characters, and modifying those bytes directly in the executable.&lt;/p&gt;&#xA;&lt;p&gt;This is a great way to build intuition around how compilers translate code, how functions map to assembly, and how tools like &lt;code&gt;objdump&lt;/code&gt; and &lt;code&gt;xxd&lt;/code&gt; help us inspect and patch binaries.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;the-source-program&#34;&gt;The Source Program&lt;/h2&gt;&#xA;&lt;p&gt;We’ll start with a minimal C program that prints &lt;code&gt;&amp;quot;ab\n&amp;quot;&lt;/code&gt;:&lt;/p&gt;</description>
+    </item>
+  </channel>
+</rss>

public/categories/containers/index.xml

@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
+  <channel>
+    <title>Containers on GeekyRyan</title>
+    <link>http://localhost:1313/categories/containers/</link>
+    <description>Recent content in Containers on GeekyRyan</description>
+    <generator>Hugo</generator>
+    <language>en</language>
+    <lastBuildDate>Wed, 25 Dec 2024 00:00:00 +0000</lastBuildDate>
+    <atom:link href="http://localhost:1313/categories/containers/index.xml" rel="self" type="application/rss+xml" />
+    <item>
+      <title>Linux Containers</title>
+      <link>http://localhost:1313/posts/2024-12-25-linux-containers/</link>
+      <pubDate>Wed, 25 Dec 2024 00:00:00 +0000</pubDate>
+      <guid>http://localhost:1313/posts/2024-12-25-linux-containers/</guid>
+      <description>&lt;h1 id=&#34;notes&#34;&gt;NOTES&lt;/h1&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Containers in Linux are implemented with various namespaces and cgroups.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h1 id=&#34;introduction&#34;&gt;Introduction&lt;/h1&gt;&#xA;&lt;p&gt;If you work in tech, it’s rare to have a day where you don’t think or read about containerization. Docker, Kubernetes, Mesos, OpenShift, containerd, Azure Kubernetes Service, Amazon Elastic Kubernetes Service—the list of terms and platforms sometimes feels endless.&lt;/p&gt;&#xA;&lt;p&gt;The reality is that nearly every major technology company relies on containers at scale. OpenAI, Google, Amazon, Netflix, and even large portions of Microsoft Azure run their infrastructure on container platforms (most notably Kubernetes). But what exactly is a “container”? We’re often told that a container is just a process running on a host system, wrapped in some clever isolation. That’s true at a very high level, but it misses the nuance. The inner workings of containers rely on powerful, low-level Linux kernel features that go far beyond a simple process.&lt;/p&gt;</description>
+    </item>
+  </channel>
+</rss>

public/categories/golang/index.xml

@@ -13,7 +13,7 @@
       <link>http://localhost:1313/posts/2025-11-02-go-mod-breaks-tests/</link>
       <pubDate>Sun, 02 Nov 2025 16:01:00 +0000</pubDate>
       <guid>http://localhost:1313/posts/2025-11-02-go-mod-breaks-tests/</guid>
-      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;If you’ve ever initialized a new Go project with &lt;code&gt;go mod init main&lt;/code&gt; and later tried to write tests for it, you may have seen this cryptic error:&lt;/p&gt;&#xA;&lt;h3&gt;&lt;/h3&gt;&#xA;&lt;p&gt;cannot import &amp;ldquo;main&amp;rdquo;&lt;/p&gt;&#xA;&lt;h3&gt;&lt;/h3&gt;&#xA;&lt;p&gt;At first glance, this doesn’t make much sense — after all, your code and tests are both in &lt;code&gt;package main&lt;/code&gt;. However, there’s a subtle interaction between how Go handles modules, packages, and test harnesses that causes this issue. Let’s walk through what’s actually happening.&lt;/p&gt;</description>
+      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;If you’ve ever initialized a new Go project with &lt;code&gt;go mod init main&lt;/code&gt; and later tried to write tests for it, you may have seen this cryptic error:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;cannot import &amp;#34;main&amp;#34;&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;At first glance, this doesn’t make much sense — after all, your code and tests are both in &lt;code&gt;package main&lt;/code&gt;. However, there’s a subtle interaction between how Go handles modules, packages, and test harnesses that causes this issue. Let’s walk through what’s actually happening.&lt;/p&gt;</description>
     </item>
     <item>
       <title>Detecting MIME Types in Go</title>

public/categories/index.xml

@@ -6,22 +6,43 @@
     <description>Recent content in Categories on GeekyRyan</description>
     <generator>Hugo</generator>
     <language>en</language>
-    <lastBuildDate>Sun, 02 Nov 2025 16:01:00 +0000</lastBuildDate>
+    <lastBuildDate>Sun, 23 Nov 2025 16:01:00 +0000</lastBuildDate>
     <atom:link href="http://localhost:1313/categories/index.xml" rel="self" type="application/rss+xml" />
     <item>
-      <title>Golang</title>
-      <link>http://localhost:1313/categories/golang/</link>
-      <pubDate>Sun, 02 Nov 2025 16:01:00 +0000</pubDate>
-      <guid>http://localhost:1313/categories/golang/</guid>
+      <title>Assembly</title>
+      <link>http://localhost:1313/categories/assembly/</link>
+      <pubDate>Sun, 23 Nov 2025 16:01:00 +0000</pubDate>
+      <guid>http://localhost:1313/categories/assembly/</guid>
       <description></description>
     </item>
     <item>
       <title>Programming</title>
       <link>http://localhost:1313/categories/programming/</link>
-      <pubDate>Sun, 02 Nov 2025 16:01:00 +0000</pubDate>
+      <pubDate>Sun, 23 Nov 2025 16:01:00 +0000</pubDate>
       <guid>http://localhost:1313/categories/programming/</guid>
       <description></description>
     </item>
+    <item>
+      <title>Reverse Engineering</title>
+      <link>http://localhost:1313/categories/reverse-engineering/</link>
+      <pubDate>Sun, 23 Nov 2025 16:01:00 +0000</pubDate>
+      <guid>http://localhost:1313/categories/reverse-engineering/</guid>
+      <description></description>
+    </item>
+    <item>
+      <title>Systems</title>
+      <link>http://localhost:1313/categories/systems/</link>
+      <pubDate>Sun, 23 Nov 2025 16:01:00 +0000</pubDate>
+      <guid>http://localhost:1313/categories/systems/</guid>
+      <description></description>
+    </item>
+    <item>
+      <title>Golang</title>
+      <link>http://localhost:1313/categories/golang/</link>
+      <pubDate>Sun, 02 Nov 2025 16:01:00 +0000</pubDate>
+      <guid>http://localhost:1313/categories/golang/</guid>
+      <description></description>
+    </item>
     <item>
       <title>TIL</title>
       <link>http://localhost:1313/categories/til/</link>

public/categories/programming/index.xml

@@ -6,14 +6,21 @@
     <description>Recent content in Programming on GeekyRyan</description>
     <generator>Hugo</generator>
     <language>en</language>
-    <lastBuildDate>Sun, 02 Nov 2025 16:01:00 +0000</lastBuildDate>
+    <lastBuildDate>Sun, 23 Nov 2025 16:01:00 +0000</lastBuildDate>
     <atom:link href="http://localhost:1313/categories/programming/index.xml" rel="self" type="application/rss+xml" />
+    <item>
+      <title>Modify Machine Code in Executables</title>
+      <link>http://localhost:1313/posts/2025-11-23-modify-machine-code/</link>
+      <pubDate>Sun, 23 Nov 2025 16:01:00 +0000</pubDate>
+      <guid>http://localhost:1313/posts/2025-11-23-modify-machine-code/</guid>
+      <description>&lt;h1 id=&#34;modifying-machine-code-in-executables&#34;&gt;Modifying Machine Code in Executables&lt;/h1&gt;&#xA;&lt;p&gt;In this post, we’ll walk through a simple but fun reverse-engineering exercise: taking a compiled C program, locating the machine instructions responsible for printing characters, and modifying those bytes directly in the executable.&lt;/p&gt;&#xA;&lt;p&gt;This is a great way to build intuition around how compilers translate code, how functions map to assembly, and how tools like &lt;code&gt;objdump&lt;/code&gt; and &lt;code&gt;xxd&lt;/code&gt; help us inspect and patch binaries.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;the-source-program&#34;&gt;The Source Program&lt;/h2&gt;&#xA;&lt;p&gt;We’ll start with a minimal C program that prints &lt;code&gt;&amp;quot;ab\n&amp;quot;&lt;/code&gt;:&lt;/p&gt;</description>
+    </item>
     <item>
       <title>Understanding Why “module main” Breaks Go Tests</title>
       <link>http://localhost:1313/posts/2025-11-02-go-mod-breaks-tests/</link>
       <pubDate>Sun, 02 Nov 2025 16:01:00 +0000</pubDate>
       <guid>http://localhost:1313/posts/2025-11-02-go-mod-breaks-tests/</guid>
-      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;If you’ve ever initialized a new Go project with &lt;code&gt;go mod init main&lt;/code&gt; and later tried to write tests for it, you may have seen this cryptic error:&lt;/p&gt;&#xA;&lt;h3&gt;&lt;/h3&gt;&#xA;&lt;p&gt;cannot import &amp;ldquo;main&amp;rdquo;&lt;/p&gt;&#xA;&lt;h3&gt;&lt;/h3&gt;&#xA;&lt;p&gt;At first glance, this doesn’t make much sense — after all, your code and tests are both in &lt;code&gt;package main&lt;/code&gt;. However, there’s a subtle interaction between how Go handles modules, packages, and test harnesses that causes this issue. Let’s walk through what’s actually happening.&lt;/p&gt;</description>
+      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;If you’ve ever initialized a new Go project with &lt;code&gt;go mod init main&lt;/code&gt; and later tried to write tests for it, you may have seen this cryptic error:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;cannot import &amp;#34;main&amp;#34;&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;At first glance, this doesn’t make much sense — after all, your code and tests are both in &lt;code&gt;package main&lt;/code&gt;. However, there’s a subtle interaction between how Go handles modules, packages, and test harnesses that causes this issue. Let’s walk through what’s actually happening.&lt;/p&gt;</description>
     </item>
   </channel>
 </rss>

public/categories/reverse-engineering/index.xml

@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
+  <channel>
+    <title>Reverse Engineering on GeekyRyan</title>
+    <link>http://localhost:1313/categories/reverse-engineering/</link>
+    <description>Recent content in Reverse Engineering on GeekyRyan</description>
+    <generator>Hugo</generator>
+    <language>en</language>
+    <lastBuildDate>Sun, 23 Nov 2025 16:01:00 +0000</lastBuildDate>
+    <atom:link href="http://localhost:1313/categories/reverse-engineering/index.xml" rel="self" type="application/rss+xml" />
+    <item>
+      <title>Modify Machine Code in Executables</title>
+      <link>http://localhost:1313/posts/2025-11-23-modify-machine-code/</link>
+      <pubDate>Sun, 23 Nov 2025 16:01:00 +0000</pubDate>
+      <guid>http://localhost:1313/posts/2025-11-23-modify-machine-code/</guid>
+      <description>&lt;h1 id=&#34;modifying-machine-code-in-executables&#34;&gt;Modifying Machine Code in Executables&lt;/h1&gt;&#xA;&lt;p&gt;In this post, we’ll walk through a simple but fun reverse-engineering exercise: taking a compiled C program, locating the machine instructions responsible for printing characters, and modifying those bytes directly in the executable.&lt;/p&gt;&#xA;&lt;p&gt;This is a great way to build intuition around how compilers translate code, how functions map to assembly, and how tools like &lt;code&gt;objdump&lt;/code&gt; and &lt;code&gt;xxd&lt;/code&gt; help us inspect and patch binaries.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;the-source-program&#34;&gt;The Source Program&lt;/h2&gt;&#xA;&lt;p&gt;We’ll start with a minimal C program that prints &lt;code&gt;&amp;quot;ab\n&amp;quot;&lt;/code&gt;:&lt;/p&gt;</description>
+    </item>
+  </channel>
+</rss>

public/categories/systems/index.xml

@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
+  <channel>
+    <title>Systems on GeekyRyan</title>
+    <link>http://localhost:1313/categories/systems/</link>
+    <description>Recent content in Systems on GeekyRyan</description>
+    <generator>Hugo</generator>
+    <language>en</language>
+    <lastBuildDate>Sun, 23 Nov 2025 16:01:00 +0000</lastBuildDate>
+    <atom:link href="http://localhost:1313/categories/systems/index.xml" rel="self" type="application/rss+xml" />
+    <item>
+      <title>Modify Machine Code in Executables</title>
+      <link>http://localhost:1313/posts/2025-11-23-modify-machine-code/</link>
+      <pubDate>Sun, 23 Nov 2025 16:01:00 +0000</pubDate>
+      <guid>http://localhost:1313/posts/2025-11-23-modify-machine-code/</guid>
+      <description>&lt;h1 id=&#34;modifying-machine-code-in-executables&#34;&gt;Modifying Machine Code in Executables&lt;/h1&gt;&#xA;&lt;p&gt;In this post, we’ll walk through a simple but fun reverse-engineering exercise: taking a compiled C program, locating the machine instructions responsible for printing characters, and modifying those bytes directly in the executable.&lt;/p&gt;&#xA;&lt;p&gt;This is a great way to build intuition around how compilers translate code, how functions map to assembly, and how tools like &lt;code&gt;objdump&lt;/code&gt; and &lt;code&gt;xxd&lt;/code&gt; help us inspect and patch binaries.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;the-source-program&#34;&gt;The Source Program&lt;/h2&gt;&#xA;&lt;p&gt;We’ll start with a minimal C program that prints &lt;code&gt;&amp;quot;ab\n&amp;quot;&lt;/code&gt;:&lt;/p&gt;</description>
+    </item>
+  </channel>
+</rss>

public/categories/terraform/index.xml

@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="utf-8" standalone="yes"?>
+<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
+  <channel>
+    <title>Terraform on GeekyRyan</title>
+    <link>http://localhost:1313/categories/terraform/</link>
+    <description>Recent content in Terraform on GeekyRyan</description>
+    <generator>Hugo</generator>
+    <language>en</language>
+    <lastBuildDate>Mon, 09 Jan 2023 00:00:00 +0000</lastBuildDate>
+    <atom:link href="http://localhost:1313/categories/terraform/index.xml" rel="self" type="application/rss+xml" />
+    <item>
+      <title>Deploy Azure Kubernetes Service with NAT Gateway using Terraform</title>
+      <link>http://localhost:1313/posts/2023-01-09-deploy-aks-with-nat-gateway-using-tf-copy/</link>
+      <pubDate>Mon, 09 Jan 2023 00:00:00 +0000</pubDate>
+      <guid>http://localhost:1313/posts/2023-01-09-deploy-aks-with-nat-gateway-using-tf-copy/</guid>
+      <description>&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Azure NAT Gateway is a fully managed highly resilient NAT (Network Address Translation) service provided by Microsoft. After creating a NAT Gateway and then associating it with a subnet, all devices in that subnet will automatically route outbound traffic through the gateway. This is because NAT Gateway takes precedence over other outbound routing methods and replaces the default Internet destination of a subnet. However, the presence of custom UDRs for virtual appliances and ExpressRoute override NAT gateway for directing internet bound traffic (route to the 0.0.0.0/0 address prefix).&lt;/p&gt;</description>
+    </item>
+  </channel>
+</rss>