<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>AdamStas.com - Home of Adam Stasiniewicz</title>
        <link>https://www.adamstas.com/</link>
        <description>Home of Adam Stasiniewicz</description>
        <generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 11 Nov 2025 21:20:15 &#43;0000</lastBuildDate>
            <atom:link href="https://www.adamstas.com/index.xml" rel="self" type="application/rss+xml" />
        <item>
    <title>Please Use DNSSEC</title>
    <link>https://www.adamstas.com/please-use-dnssec/</link>
    <pubDate>Tue, 11 Nov 2025 21:20:15 &#43;0000</pubDate><author>
        <name>Adam Stasiniewicz</name>
    </author><guid>https://www.adamstas.com/please-use-dnssec/</guid>
    <description><![CDATA[<p>The other day I was reading about <a href="https://arstechnica.com/security/2025/10/bind-warns-of-bugs-that-could-bring-dns-cache-attack-back-from-the-dead/" target="_blank" rel="noopener noreferrer">yet another DNS vulnerability</a>.  Vulnerabilities in DNS have been well known since <a href="https://www.kb.cert.org/vuls/id/800113" target="_blank" rel="noopener noreferrer">2008</a>, and since <a href="https://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions#Implementation" target="_blank" rel="noopener noreferrer">2010</a> we&rsquo;ve had an excellent solution, <a href="https://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions" target="_blank" rel="noopener noreferrer">DNSSEC</a>.  DNSSEC addresses many of the most common DNS vulnerabilities on the internet today (including this most recent vulnerability).  For most, setup is very simple.  Unfortunately, DNSSEC is an opt-in technology.  So, it&rsquo;s a good time to remind all my Internet friends that today&rsquo;s a good day to double-check if you have DNSSEC enabled, and if you don&rsquo;t, to make plans to enable it.</p>]]></description>
</item><item>
    <title>Infineon / YubiKey Cloning Vulnerability</title>
    <link>https://www.adamstas.com/infineon-yubikey-cloning-vulnerability/</link>
    <pubDate>Tue, 03 Sep 2024 21:25:21 -0700</pubDate><author>
        <name>Adam Stasiniewicz</name>
    </author><guid>https://www.adamstas.com/infineon-yubikey-cloning-vulnerability/</guid>
    <description><![CDATA[<p><em>Original <a href="https://arstechnica.com/security/2024/09/yubikeys-are-vulnerable-to-cloning-attacks-thanks-to-newly-discovered-side-channel/" target="_blank" rel="noopener noreferrer">Ars Technica Story</a></em></p>
<p>This is, unfortunately, a big deal.  Not just for the users of YubiKeys, but also for anything using Infineon crypto chips.  Infineon makes the crypto chips in a ton of devices, including TPMs, smart cards, passports, credit cards, and SIM cards.  I suspect there will be more fallout from this, as additional devices are found to be using the same cryptographic library.</p>
<p>There are two important mitigations:</p>]]></description>
</item><item>
    <title>Passkey Redaction and the Impact to Organizations</title>
    <link>https://www.adamstas.com/passkey-redaction-and-the-impact-to-organizations/</link>
    <pubDate>Sun, 14 Jul 2024 21:07:55 -0700</pubDate><author>
        <name>Adam Stasiniewicz</name>
    </author><guid>https://www.adamstas.com/passkey-redaction-and-the-impact-to-organizations/</guid>
    <description><![CDATA[<p>Recently, <a href="https://www.esentire.com/blog/securing-passkeys-thwarting-authentication-method-redaction-attacks" target="_blank" rel="noopener noreferrer">eSentire published</a> some interesting research on successfully phishing users even when they’ve configured phishing resistant MFA (like a FIDO2 Passkey or a smart card). For organizations deploying Phishing Resistant MFA (PR-MFA), like a FIDO2 Passkey, be it for internal user authentication or customer logon, there are some important takeaways.</p>]]></description>
</item><item>
    <title>Where to Find My Old Content</title>
    <link>https://www.adamstas.com/where-to-find-my-old-content/</link>
    <pubDate>Thu, 21 Dec 2023 17:09:37 &#43;0000</pubDate><author>
        <name>Adam Stasiniewicz</name>
    </author><guid>https://www.adamstas.com/where-to-find-my-old-content/</guid>
    <description><![CDATA[<p>Much of my public work has disapeared into the depths of the internet, but I found a few things still lurking around.</p>]]></description>
</item><item>
    <title>Thoughts on the EU&#39;s QWAC Proposal</title>
    <link>https://www.adamstas.com/thoughts-on-the-eu-qwac-proposal/</link>
    <pubDate>Tue, 28 Nov 2023 17:34:10 &#43;0000</pubDate><author>
        <name>Adam Stasiniewicz</name>
    </author><guid>https://www.adamstas.com/thoughts-on-the-eu-qwac-proposal/</guid>
    <description><![CDATA[<p>I was recently listening to <a href="https://twit.tv/shows/security-now" target="_blank" rel="noopener noreferrer">Security Now!&rsquo;s</a> coverage of the EU’s QWAC proposal.  There’s much debate regarding the EU’s role in the global PKI ecosystem, when it dawned on me there’s a far simpler solution that should (hopefully) address everyone’s concerns.</p>]]></description>
</item><item>
    <title>Canceling LastPass</title>
    <link>https://www.adamstas.com/canceling-lastpass/</link>
    <pubDate>Sat, 24 Dec 2022 17:25:58 &#43;0000</pubDate><author>
        <name>Adam Stasiniewicz</name>
    </author><guid>https://www.adamstas.com/canceling-lastpass/</guid>
    <description><![CDATA[<p>12 years ago I started paying for LastPass Premium.  Today, I canceled my subscription, migrated my data to a different service, and deleted my account.</p>]]></description>
</item></channel>
</rss>
