+6
−2
Loading
Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more
Allow attaching an SA to an xfrm interface id after the creation of the SA, so that tasks such as keying which must be done as the SA is created, can remain separate from the decision on how to route traffic from an SA. This permits SA creation to be decomposed in to three separate steps: 1) allocation of a SPI 2) algorithm and key negotiation 3) insertion into the data path Signed-off-by:Nathan Harold <nharold@google.com> Signed-off-by:
Steffen Klassert <steffen.klassert@secunet.com> (cherry picked from commit 5baf4f9c0035f3e33bb693a1a1e87599f6e804e6) Signed-off-by:
Benedict Wong <benedictwong@google.com> Bug: 113046120 Change-Id: I45a4bf725f3b8eaa8dae3266f9c411febb4c8720