0brand:
I followed all the steps from the links you provided (in sys-whonix and whonix-gw Template when appropriate) and curl
must be run under user clearnet
for both temporary or permanent deactivation.
Is this what is expected?
Whonix 14:
Have a look at the end what really happens. Only the latest exec
calls matters.
uwtwrapper_verbose=1 curl something
Expected:
Using uwt / torsocks / stream isolation.
Result:
exec torsocks /usr/lib/uwtexec something
exec -a /usr/bin/curl /usr/bin/curl.anondist-orig something
I.e. torsocks gets prepended before running curl.
uwtwrapper_verbose=1 UWT_DEV_PASSTHROUGH=1 curl something
Expected:
Not using torsocks / stream isolation.
Result:
exec /usr/lib/uwtexec something
exec -a /usr/bin/curl /usr/bin/curl.anondist-orig something
I.e. torsocks does not get prepeneded. curl gets run as is. No stream isolation. Local connections unhindered. Same effect as running curl if uwt wasn’t installed.
/usr/bin/curl.anondist-orig is the real curl binary. I.e. No stream isolation. Local connections unhindered. Same effect as running curl if uwt wasn’t installed.
Running /usr/bin/curl.anondist-orig directly circumvents all the uwt logic.
I more question
curl
can be run from user clearnet
without appending .anondist-org
(works)
Should users be warned not to do this even if it seems to works?
Warn against what?
- It’s still torified - we could even call this a bug?
- It’s to be expected to be using clearnet when using Whonix-Gateway and logging in at user
clearnet
.
- It’s not something happening by accident.
- We don’t document this light heartily.
.
clearnet@host:/home/user$ uwtwrapper_verbose=1 curl https://check.torproject.org
exec torsocks /usr/lib/uwtexec https://check.torproject.org
exec -a /usr/bin/curl /usr/bin/curl.anondist-orig https://check.torproject.org
So to reach actual clearnet, one still has to disable uwtrapper(s).
When using user clearnet
on Whonix-Gateway and it’s expected to be reaching clearnet.