<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Systematic Parsing of X.509: Eradicating Security Issues with a Parse Tree · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1812.04959/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1812.04959/feed.xml" rel="self" type="application/rss+xml" /><item><title>Systematic Parsing of X.509: Eradicating Security Issues with a Parse Tree — mentioned by tedunangst</title><link>https://news.ycombinator.com/item?id=25426033</link><guid isPermaLink="false">urn:hackerpapers:mention:1812.04959:25426033</guid><pubDate>Tue, 15 Dec 2020 01:42:35 GMT</pubDate><description>&lt;p&gt;Overshoot on my part. I was thinking of problems like those in https://arxiv.org/abs/1812.04959, but that&amp;#x27;s a different problem.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1812.04959/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item><item><title>Systematic Parsing of X.509: Eradicating Security Issues with a Parse Tree — HN submission</title><link>https://news.ycombinator.com/item?id=18695965</link><guid isPermaLink="false">urn:hackerpapers:submission:1812.04959:18695965</guid><pubDate>Sun, 16 Dec 2018 23:42:41 GMT</pubDate><description>&lt;p&gt;Systematic Parsing of X.509: Eradicating Security Issues with a Parse Tree&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;146 points; 25 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/1812.04959/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item></channel></rss>
