New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 881107 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 873123
Owner:
Closed: Sep 6
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Android Always-On VPN can be turned off from Chrome Settings

Reported by f5mobile...@gmail.com, Sep 5

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS aarch64 10575.58.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

Steps to reproduce the problem:
1. Turn On Always-On VPN from within Android subsystem (settings) running on ChromeOS. 
2. Let the VPN client establish VPN connection.
3. Once connected goto ChromeOS Settings --> Network --> VPN.
4. Disconnect button is available to stop always-on VPN.
5. This defeats the very purpose of ALWAYS-ON VPN.

What is the expected behavior?
- VPN established through Android subsystem creates a tunnel for the entire Chromebook and passes all traffic through the tunnel until specified otherwise. Applies to traffic generated by android as well as chrome native apps.
- So Always-On VPN when enabled through Android settings should be respected by ChromeOS settings as well.
- Once always-on VPN is ON there should be NO means for the user to disconnect the VPN.

What went wrong?
- Users are now provided with disconnect VPN functionality within Chrome settings
- Disconnect should be DISABLED when always-on is ON

Did this work before? No 

Chrome version: 67.0.3396.99  Channel: n/a
OS Version: 10575.58.0
Flash Version:
 
Cc: bartfab@chromium.org
Components: Platform>Apps>ARC
Owner: phweiss@chromium.org
Status: Assigned (was: Unconfirmed)
Philipp, I think you were working on Always-On VPN?
Mergedinto: 873123
Status: Duplicate (was: Assigned)
Yes, I'm working on applying the Android setting to Chrome traffic as well, and I discovered the same problem with the disconnect button. The fix is currently planned for Chrome version 71.
Thank you. Will wait for this fix in version 71.
Cc: elijahtaylor@chromium.org
+Elijah, FYI. We briefly talked about the possibility of punting this to M72 yesterday. As you see, there is external customer demand. Pending any catastrophic road blocks, we should keep this feature on track for M71.

Sign in to add a comment