Re: [qubes-users] UpdateVM pref not sticking

['MirrorWay' via qubes-users]

I was confused by the same thing - 
https://github.com/QubesOS/qubes-issues/issues/3527

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/-qGWYBZyrKv0aQdqQoBWvW5_CnHL6wRC3jle2MiB7a3-jIkByQhkE6cD358KENuDuhgToqJqPP4iTtS0IjUQiXHK50d9-CG95jNHO6JRUSk%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] UpdateVM pref not sticking

[Unman]

On Sat, Mar 24, 2018 at 05:35:01PM -0400, Micah Lee wrote:
> ‐‐‐ Original Message ‐‐‐
> 
> On March 24, 2018 2:28 PM, Micah Lee  wrote:
> 
> > When I installed Qubes 4.0 I chose to install all of my updates over Tor. 
> > Since then, I've opened Qubes Global Settings and changed UpdateVM to 
> > sys-firewall.
> > 
> > When I install dom0 updates, this seems to work fine. It says `Using 
> > sys-firewall as UpdateVM to download updates for Dom0`.
> > 
> > But when I try installing updates in my templates, such fedora-26, it still 
> > uses sys-whonix as the UpdateVM. I'm sure because as soon as I try 
> > installing updates, sys-whonix starts, and if I shut it down in the middle 
> > of updates, the updates fail. (And also the downloads are very slow.)
> > 
> > I'd like to be able to control which UpdateVM my templates use to update. 
> > Any idea how I can troubleshoot what's going on?
> 
> 
> Looking at another thread going on right now, I found this useful:
> https://groups.google.com/forum/#!searchin/qubes-users/Whonix%7Csort:date/qubes-users/gLqORddxb-Y/mDxXDi3cAwAJ
> 
> I can edit /etc/qubes-rpc/policy/qubes.UpdatesProxy, and change 
> target=sys-whonix to target=sys-net. After I do that, my template seems to 
> use sys-net as the UpdateVM.
> 
> This seems like a bug though. Shouldn't this file change when I change Qubes 
> Global Settings?

This has come up before - it's the same situation as in 3.2 with "Global
Settings" in Qubes manager.
The term "Global" here, doesnt mean "across the board": it's what
applies to dom0. I think this is somewhat misleading, but it's how it
is.
So not a bug, but misleading.

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20180324235622.gi2qk3afaqrlimi5%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] UpdateVM pref not sticking

[Micah Lee]

‐‐‐ Original Message ‐‐‐

On March 24, 2018 2:28 PM, Micah Lee  wrote:

> When I installed Qubes 4.0 I chose to install all of my updates over Tor. 
> Since then, I've opened Qubes Global Settings and changed UpdateVM to 
> sys-firewall.
> 
> When I install dom0 updates, this seems to work fine. It says `Using 
> sys-firewall as UpdateVM to download updates for Dom0`.
> 
> But when I try installing updates in my templates, such fedora-26, it still 
> uses sys-whonix as the UpdateVM. I'm sure because as soon as I try installing 
> updates, sys-whonix starts, and if I shut it down in the middle of updates, 
> the updates fail. (And also the downloads are very slow.)
> 
> I'd like to be able to control which UpdateVM my templates use to update. Any 
> idea how I can troubleshoot what's going on?


Looking at another thread going on right now, I found this useful:
https://groups.google.com/forum/#!searchin/qubes-users/Whonix%7Csort:date/qubes-users/gLqORddxb-Y/mDxXDi3cAwAJ

I can edit /etc/qubes-rpc/policy/qubes.UpdatesProxy, and change 
target=sys-whonix to target=sys-net. After I do that, my template seems to use 
sys-net as the UpdateVM.

This seems like a bug though. Shouldn't this file change when I change Qubes 
Global Settings?

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1I6fw0aN1qNu1ceuqUMupRoDL38Dn-aLhox9wTOkwIAxAcG54APubk62trf1eCqDEwcOuTZ6lvMzs19oKlBJchss00dA7snHdK3CRLwb5OM%3D%40micahflee.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] UpdateVM pref not sticking

[Micah Lee]

When I installed Qubes 4.0 I chose to install all of my updates over Tor. Since 
then, I've opened Qubes Global Settings and changed UpdateVM to sys-firewall.

When I install dom0 updates, this seems to work fine. It says `Using 
sys-firewall as UpdateVM to download updates for Dom0`.

But when I try installing updates in my templates, such fedora-26, it still 
uses sys-whonix as the UpdateVM. I'm sure because as soon as I try installing 
updates, sys-whonix starts, and if I shut it down in the middle of updates, the 
updates fail. (And also the downloads are very slow.)

I'd like to be able to control which UpdateVM my templates use to update. Any 
idea how I can troubleshoot what's going on?
​

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/uTNNgSLwOQzmGANQ505H44OTCoTO4VrUtXQBeFdyzCB3bOdGS-8pqN9JM0oncUOViqEc0YBFJxghkP1Vx9mV_o78UvjAI2LiyQsp3FJDB5o%3D%40micahflee.com.
For more options, visit https://groups.google.com/d/optout.