Qubes/gsoc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Lost all hope about lists

Browse Source
This commit is contained in:
Giulio 2021-06-25 16:37:58 +02:00
parent cf7ba09bb2
commit 0bd2bb7181
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Readme.md
View File

@ -149,18 +149,20 @@ It is important to note that in the last case, it is just a standard case of int
### Implementation Roadmap ### Implementation Roadmap
1. ✔️ In `core-admin-client/qubesadmin/firewall.py` firewall.py > The code
1. ✔️ In `core-admin-client/qubesadmin/firewall.py` firewall.py > The code
needs to support the new options for the rule (action=forward needs to support the new options for the rule (action=forward
frowardtype=<internal/external> srcports=443-443 srchosts=0.0.0.0/0 frowardtype=<internal/external> srcports=443-443 srchosts=0.0.0.0/0
2. ✔️ In `core-admin/qubes/firewall.py` -> The code needs to support the same 2. ✔️ In `core-admin/qubes/firewall.py` -> The code needs to support the same
options as the point above options as the point above
3. 🚧 In `core-admin/qubes/vm/mix/net.py` -> The most important logic goes 3. 🚧 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 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 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. 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 4. ❌ In `core-agent-linux/qubesagent/firewall.py` -> Here goes the logic for
building the correct syntax for iptables or nft and the actual execution building the correct syntax for iptables or nft and the actual execution
5. ❌ GUI 5. ❌ GUI