Feature request: Kill switch

Suggestions/comments/criticisms are welcome here


Posts: 1
Joined: Sat Mar 03, 2018 8:17 am

Post by stackundertheother » Sat Mar 03, 2018 8:31 am
I'm new to the forum so this has probably been requested before but is there any plans on adding a kill switch in the future?


User avatar
Posts: 1988
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Tue Mar 06, 2018 3:28 pm
Hi stackundertheother,

Thanks for the feedback. I'm afraid it's not something we currently plan on adding, however the following guide walks through how to add a Kill Script type feature to Viscosity via the use of Viscosity's scripting support:
https://www.sparklabs.com/support/kb/ar ... fic-leaks/

James Bekkema
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs


Posts: 2
Joined: Wed Apr 22, 2015 4:46 am

Post by TCB13 » Mon May 07, 2018 12:36 am

I don't think the script is enough. Viscosity should be able to operate in a way where it automatically disables all network traffic until a VPN connection is established.

When I say "disables all network traffic" I'm not talking about what happens on the script. It should be not about turning interfaces down, it should somehow block all traffic in a similar way that the littlesnitch/hands off firewalls are able to do without bringing the interfaces down (maybe unroutable default route?)

Use case example: someone always uses a VPN to go online. Right now between the time the computer starts / comes back from suspended state and the users connects to some VPN multiple Apps are able to connect to the internet and leak data around. This is why this feature is needed.

Thank you.
3 posts Page 1 of 1