From 4c612624445e1b3d8bc60abbbd7f1fea1e4a18b4 Mon Sep 17 00:00:00 2001
From: The Robur Team <team@robur.coop>
Date: Mon, 28 Oct 2024 17:32:24 +0000
Subject: [PATCH] Pushed by YOCaml 2 from
 52bd07a059749b96c7933e6303de25dbdfbc696e

---
 articles/2024-08-21-OpenVPN-and-MirageVPN.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/articles/2024-08-21-OpenVPN-and-MirageVPN.html b/articles/2024-08-21-OpenVPN-and-MirageVPN.html
index 15a320e..ca598d8 100644
--- a/articles/2024-08-21-OpenVPN-and-MirageVPN.html
+++ b/articles/2024-08-21-OpenVPN-and-MirageVPN.html
@@ -25,7 +25,7 @@
 <article>
     <h1>MirageVPN and OpenVPN</h1>
     <ul class="tags-list"><li><a href="/tags.html#tag-MirageVPN">MirageVPN</a></li><li><a href="/tags.html#tag-OpenVPN">OpenVPN</a></li><li><a href="/tags.html#tag-security">security</a></li></ul><p>At <a href="https://robur.coop/">Robur</a> we have been busy at work implementing our OpenVPN™-compatible MirageVPN software.
-Recently we have implemented the <a href="https://blog.robur.coop/articles/miragevpn-server.html">server side</a>.
+Recently we have implemented the <a href="miragevpn-server">server side</a>.
 In order to implement this side of the protocol I studied parts of the OpenVPN™ source code and performed experiments to understand what the implementation does at the protocol level.
 Studying the OpenVPN™ implementation has lead me to discover two security issues: CVE-2024-28882 and CVE-2024-5594.
 In this article I will talk about the relevant parts of the protocol, and describe the security issues in detail.</p>