10
9
Fork
You've already forked linux-app
14

kill switch #187

Closed
opened 2019年08月29日 12:44:59 +02:00 by efef · 7 comments
efef commented 2019年08月29日 12:44:59 +02:00 (Migrated from github.com)
Copy link

design kill-switch to avoid leaking when eduVPN is down

design kill-switch to avoid leaking when eduVPN is down
efef commented 2020年01月14日 12:15:44 +01:00 (Migrated from github.com)
Copy link
maybe do something like: https://github.com/ProtonVPN/protonvpn-cli-ng/blob/master/USAGE.md#kill-switch
gijzelaerr commented 2020年05月25日 14:06:16 +02:00 (Migrated from github.com)
Copy link

I would say this is a 'nice to have', and should not block the 2.0 release.

I would say this is a 'nice to have', and should not block the 2.0 release.
jwijenbergh commented 2022年02月17日 16:58:29 +01:00 (Migrated from github.com)
Copy link

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?
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?
gijzelaerr commented 2022年02月18日 09:32:59 +01:00 (Migrated from github.com)
Copy link

ok agreed, lets postpone this to a future release, then we decide if we drop the plan or not.

ok agreed, lets postpone this to a future release, then we decide if we drop the plan or not.
jwijenbergh commented 2022年06月23日 10:18:00 +02:00 (Migrated from github.com)
Copy link

Maybe we can document the steps that an user should take to enable a killswitch manually

Maybe we can document the steps that an user should take to enable a killswitch manually
jwijenbergh commented 2023年03月06日 16:11:15 +01:00 (Migrated from github.com)
Copy link

We should document how to do this but not implement it in core IMO

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

This has been open too long and I am not sure how to even begin documenting this
Sign in to join this conversation.
No Branch/Tag specified
master
upstream-deb
openvpn-persistent
1.x
4.7.2
4.7.1
4.7.0
4.6.0
4.5.1
4.5.0
4.4.99.0
4.4.0
4.3.1
4.3.0
4.2.99.1
4.2.99.0
4.2.1
4.2.0
4.1.99.0
4.1.3
4.1.2
4.1.1
4.1.0
3.1.1
4.0.1
4.0.0
pr-3.3.1
pr-3.3.0
pr-3.2.0
3.1.0
3.0.0
2.2.1
2.2.0
2.1.0
2.0.0
1.1
1.0.3
1.0.2
1.0.1
1.0rc17
1.0rc16
1.0rc15
1.0rc14
1.0rc13
1.0rc12
1.0rc11
1.0rc10
1.0rc9
1.0rc8
1.0rc7
1.0rc6
1.0rc5
1.0rc4
1.0rc3
1.0rc2
1.0rc1
0.8
0.7.2
0.7.1
0.7
0.6.1
0.6
0.5.1
0.5
0.3
0.2.1
0.2
0.1.1
0.1
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
eduVPN/linux-app#187
Reference in a new issue
eduVPN/linux-app
No description provided.
Delete branch "%!s()"

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?