<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: shellcromancer</title><link>https://news.ycombinator.com/user?id=shellcromancer</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 25 Jun 2026 03:46:53 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=shellcromancer" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by shellcromancer in "OpenAI unveils its first custom chip, built by Broadcom"]]></title><description><![CDATA[
<p>Probably obvious but still omitted in the OpenAI post: chips are being made by TSMC [1]. Wasn't sure if Intel got it.<p>1. <a href="https://www.investing.com/news/stock-market-news/openai-unveils-custom-chip-it-designed-with-broadcom-to-boost-its-ai-infrastructure-4758233" rel="nofollow">https://www.investing.com/news/stock-market-news/openai-unve...</a></p>
]]></description><pubDate>Wed, 24 Jun 2026 14:36:31 +0000</pubDate><link>https://news.ycombinator.com/item?id=48660641</link><dc:creator>shellcromancer</dc:creator><comments>https://news.ycombinator.com/item?id=48660641</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48660641</guid></item><item><title><![CDATA[New comment by shellcromancer in "Notepad++ hijacked by state-sponsored actors"]]></title><description><![CDATA[
<p>> Additionally, the XML returned by the update server is now singed (XMLDSig)<p>The latest and greatest cryptography powering everyone’s favorite SAML-based single-sign on.</p>
]]></description><pubDate>Mon, 02 Feb 2026 04:47:55 +0000</pubDate><link>https://news.ycombinator.com/item?id=46852520</link><dc:creator>shellcromancer</dc:creator><comments>https://news.ycombinator.com/item?id=46852520</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46852520</guid></item><item><title><![CDATA[Credential Exchange Format publishes version 1.0]]></title><description><![CDATA[
<p>Article URL: <a href="https://fidoalliance.org/specs/cx/cxf-v1.0-ps-20250814.html">https://fidoalliance.org/specs/cx/cxf-v1.0-ps-20250814.html</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=44998186">https://news.ycombinator.com/item?id=44998186</a></p>
<p>Points: 3</p>
<p># Comments: 0</p>
]]></description><pubDate>Sat, 23 Aug 2025 18:56:55 +0000</pubDate><link>https://fidoalliance.org/specs/cx/cxf-v1.0-ps-20250814.html</link><dc:creator>shellcromancer</dc:creator><comments>https://news.ycombinator.com/item?id=44998186</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=44998186</guid></item><item><title><![CDATA[New comment by shellcromancer in "The cryptography behind passkeys"]]></title><description><![CDATA[
<p>The FIDO Alliance (who wrote the WebAuthn spec with the W3C) has a draft specification for a format (Credential Exchange Format) and protocol (Credential Exchange Protocol) for migrating passkeys and other credentials [1]. I don't think this is implemented by any providers yet, but it's being worked on.<p>[1] <a href="https://fidoalliance.org/specifications-credential-exchange-specifications/" rel="nofollow">https://fidoalliance.org/specifications-credential-exchange-...</a></p>
]]></description><pubDate>Wed, 14 May 2025 19:32:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=43988343</link><dc:creator>shellcromancer</dc:creator><comments>https://news.ycombinator.com/item?id=43988343</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43988343</guid></item><item><title><![CDATA[New comment by shellcromancer in "Sign in as anyone: Bypassing SAML SSO authentication with parser differentials"]]></title><description><![CDATA[
<p>Security Cryptography Whatever’s take on this week SAML non-sense will be fun.</p>
]]></description><pubDate>Sat, 15 Mar 2025 21:22:21 +0000</pubDate><link>https://news.ycombinator.com/item?id=43375239</link><dc:creator>shellcromancer</dc:creator><comments>https://news.ycombinator.com/item?id=43375239</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43375239</guid></item><item><title><![CDATA[Passkey Central]]></title><description><![CDATA[
<p>Article URL: <a href="https://www.passkeycentral.org/home/">https://www.passkeycentral.org/home/</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=41844465">https://news.ycombinator.com/item?id=41844465</a></p>
<p>Points: 3</p>
<p># Comments: 0</p>
]]></description><pubDate>Tue, 15 Oct 2024 02:51:15 +0000</pubDate><link>https://www.passkeycentral.org/home/</link><dc:creator>shellcromancer</dc:creator><comments>https://news.ycombinator.com/item?id=41844465</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41844465</guid></item><item><title><![CDATA[New comment by shellcromancer in "EUCLEAK Side-Channel Attack on the YubiKey 5 Series"]]></title><description><![CDATA[
<p>Fantastic research by NinjaLab. One of the most interesting parts to me from Yubico's advisory is that the Webauthn protocols attestation [1] is also defeated by this local cloning. Could the protocol have been better designed to resist this local cloning attack?<p>> An attacker could exploit this issue to create a fraudulent YubiKey using the recovered attestation key. This would produce a valid FIDO attestation statement during the make credential resulting in a bypass of an organization’s authenticator model preference controls for affected YubiKey versions.<p>1. <a href="https://www.w3.org/TR/webauthn-2/#attestation" rel="nofollow">https://www.w3.org/TR/webauthn-2/#attestation</a></p>
]]></description><pubDate>Tue, 03 Sep 2024 19:48:16 +0000</pubDate><link>https://news.ycombinator.com/item?id=41438457</link><dc:creator>shellcromancer</dc:creator><comments>https://news.ycombinator.com/item?id=41438457</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=41438457</guid></item><item><title><![CDATA[New comment by shellcromancer in "Pql, a pipelined query language that compiles to SQL"]]></title><description><![CDATA[
<p>> The where operator will validate that the syntax is valid, but it will pass unknown function calls through to the underlying database. In RunReveal's case, we use Clickhouse under the hood, so if we wanted to do a case-insensitive match we could still use Clickhouse's lower function.<p>From the release blog [1] they mention that unknown functions are passed through to the underlying SQL engine -- this let's them target anything from mysql, Postgres, ClickHouse or proprietary engines like Snowflake.<p>1. <a href="https://blog.runreveal.com/introducing-pql/" rel="nofollow">https://blog.runreveal.com/introducing-pql/</a></p>
]]></description><pubDate>Thu, 29 Feb 2024 16:16:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=39551321</link><dc:creator>shellcromancer</dc:creator><comments>https://news.ycombinator.com/item?id=39551321</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=39551321</guid></item><item><title><![CDATA[New comment by shellcromancer in "Show HN: Skip the SSO Tax, access your user data with OSS"]]></title><description><![CDATA[
<p>Shameless self-plug for an alternative tax that affects operational security and reliability teams: <a href="https://audit-logs.tax" rel="nofollow">https://audit-logs.tax</a><p>Understanding how your breach impacts me, or detecting how the abuse of your tools are used to impact our organizations shouldn't cost additional money or be gated to only enterprise contracts.<p>Happy to take PRs for other vendors logs being added: <a href="https://github.com/shellcromancer/audit-log-wall-of-shame">https://github.com/shellcromancer/audit-log-wall-of-shame</a></p>
]]></description><pubDate>Tue, 11 Apr 2023 18:12:39 +0000</pubDate><link>https://news.ycombinator.com/item?id=35528922</link><dc:creator>shellcromancer</dc:creator><comments>https://news.ycombinator.com/item?id=35528922</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=35528922</guid></item><item><title><![CDATA[Coinbase disrupts social engineering attack]]></title><description><![CDATA[
<p>Article URL: <a href="https://www.coinbase.com/blog/social-engineering-a-coinbase-case-study">https://www.coinbase.com/blog/social-engineering-a-coinbase-case-study</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=34843625">https://news.ycombinator.com/item?id=34843625</a></p>
<p>Points: 1</p>
<p># Comments: 0</p>
]]></description><pubDate>Sat, 18 Feb 2023 03:39:02 +0000</pubDate><link>https://www.coinbase.com/blog/social-engineering-a-coinbase-case-study</link><dc:creator>shellcromancer</dc:creator><comments>https://news.ycombinator.com/item?id=34843625</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=34843625</guid></item><item><title><![CDATA[New comment by shellcromancer in "AirDrop is now limited to 10 minutes"]]></title><description><![CDATA[
<p>Regardless of where it's rolled out first, this is a good example of reducing the attack surface from remote exploits (which China is known to have and use at contests like Tianfu Cup). Seems in line with changes they made with "Lockdown Mode" that users can opt into.</p>
]]></description><pubDate>Mon, 28 Nov 2022 20:41:01 +0000</pubDate><link>https://news.ycombinator.com/item?id=33779276</link><dc:creator>shellcromancer</dc:creator><comments>https://news.ycombinator.com/item?id=33779276</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=33779276</guid></item></channel></rss>