<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Engineering Field Notes</title>
    <link>https://engineering-notes.anastratulat.dev/</link>
    <description>Practical research, experiments and lessons from software engineering.</description>
    <language>en</language>
    <atom:link href="https://engineering-notes.anastratulat.dev/feed.xml" rel="self" type="application/rss+xml"/>
    <lastBuildDate>Fri, 20 Nov 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>I added a JVM flag in Docker to mitigate the Java4Shell vulnerability. How do I test it?</title>
      <link>https://engineering-notes.anastratulat.dev/articles/verify-jvm-flag-docker-java4shell-jconsole/</link>
      <guid isPermaLink="true">https://engineering-notes.anastratulat.dev/articles/verify-jvm-flag-docker-java4shell-jconsole/</guid>
      <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
      <category>Engineering Tools</category>
      <description>How to use JConsole to verify that a JVM startup flag configured in Docker actually reached the running Java process, using the Java4Shell mitigation as an example.</description>
    </item>
    <item>
      <title>Java4Shell explained: how can Base64 corrupt the JVM?</title>
      <link>https://engineering-notes.anastratulat.dev/articles/java4shell-explained-base64-hotspot-jvm/</link>
      <guid isPermaLink="true">https://engineering-notes.anastratulat.dev/articles/java4shell-explained-base64-hotspot-jvm/</guid>
      <pubDate>Fri, 20 Nov 2026 00:00:00 GMT</pubDate>
      <category>Java Security</category>
      <description>A plain-English explanation of Java4Shell, HotSpot, the faulty Base64 intrinsic, the 62-byte overflow, and the JVM flag that disables the vulnerable fast path.</description>
    </item>
  </channel>
</rss>
