I was contemplating to drop support for Qubes R3.2. Makes development a
lot harder / time consuming to keep compatibility with both in mind.
Suffering from sunken cost fallacy.
0brand:
[quote=“Patrick, post:743, topic:3477”]
This very chapter: https://www.whonix.org/wiki/Dev/Qubes#Connection_through_Qubes_Updates_Proxy
Could you please test? And document a bit better?Also the following…
Qubes R3.2
http_proxy=http://10.137.255.254:8082 gpg.anondist-orig --recv-keys ...
Please forget about doing this in a TempalteVM for a second for testing
purposes. Does the gpg --recv-keys key work for you?
This is what is happening for me in a Debian VM.
gpg --recv-keys “916B 8D99 C38E AF5E 8ADC 7A2A 8D66 066A 2EEA CCDA”
gpg: keyserver receive failed: Server indicated a failure
http_proxy=http://10.137.255.254:8082 curl.anondist-orig check.torproject.org works for me in Qubes-Whonix 14 Qubes R3.2. Does
that work for you?
Qubes R4
http_proxy=http://127.0.0.1:8082 gpg.anondist-orig --recv-keys ...Would then be possible. What would be a good place to document this?
[/quote]
Does http_proxy=http://127.0.0.1:8082 gpg.anondist-orig check.torproject.org work for you in Qubes-Whonix 14 Qubes R4?
The goal is for connecting without enabling networking in TemplateVMs? Correct?
Correct.