|
|
@@ -136,9 +136,7 @@ Of course `expire=` and `comment=` are optional fields.
|
|
|
<property name="comment">example https server rule</property>
|
|
|
</properties>
|
|
|
</rule>
|
|
|
-```Sorry. We’re having trouble getting your pages back.
|
|
|
-
|
|
|
-We are having trouble restoring your last browsing session. Select Restore Session to try again.
|
|
|
+```
|
|
|
|
|
|
### Proposal chart
|
|
|
###### The main distinction between internal and external port forwarding is:
|
|
|
@@ -160,7 +158,6 @@ 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
|
|
|
needs to support the new options for the rule (action=forward
|
|
|
frowardtype=<internal/external> srcports=443-443 srchosts=0.0.0.0/0
|
|
|
@@ -175,7 +172,7 @@ building the correct syntax for iptables or nft and the actual execution
|
|
|
5. ❌ Tests
|
|
|
6. ❌ GUI
|
|
|
|
|
|
- Both tests and GUI have yet to be worked on. Automated tests will be written soon in the following weeks.
|
|
|
+Steps 1-3 are completed and needs the automated test. Step 4 has still some issues but it is in its final stages. 5 will be worked on in the following weeks, since it is mandatory before merging anything. 6 can come at a later stage.
|
|
|
|
|
|
### Required rules
|
|
|
#### External
|
