<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Yet another #BitLocker &quot;exploit&quot; circulating.]]></title><description><![CDATA[<p>Yet another <a href="https://infosec.exchange/tags/BitLocker" rel="tag">#<span>BitLocker</span></a> "exploit" circulating.</p><p>This is a friendly reminder that if you set your system to just unlock with TPM alone, the system is not protected against determined attacker. BitLocker with TPM cannot protect your system unless if you configure the system to request PIN as well.</p><p>See: <a href="https://learn.microsoft.com/en-us/windows/security/operating-system-security/data-protection/bitlocker/countermeasures" rel="nofollow noopener"><span>https://</span><span>learn.microsoft.com/en-us/wind</span><span>ows/security/operating-system-security/data-protection/bitlocker/countermeasures</span></a></p><p><a href="https://infosec.exchange/tags/infosec" rel="tag">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/cybersecurity" rel="tag">#<span>cybersecurity</span></a></p>]]></description><link>https://board.circlewithadot.net/topic/3a26c1b2-6bf0-43b7-9f17-29614924d337/yet-another-bitlocker-exploit-circulating.</link><generator>RSS for Node</generator><lastBuildDate>Thu, 14 May 2026 23:35:40 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/3a26c1b2-6bf0-43b7-9f17-29614924d337.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 13 May 2026 11:07:56 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Yet another #BitLocker &quot;exploit&quot; circulating. on Wed, 13 May 2026 11:35:31 GMT]]></title><description><![CDATA[<p><span><a href="/user/gabrielesvelto%40mas.to">@<span>gabrielesvelto</span></a></span> Any solution that unlocks the encryption automatically without user having to provide "something you know" (*) is vulnerable to attacks by definition.</p><p>*) "something you have" may be good enough, for example some token or USB key. In this case you need to accept the risk of the attacker gaining access to the token, however.</p>]]></description><link>https://board.circlewithadot.net/post/https://infosec.exchange/users/harrysintonen/statuses/116567056811628615</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://infosec.exchange/users/harrysintonen/statuses/116567056811628615</guid><dc:creator><![CDATA[harrysintonen@infosec.exchange]]></dc:creator><pubDate>Wed, 13 May 2026 11:35:31 GMT</pubDate></item><item><title><![CDATA[Reply to Yet another #BitLocker &quot;exploit&quot; circulating. on Wed, 13 May 2026 11:21:24 GMT]]></title><description><![CDATA[<p><span><a href="/user/harrysintonen%40infosec.exchange">@<span>harrysintonen</span></a></span> if you need a pre-boot PIN to make BitLocker work, wouldn't using hardware full disk encryption just be a better option? If I have to input a password or PIN at boot I'd rather use what the hardware already provides rather than Microsoft's implementation.</p>]]></description><link>https://board.circlewithadot.net/post/https://mas.to/users/gabrielesvelto/statuses/116567001327542847</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mas.to/users/gabrielesvelto/statuses/116567001327542847</guid><dc:creator><![CDATA[gabrielesvelto@mas.to]]></dc:creator><pubDate>Wed, 13 May 2026 11:21:24 GMT</pubDate></item></channel></rss>