Frozentime345 wrote on 10/16/18 5:59 AM:
System: Fedora 27/Debian 9 Templates, R3.2->upgrading to 4.0 soon
I looked through rpc policy but I couldn't find anything like this, is
there
a way to only allow certain block devices for certain appvms? Doesn't
even have to be a secure feature just something to prevent user error,
but it has to work at the qubes level so a
"bad" block device doesn't compromise the appvm.
I believe there will be some type of block device isolation (a
"sys-block" maybe) coming in Qubes 4.1, so fine grained controls might
be part of that.
Similarly, is there something in sys-net I can use to white-list? I
tried the network connections manager but I cant seem to stop it from
connecting to unknown ethernets, after its known I can set “don't
automatically connect” though.
This might vary by the distribution you are using for sys-net. Try
searching for what you are trying to accomplish with the distribution
name e.g. "Debian", instead of "Qubes". Most should apply the same way,
just make your changes in sys-net instead.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/1f4874ec-ba3e-308c-85c6-41ec3ee8fb63%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.
