On Thursday, March 29, 2018 at 6:53:30 PM UTC-4, awokd wrote:
> On Thu, March 29, 2018 4:34 pm, cooloutac wrote:
> > Upgraded to 4.0.  was able to restore all my backup vms no problems.
> 
> > made all qubes update proxy entries changed from sys-whonix  to
> > sys-firewall.
> >
> > But does this mean dom0 is not really using tor to update?
> 
> I think dom0 only looks at the UpdateVM setting in qubes-prefs for its
> update location.
> 
> > Is whonix
> > even using tor to update after doing this?  I'm confused.
> 
> I believe it would not.
> 
> > But its driving me nuts that the default fedora-26-dvm always shows
> > updates pending. and I don't know how to get rid of it.  I even changed
> > its template and it still shows updates pending and it won't let me
> > delete altogether so I can just use my custom one.
> >
> > Any solution to this?
> 
> Not sure on this one, maybe one of the salt commands is needed?

yes, actually looks like dom0's update setting is totally separate  so its 
probably using tor.  https://github.com/QubesOS/qubes-issues/issues/3527

Not sure about whonix templates itself though?  I guess I have to check that 
proxy file again.

According to another github i can't find right now,  doesn't look like fedora 
will be able to update over tor any time soon using whonix.   But according to 
the github above each template can use a specific updatevm in 4.0.

Also now my custom dvm is constantly showing updates pending in qubes manager.  
 Once i update the template used for the dvm template,  it constantly shows 
update pending.

-- 
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/f05e1d96-0a7b-4048-92a6-4ecc5eefc839%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to