From 8a228695d6f6b902c0a46db0f34b3d9923e7ef18 Mon Sep 17 00:00:00 2001 From: Giulio Date: Fri, 25 Jun 2021 16:35:37 +0200 Subject: [PATCH] Fixed list maybe? --- Readme.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/Readme.md b/Readme.md index f441ace..eeffcb5 100644 --- a/Readme.md +++ b/Readme.md @@ -149,19 +149,18 @@ It is important to note that in the last case, it is just a standard case of int ### Implementation Roadmap - 1. ✔️ In `core-admin-client/qubesadmin/firewall.py` firewall.py > The code + * ✔️ In `core-admin-client/qubesadmin/firewall.py` firewall.py > The code needs to support the new options for the rule (action=forward frowardtype= srcports=443-443 srchosts=0.0.0.0/0 - 2. ✔️ In `core-admin/qubes/firewall.py` -> The code needs to support the same + * ✔️ In `core-admin/qubes/firewall.py` -> The code needs to support the same options as the point above - 3. 🚧 In `core-admin/qubes/vm/mix/net.py` -> The most important logic goes + * 🚧 In `core-admin/qubes/vm/mix/net.py` -> The most important logic goes here. Here there is the need to resolve the full network chain for external port forwarding. From here it is possible to add the respective rules to the QubesDB of each NetVM in he chain and trigger a reload event. - 4. ❌ In `core-agent-linux/qubesagent/firewall.py` -> Here goes the logic for + * ❌ In `core-agent-linux/qubesagent/firewall.py` -> Here goes the logic for building the correct syntax for iptables or nft and the actual execution - 5. ❌ GUI - + * ❌ GUI ### Required rules