<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Infrastructure on Digitaliziran si</title><link>https://cbuctok.github.io/digitaliziran.si/tags/infrastructure/</link><description>Recent content in Infrastructure on Digitaliziran si</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 12 Apr 2026 07:21:05 +0000</lastBuildDate><atom:link href="https://cbuctok.github.io/digitaliziran.si/tags/infrastructure/index.xml" rel="self" type="application/rss+xml"/><item><title>The Security Debt Behind NVIDIA's GH200: What the Marketing Materials Won't Tell You</title><link>https://cbuctok.github.io/digitaliziran.si/2026/04/12/the-security-debt-behind-nvidias-gh200-what-the-marketing-materials-wont-tell-you/</link><pubDate>Sun, 12 Apr 2026 07:21:05 +0000</pubDate><guid>https://cbuctok.github.io/digitaliziran.si/2026/04/12/the-security-debt-behind-nvidias-gh200-what-the-marketing-materials-wont-tell-you/</guid><description>&lt;p&gt;You deployed NVIDIA&amp;rsquo;s GH200 Grace Hopper for its unified CPU-GPU memory architecture - the selling point that makes it a powerhouse for AI and HPC workloads. What nobody mentioned: your operating system is silently placing sensitive data into GPU memory without explicit application intent. And NVIDIA has known about it since at least October 2025.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://cbuctok.github.io/digitaliziran.si/2025/02/10/adventures-in-setting-up-nvidias-gh200-grace-hopper-a-tale-of-two-systems/"&gt;Fourteen months ago, I wrote about the excitement of setting up this hardware&lt;/a&gt; - two systems in one, a Grace CPU paired with a Hopper GPU and a BlueField-3 DPU for good measure. The setup had its quirks, but the promise was clear. Since then, I have been cataloguing what the marketing materials leave out. This is the security reckoning that setup experience did not prepare me for.&lt;/p&gt;</description></item></channel></rss>