The whonix instructions for corridor don’t work for Qubes 4.2. If anyone can get corridor working for qubes 4.2 I am willing to pay 75$
1 Like
Try Qubes, please. (And check Pitfalls.)
1 Like
The corridor package in the Whonix repository is outdated.
I set up a DispVM named sys-corridor using a minimal Debian template and installed all the necessary dependencies.
The output from iptables matches the rules listed on the Whonix page. However, corridor-data returns the following errors:
corridor-data[11350]: socat[11350] E connect, AF=1 "/var/run/tor/control", 22): Connection refused
corridor-data[11357]: socat[11357] E connect, AF=1 "/var/run/tor/control", 22): Connection refused
corridor-data[11399]: socat[11399] E connect, AF=1 "/var/run/tor/control", 22): Connection refused
Additionally, there is no /var/log/syslog available.
I initially thought the issue might be related to iptables using nftables, so I switched to legacy iptables, but the problem persists.
I noticed that the corridor package in the Whonix repository is outdated compared to the original repository on Rustybird’s GitHub, which has several commits ahead. @adrelanos, are you aware of this?
I’ve updated to the latest commits, but it’s still not working. There are no errors, and everything appears to be fine, yet it still doesn’t function. I also switched to standalonevm, but there was no change in the outcome.