No-op refactoring of VPN lockdown status check.
Currently, if VPN lockdown is disabled, the blocking judgement
inside VPN will return false immediately. It will make
ConnectivityService hard to check blocked status by a given
VPN lockdown status.
Thus, move this check into ConnectivityService and check it
externally.
Bug: 117814902
Test: 1. manual test with 3rd-party vpn app
2. runtest frameworks-net
Change-Id: Ia8319b1a1a12f1058c24badf2431f2ec69bc78e7
diff --git a/services/core/java/com/android/server/connectivity/Vpn.java b/services/core/java/com/android/server/connectivity/Vpn.java
index 48082b6..b7ed2f9 100644
--- a/services/core/java/com/android/server/connectivity/Vpn.java
+++ b/services/core/java/com/android/server/connectivity/Vpn.java
@@ -381,6 +381,15 @@
}
/**
+ * Check whether to prevent all traffic outside of a VPN even when the VPN is not connected.
+ *
+ * @return {@code true} if VPN lockdown is enabled.
+ */
+ public boolean getLockdown() {
+ return mLockdown;
+ }
+
+ /**
* Checks if a VPN app supports always-on mode.
*
* In order to support the always-on feature, an app has to
@@ -1533,17 +1542,15 @@
}
/**
- * @return {@code true} if {@param uid} is blocked by an always-on VPN.
- * A UID is blocked if it's included in one of the mBlockedUsers ranges and the VPN is
- * not connected, or if the VPN is connected but does not apply to the UID.
+ * @param uid The target uid.
*
+ * @return {@code true} if {@code uid} is included in one of the mBlockedUsers ranges and the
+ * VPN is not connected, or if the VPN is connected but does not apply to the {@code uid}.
+ *
+ * @apiNote This method don't check VPN lockdown status.
* @see #mBlockedUsers
*/
public synchronized boolean isBlockingUid(int uid) {
- if (!mLockdown) {
- return false;
- }
-
if (mNetworkInfo.isConnected()) {
return !appliesToUid(uid);
} else {