<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>VyOS - Blog</title>
    <link>https://blog.vyos.io</link>
    <description>VyOS Platform Project news and updates 
All about development and project life in  our blog</description>
    <language>en</language>
    <pubDate>Tue, 28 Jul 2026 10:45:00 GMT</pubDate>
    <dc:date>2026-07-28T10:45:00Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>VyOS Project June &amp; July 2026 Update</title>
      <link>https://blog.vyos.io/vyos-project-june-july-2026</link>
      <description>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://blog.vyos.io/vyos-project-june-july-2026" title="" class="hs-featured-image-link"&gt; &lt;img src="https://blog.vyos.io/hubfs/vyos_mothly_update_june-july2026_blogpost.png" alt="VyOS Project June &amp;amp; July 2026 Update" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Hello, Community!&lt;/p&gt; 
&lt;p&gt;The June and July development update is here. Over the past two months, the VyOS team focused on security and compliance enhancements, community-driven improvements, platform updates, and customer engagement.&amp;nbsp;&lt;/p&gt; 
&lt;p&gt;On the security side, we laid the groundwork for FIPS compliance, added post-quantum key exchange to IPsec, and started publishing SBOM artifacts for full supply-chain transparency. The community also stepped in with some hard-won fixes, from a zone-based firewall bug in VRF configurations to a route-target quirk that was causing needless traffic interruptions on every commit.&amp;nbsp;&lt;/p&gt;</description>
      <content:encoded>&lt;div class="hs-featured-image-wrapper"&gt; 
 &lt;a href="https://blog.vyos.io/vyos-project-june-july-2026" title="" class="hs-featured-image-link"&gt; &lt;img src="https://blog.vyos.io/hubfs/vyos_mothly_update_june-july2026_blogpost.png" alt="VyOS Project June &amp;amp; July 2026 Update" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"&gt; &lt;/a&gt; 
&lt;/div&gt; 
&lt;p&gt;Hello, Community!&lt;/p&gt; 
&lt;p&gt;The June and July development update is here. Over the past two months, the VyOS team focused on security and compliance enhancements, community-driven improvements, platform updates, and customer engagement.&amp;nbsp;&lt;/p&gt; 
&lt;p&gt;On the security side, we laid the groundwork for FIPS compliance, added post-quantum key exchange to IPsec, and started publishing SBOM artifacts for full supply-chain transparency. The community also stepped in with some hard-won fixes, from a zone-based firewall bug in VRF configurations to a route-target quirk that was causing needless traffic interruptions on every commit.&amp;nbsp;&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4129050&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fblog.vyos.io%2Fvyos-project-june-july-2026&amp;amp;bu=https%253A%252F%252Fblog.vyos.io&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>ipsec</category>
      <category>vyos</category>
      <category>openssl</category>
      <category>Development Update</category>
      <category>Network Security</category>
      <category>ML-KEM</category>
      <category>FIPS</category>
      <category>Post-Quantum Cryptography</category>
      <category>SBOM</category>
      <pubDate>Tue, 28 Jul 2026 10:45:00 GMT</pubDate>
      <author>daniil@sentrium.io (Daniil Baturin)</author>
      <guid>https://blog.vyos.io/vyos-project-june-july-2026</guid>
      <dc:date>2026-07-28T10:45:00Z</dc:date>
    </item>
  </channel>
</rss>
