Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upIt's impossible to set firewall policy and rules atomically #2869
Comments
marmarek
added
C: core
enhancement
P: major
labels
Jun 26, 2017
marmarek
added this to the Release 4.0 milestone
Jun 26, 2017
marmarek
self-assigned this
Jun 26, 2017
added a commit
to QubesOS/qubes-doc
that referenced
this issue
Jun 26, 2017
added a commit
to marmarek/qubes-core-admin
that referenced
this issue
Jun 26, 2017
added a commit
to marmarek/qubes-core-admin-client
that referenced
this issue
Jun 26, 2017
added a commit
to marmarek/qubes-core-admin-client
that referenced
this issue
Jun 26, 2017
marmarek
closed this
in
marmarek/qubes-core-admin@842efb5
Jul 4, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
qubesos-bot
Jul 4, 2017
Automated announcement from builder-github
The package qubes-core-dom0-4.0.1-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:
sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
qubesos-bot
commented
Jul 4, 2017
|
Automated announcement from builder-github The package
|
qubesos-bot
added
the
r4.0-dom0-cur-test
label
Jul 4, 2017
qubesos-bot
referenced this issue
in QubesOS/updates-status
Jul 4, 2017
Closed
core-admin v4.0.1 (r4.0) #100
added a commit
to marmarek/qubes-core-admin-client
that referenced
this issue
Jul 5, 2017
added a commit
to marmarek/qubes-core-admin-client
that referenced
this issue
Jul 5, 2017
qubesos-bot
referenced this issue
in QubesOS/updates-status
Jul 5, 2017
Closed
core-admin-client v4.0.1 (r4.0) #116
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
marmarek commentedJun 26, 2017
Sometimes it's useful to update firewall rules while VM is running. In this case, it's important to atomically set the firewall - especially when VM have some traffic filtered, it should not have access to those targets also during loading new firewall.
Having separate policy (default action) and actual rules makes it hard.
Safer alternative: always have policy "drop" and optionally put "always allow" rule at the end.