Disallow Reserved SPI Allocation
Disallow the allocation of SPIs in the range reserved for future use by RFC 4303. Bug: 77205120 Test: runtest frameworks-net Merged-In: I05e26ed34b5871f1a07d5bd7b58b79a64cd74b67 Change-Id: I05e26ed34b5871f1a07d5bd7b58b79a64cd74b67 (cherry picked from commit 7f606ee8e57d9d8b7c5d0cb2a78421aa02efb385)
This commit is contained in:
committed by
Benedict Wong
parent
ad2615cae5
commit
1b88f0e6ab
@@ -274,7 +274,8 @@ public final class IpSecManager {
|
||||
*
|
||||
* @param destinationAddress the destination address for traffic bearing the requested SPI.
|
||||
* For inbound traffic, the destination should be an address currently assigned on-device.
|
||||
* @param requestedSpi the requested SPI, or '0' to allocate a random SPI
|
||||
* @param requestedSpi the requested SPI, or '0' to allocate a random SPI. The range 1-255 is
|
||||
* reserved and may not be used. See RFC 4303 Section 2.1.
|
||||
* @return the reserved SecurityParameterIndex
|
||||
* @throws {@link #ResourceUnavailableException} indicating that too many SPIs are
|
||||
* currently allocated for this user
|
||||
|
||||
Reference in New Issue
Block a user