-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement new firewall dom0->VM interface #1815
Comments
There is no vm.write_iptables_xenstore_entry(). QubesOS/qubes-issues#1815
- introduce 'firewall-changed' event - add reload_firewall_for_vm stub function Should that function be private, called only from appropriate event handlers? QubesOS/qubes-issues#1815
There is no vm.write_iptables_xenstore_entry(). QubesOS/qubes-issues#1815
- introduce 'firewall-changed' event - add reload_firewall_for_vm stub function Should that function be private, called only from appropriate event handlers? QubesOS/qubes-issues#1815
The outcome is... Quote @marmarek:
|
There is no vm.write_iptables_xenstore_entry(). QubesOS/qubes-issues#1815
- introduce 'firewall-changed' event - add reload_firewall_for_vm stub function Should that function be private, called only from appropriate event handlers? QubesOS/qubes-issues#1815
Questions pertaining to using Whonix with firewall rules keep coming up, so I'm providing a response here so that I can direct people to this issue: Whonix-Gateway does not currently support firewall rules. This is a known issue, which I brought up here and here, which branched off here and is being tracked in #1815 (this issue) and here. Short answer: For now, there's no way to enforce firewall rules for a VM using a |
I've documented new (yet to be implemented) interface for firewall rules: As for implementation (in the VM), I plan to replace current iptables-based |
First part - handling firewall.xml and rules formatting. Specification on https://qubes-os.org/doc/vm-interface/ TODO (for dom0): - plug into QubesVM object - expose rules in QubesDB (including reloading) - drop old functions (vm.get_firewall_conf etc) QubesOS/qubes-issues#1815
This rewrite is mainly to adopt new interface for Qubes 4.x. Main changes: - change language from bash to python, introduce qubesagent python package - support both nftables (preferred) and iptables - new interface (https://qubes-os.org/doc/vm-interface/) - IPv6 support - unit tests included - nftables version support running along with other firewall loaded Fixes QubesOS/qubes-issues#1815 QubesOS/qubes-issues#718
First part - handling firewall.xml and rules formatting. Specification on https://qubes-os.org/doc/vm-interface/ TODO (for dom0): - plug into QubesVM object - expose rules in QubesDB (including reloading) - drop old functions (vm.get_firewall_conf etc) QubesOS/qubes-issues#1815
This will allow setting only IPv4-related rules to IPv4 address, and the same for IPv6 QubesOS/qubes-issues#1815
Currently dom0 do not assign IPv6 addresses for VMs, so there is no sense in IPv6 firewall yet. QubesOS/qubes-issues#1815
First part - handling firewall.xml and rules formatting. Specification on https://qubes-os.org/doc/vm-interface/ TODO (for dom0): - plug into QubesVM object - expose rules in QubesDB (including reloading) - drop old functions (vm.get_firewall_conf etc) QubesOS/qubes-issues#1815
Currently dom0 do not assign IPv6 addresses for VMs, so there is no sense in IPv6 firewall yet. QubesOS/qubes-issues#1815
First part - handling firewall.xml and rules formatting. Specification on https://qubes-os.org/doc/vm-interface/ TODO (for dom0): - plug into QubesVM object - expose rules in QubesDB (including reloading) - drop old functions (vm.get_firewall_conf etc) QubesOS/qubes-issues#1815
This will allow setting only IPv4-related rules to IPv4 address, and the same for IPv6 QubesOS/qubes-issues#1815
Currently dom0 do not assign IPv6 addresses for VMs, so there is no sense in IPv6 firewall yet. QubesOS/qubes-issues#1815
Shouldn't a warning be displayed when using sys-whonix as NetVM and opening the Firewall tab in VM Preferences, just like it is when sys-net is used as NetVM? Otherwise, how will the average user know? |
Sounds like this is covered by #2003. |
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
This is placeholder for the outcome of this discussion: https://groups.google.com/d/msgid/qubes-devel/20160114163808.GW4892%40mail-itl
The text was updated successfully, but these errors were encountered: