<?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[Defender 1: This appliance is running an ancient AF version, how is it not a smoking ruin at this point?]]></title><description><![CDATA[<p>Defender 1: This appliance is running an ancient AF version, how is it not a smoking ruin at this point?</p><p>Defender 2: Well, it turns out that all of the attacker scanning tools use libraries that have disabled TLS before 1.0 and this appliance only supports SSL v3 sooo.... </p><ul><li>OpenSSL 1.1.1 sets the default min to TLS 1.0</li><li>Python 2.7 / 3.6 set the default min to TLS 1.0 but depend on the underlying crypto lib.</li><li>Go default min prior to 1.18 was TLS 1.0</li><li><code>curl</code> default min was TLS 1.0 from curl 7.39.0 to 8.15.x</li><li><code>wget</code> uses underlying lib</li></ul><p><a href="https://infosec.exchange/tags/Security" rel="tag">#<span>Security</span></a> <a href="https://infosec.exchange/tags/TLS" rel="tag">#<span>TLS</span></a></p>]]></description><link>https://board.circlewithadot.net/topic/5a82c20f-cb21-4051-b406-33737b6ef00d/defender-1-this-appliance-is-running-an-ancient-af-version-how-is-it-not-a-smoking-ruin-at-this-point</link><generator>RSS for Node</generator><lastBuildDate>Fri, 17 Apr 2026 03:45:56 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/5a82c20f-cb21-4051-b406-33737b6ef00d.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 30 Mar 2026 17:02:48 GMT</pubDate><ttl>60</ttl></channel></rss>