From 4ebe5866299597fa98de9d0c1c26e1c960e4acdb Mon Sep 17 00:00:00 2001
From: urist <urist@dev.null>
Date: Wed, 25 Dec 2024 15:49:41 +0100
Subject: [PATCH] move attack flow diagram to the article folder

---
 .../high_availability}/ha_attack_flow.png           | Bin
 opsec/high_availability/index.html                  |   2 +-
 2 files changed, 1 insertion(+), 1 deletion(-)
 rename {assets/img => opsec/high_availability}/ha_attack_flow.png (100%)

diff --git a/assets/img/ha_attack_flow.png b/opsec/high_availability/ha_attack_flow.png
similarity index 100%
rename from assets/img/ha_attack_flow.png
rename to opsec/high_availability/ha_attack_flow.png
diff --git a/opsec/high_availability/index.html b/opsec/high_availability/index.html
index 6f3d47f..9beb988 100644
--- a/opsec/high_availability/index.html
+++ b/opsec/high_availability/index.html
@@ -156,7 +156,7 @@ from extracting location information based on their operation. This works best w
 Below is a chart depicting an adversary attack flow. As shown, high availability will prevent the adversary from progressing beyond their initial step of uptime-based target acquisition.
 <br>
 <br>
-<img src="../../assets/img/ha_attack_flow.png" width="75%" height="75%">
+<img src="ha_attack_flow.png" width="75%" height="75%">
 
 </p>