ACW in Whonix-appvm doesnt save configurations

If you choose to connect through obfs4 or obfs3 or customize it manually , Tor wont connect back to that but it will always keep goes back to the default settings which is connect to obfs4, but not obfs3 or …etc.

and by that leading as well to:


1 Like

ACW creates a Tor config file. /usr/local/etc/torrc.d/40_tor_control_panel.conf

cat /usr/local/etc/torrc.d/40_tor_control_panel.conf

This file persists after reboot and settings there don’t change after reboot?

What you mean, when you start ACW again, you would expect that the settings from

  • a) last use of ACW, or
  • b) from what is in /usr/local/etc/torrc.d/40_tor_control_panel.conf at the next start of ACW should be the ones that ACW

should show when you start it again?

//cc @troubadour @iry

i meant if u reboot the system (gw-appvm) , ACW will go back to “obfs4 recommended” , though i have chosen before that obfs3.

so its better to keep the settings that the user made even after reboot.

i thinks its B

1 Like

The setting remains unchanged in /usr/local/etc/torrc.d/40_tor_control_panel.conf so Tor’s config doesn’t get actually changed back. ACW was thought of being constantly rerun, I guess.

Nonetheless, I think it’s a good idea. If this is doable and someone willing to implement it, that would be amazing!

1 Like