On Thu, Oct 18, 2018 at 12:06:21AM -0700, [email protected] wrote: > On Tuesday, October 16, 2018 at 5:46:13 PM UTC, Frozentime345 wrote: > > 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. > > > > 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. > > For some reason Im not receiving emails from my own thread lol? Luckily I > googled the group to see if the post made it. > Cool on qubes 4.1 sounds good. > > Thanks, I'll look into udev config. > > Will this no auto default setting for network manager stop new connections or > just stop network manager? Ideally I want it to allow me to config new > networks before connecting or ask me confirmation before connecting, > basically to prevent user error. >
man networkmanager.conf Those were alternatives I gave - either disable NetworkManager OR configure so as not to create default connections. -- 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/20181018113424.ysdbsl4ksrpeoup4%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
