I’m using sys-cacher (via qusal) and have found it to be terrific and life-changing
I have a significant number of templates (more than a dozen) so the impact is mega
However, I’m not quite sure how to handle (or, how to properly configure) the whonix templates to use cacher. I understand how and why they aren’t using sys-cacher “out of the box” and that makes sense
I’ve thought about what I want to do, in the context of what is acceptable for my privacy requirements
- Using
sys-cacher
for anon/whonix VMs is acceptable to me. The upstream forsys-cacher
is a VPN which I don’t mind inferring that I’m using whonix - Using a special (second)
sys-cacher
(e.g.sys-cacher-anon
) with asys-whonix
upstream would also be fine, though I think it may be a bunch more work, and I don’t know that I personally benefit much from anonymizing my whonix updates
So I’m flexible. But I want cached updates for whonix templates, and I do not want to use whonix/tor for the main sys-cacher
used by non-whonix VMs (because tor is slow, and I don’t need the anonymity)
What is the ideal way to configure Qubes to do what I want?
Do I simply enable updates-proxy-set
service in the whonix template VMs, and ensure they are permitted via qubes rpc?
I have seen this thread which discusses cacher and whonix a bit, and at least one other, but I had a hard time following the discussion
Point me to a thread that contains roughly what I might need to better understand how/what to do and I will take another pass at it, even if it’s one I’ve already read. I don’t necessarily need a guide. Though a brief one would be appreciated