design kill-switch to avoid leaking when eduVPN is down
kill switch #187
maybe do something like: https://github.com/ProtonVPN/protonvpn-cli-ng/blob/master/USAGE.md#kill-switch
I would say this is a 'nice to have', and should not block the 2.0 release.
It is nice to have but I see lots of problems with this
- We need root privileges in order to modify iptables/nftables rules
- Could implement a popup with password, but this is not ideal
- When to reset these rules?
- Will they be removed when the application is removed?
ok agreed, lets postpone this to a future release, then we decide if we drop the plan or not.
Maybe we can document the steps that an user should take to enable a killswitch manually
We should document how to do this but not implement it in core IMO
This has been open too long and I am not sure how to even begin documenting this
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?