Add clarifying comments on for IPsec forward policies

This change adds clarifying comments for the usage of the forward
policies in IPsec, and corrects a comment to properly specify the
permissions allowed.

Bug: 185495453
Test: Comment-only changes
Change-Id: I6d36522c344c41b0ebd90d46b216d115b678dd31
This commit is contained in:
Benedict Wong
2021-05-10 18:26:02 -07:00
parent 908d34edcb
commit 47b528cfe7

View File

@@ -1112,7 +1112,7 @@ public class IpSecService extends IIpSecService.Stub {
case IpSecManager.DIRECTION_IN: case IpSecManager.DIRECTION_IN:
return; return;
case IpSecManager.DIRECTION_FWD: case IpSecManager.DIRECTION_FWD:
// Only NETWORK_STACK or PERMISSION_NETWORK_STACK allowed to use forward policies // Only NETWORK_STACK or MAINLINE_NETWORK_STACK allowed to use forward policies
PermissionUtils.enforceNetworkStackPermission(mContext); PermissionUtils.enforceNetworkStackPermission(mContext);
return; return;
} }
@@ -1358,6 +1358,16 @@ public class IpSecService extends IIpSecService.Stub {
ikey, ikey,
0xffffffff, 0xffffffff,
resourceId); resourceId);
// Add a forwarding policy on the tunnel interface. In order to support forwarding
// the IpSecTunnelInterface must have a forwarding policy matching the incoming SA.
//
// Unless a IpSecTransform is also applied against this interface in DIRECTION_FWD,
// forwarding will be blocked by default (as would be the case if this policy was
// absent).
//
// This is necessary only on the tunnel interface, and not any the interface to
// which traffic will be forwarded to.
netd.ipSecAddSecurityPolicy( netd.ipSecAddSecurityPolicy(
callerUid, callerUid,
selAddrFamily, selAddrFamily,