<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on fuldeka's homepage</title><link>https://fuldeka.github.io/blog/</link><description>Recent content in Blog on fuldeka's homepage</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 05 Sep 2026 11:40:00 +0200</lastBuildDate><atom:link href="https://fuldeka.github.io/blog/atom.xml" rel="self" type="application/rss+xml"/><item><title>TPM2+PIN Encryption Schemes: Evaluating and Enhancing Security</title><link>https://fuldeka.github.io/blog/tpm2-pin-encryption-schemes-evaluating-and-enhancing-security/</link><pubDate>Sat, 05 Sep 2026 11:40:00 +0200</pubDate><guid>https://fuldeka.github.io/blog/tpm2-pin-encryption-schemes-evaluating-and-enhancing-security/</guid><description>&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; Analyzing vulnerabilities in TPM2+PIN schemes and walking through an &lt;a href="https://github.com/systemd/systemd/pull/41859"&gt;implementation&lt;/a&gt; for &lt;code&gt;systemd-cryptenroll&lt;/code&gt;, ensuring a security profile that is &lt;strong&gt;no less robust than&lt;/strong&gt; traditional password-based schemes.&lt;/p&gt;&#10;&lt;h2 id="why-tpm-based-encryption"&gt;Why TPM-based encryption?&lt;/h2&gt;&#10;&lt;p&gt;Encrypted disks are usually protected with passwords or passphrases. Assuming a &lt;strong&gt;truly random&lt;/strong&gt; password of &lt;strong&gt;sufficient length&lt;/strong&gt; is used and stretched by the encryption software, using a memory-hard &lt;a href="https://en.wikipedia.org/wiki/Key_derivation_function"&gt;KDF&lt;/a&gt; like &lt;a href="https://en.wikipedia.org/wiki/Argon2"&gt;Argon2&lt;/a&gt;, chances of anyone successfully performing a brute-force attack are virtually hopeless under most circumstances. Unfortunately, humans are poor at generating randomness, and because passwords created by humans are never as clever as they seem, most passwords end up being weak.&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;</description></item></channel></rss>