Fixed list maybe?
This commit is contained in:
parent
715096466d
commit
8a228695d6
11
Readme.md
11
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=<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
|
||||
* ✔️ 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
|
||||
|
Loading…
Reference in New Issue
Block a user