<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Asn1 on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/asn1/</link>
    <description>Recent content in Asn1 on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 10 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/asn1/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>ASN.1 Codec Libraries in 2026: asn1c vs rasn vs asn1tools vs ASN1js Compared</title>
      <link>https://www.pistack.xyz/posts/2026-10-10-asn1-codec-libraries-asn1c-rasn-asn1tools-asn1js-comparison/</link>
      <pubDate>Sat, 10 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-10-asn1-codec-libraries-asn1c-rasn-asn1tools-asn1js-comparison/</guid>
      <description>&lt;p&gt;Your TLS certificate, your LDAP bind request, your SNMP trap, and the signaling messages inside a 5G core are all encoded in the same thing: &lt;strong&gt;ASN.1&lt;/strong&gt;, a data description language from 1984 that refuses to die because nothing else encodes a schema into a predictable, standards-locked byte stream. If you write tooling that touches certificates, PKI, telecom stacks, or industrial protocols, you will eventually need an ASN.1 codec — and picking the wrong one costs you weeks.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
