<?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>chs.us — Carl Sampson</title><link>https://chs.us/</link><description/><language>en-us</language><managingEditor>carl.sampson@gmail.com (Carl Sampson)</managingEditor><webMaster>carl.sampson@gmail.com (Carl Sampson)</webMaster><lastBuildDate>Wed, 01 Jul 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://chs.us/tags/jndi/index.xml" rel="self" type="application/rss+xml"/><item><title>Hand-rolling the JNDI Reference: what the JVM actually deserializes</title><link>https://chs.us/2026/07/jndi-reference-deserialization/</link><pubDate>Wed, 01 Jul 2026 12:00:00 +0000</pubDate><author>carl.sampson@gmail.com (Carl Sampson)</author><guid>https://chs.us/2026/07/jndi-reference-deserialization/</guid><description>How a Log4Shell-style LDAP/RMI callback returns a javax.naming.Reference, byte for byte — and two serialization bugs that only a real JVM catches.</description><category>Security</category><category>Java</category><category>Deserialization</category><category>Jndi</category><category>Log4shell</category><category>Rmi</category><category>Ldap</category><category>Websec</category></item></channel></rss>