<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: asdfxkcd</title><link>https://news.ycombinator.com/user?id=asdfxkcd</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Tue, 28 Jul 2026 23:22:30 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=asdfxkcd" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by asdfxkcd in "US citizen charged after GrapheneOS phone wipes during airport search"]]></title><description><![CDATA[
<p>Maybe also shows that the duress PIN feature could be implemented better. Booting into a completely fresh phone is suspicious. There also shouldn't be any visual or other indicators of that happening.<p>In the old TrueCrypt containers you could set an optional second password that would decrypt a different volume. The size of the container file was always the same, a decrypted volume always showed the full container size, the portion not occupied by the data in the main volume was filled with noise, and the data on the non-loaded volume was not protected (so you could erase it without warning by storing too much on the loaded volume), making it practically impossible to prove the existence of a second volume either way in a search situation. I guess there was a reason why the project was stopped.</p>
]]></description><pubDate>Mon, 27 Jul 2026 03:43:00 +0000</pubDate><link>https://news.ycombinator.com/item?id=49064970</link><dc:creator>asdfxkcd</dc:creator><comments>https://news.ycombinator.com/item?id=49064970</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49064970</guid></item></channel></rss>