<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Supply Chain Security on Ulveon's Thoughts</title><link>https://ulveon-thoughts-f210db.gitlab.io/tag/supply-chain-security/</link><description>Recent content in Supply Chain Security on Ulveon's Thoughts</description><generator>Hugo</generator><language>en-IE</language><lastBuildDate>Wed, 03 Dec 2025 08:00:00 +0100</lastBuildDate><atom:link href="https://ulveon-thoughts-f210db.gitlab.io/tag/supply-chain-security/index.xml" rel="self" type="application/rss+xml"/><item><title>The secure open source fallacy</title><link>https://ulveon-thoughts-f210db.gitlab.io/p/2025-12-03-the-secure-open-source-fallacy/</link><pubDate>Wed, 03 Dec 2025 08:00:00 +0100</pubDate><guid>https://ulveon-thoughts-f210db.gitlab.io/p/2025-12-03-the-secure-open-source-fallacy/</guid><description>&lt;p&gt;Most open source advocates, and many security professionals, often say things like &amp;ldquo;open source software is secure because you can just read the code&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;This argument assumes that the ability to read source code directly translates into the ability to understand, verify, and trust it, because you can see the files this software opens or the network sockets it listens on. You can see the kind of network data it sends, and the cryptography it uses.&lt;/p&gt;</description></item></channel></rss>