<story><title>Saltpack – A modern crypto messaging format</title><url>https://saltpack.org/</url></story><parent_chain></parent_chain><comment><author>jnwatson</author><text>This is classic young-person-fails-to-understand-venerable-standard-so-he-reimplements-half-of-it.&lt;p&gt;Messagepack is schemaless and noncanonical.  What that means is that a lot of the bounds&amp;#x2F;field checking is pushed up to the application layer.  I wouldn&amp;#x27;t encode crypto with that (and I love Messagepack).&lt;p&gt;All the hate for ASN.1, yet it is among the most battle-tested specifications out there.  Blaming ASN.1 for the shitty ASN.1 parsers written in the 80&amp;#x27;s and 90&amp;#x27;s is like blaming libsocket for all the network attacks.</text></comment>
<story><title>Saltpack – A modern crypto messaging format</title><url>https://saltpack.org/</url></story><parent_chain></parent_chain><comment><author>floatboth</author><text>MessagePack should be replaced with &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;cbor.io&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;cbor.io&lt;/a&gt; everywhere, as CBOR is an actual IETF RFC. Even if that kills the naming pun opportunity.</text></comment>