On 09/21/2016 06:24 AM, Robert Mittendorf wrote:
Am 09/20/2016 um 10:29 PM schrieb Chris Laprise:
This is a good candidate for filing an issue, but mainly for this
situation -- "A warning if an upstream VM does not implement the
firewall rules", which should include connecting to netvms.
II
Am 09/20/2016 um 10:29 PM schrieb Chris Laprise:
This is a good candidate for filing an issue, but mainly for this
situation -- "A warning if an upstream VM does not implement the
firewall rules", which should include connecting to netvms.
IIRC, Qubes Manager used to grey-out the firewall ta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-09-21 03:07, Andrew David Wong wrote:
> On 2016-09-20 10:16, mittend...@digitrace.de wrote:
>> [...]
> Thanks! This general suggestion has previously been made
> and is currently being tracked here:
>
> https://github.com/QubesOS/qubes-issue
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-09-20 10:16, mittend...@digitrace.de wrote:
> Hey,
>
> Firewall rules are set for a specific VM/Qube. From common understanding
> people would probably think that those rules are active no matter what
> happens outside of that very VM/Qube
On 09/20/2016 01:16 PM, mittend...@digitrace.de wrote:
Hey,
Firewall rules are set for a specific VM/Qube. From common
understanding people would probably think that those rules are active
no matter what happens outside of that very VM/Qube, but in fact it
seems like those rules are active if
Hey,
Firewall rules are set for a specific VM/Qube. From common understanding
people would probably think that those rules are active no matter what
happens outside of that very VM/Qube, but in fact it seems like those
rules are active if and only if there is an ProxyVM connected to that
VM/Q