aboutsummaryrefslogtreecommitdiffstats
path: root/src/libstrongswan/crypto/diffie_hellman.c
diff options
context:
space:
mode:
authorTobias Brunner <tobias@strongswan.org>2014-10-16 16:16:48 +0200
committerTobias Brunner <tobias@strongswan.org>2014-12-05 10:12:46 +0100
commit02df52fd2b557ddcecdf250ecb7f32b2c716ebc8 (patch)
treedbc0d603742b8f3df162d546124b54cf65d36689 /src/libstrongswan/crypto/diffie_hellman.c
parentbf5d0693efe8aca8c1b87457ed2da322d72a23fa (diff)
downloadstrongswan-02df52fd2b557ddcecdf250ecb7f32b2c716ebc8.tar.bz2
strongswan-02df52fd2b557ddcecdf250ecb7f32b2c716ebc8.tar.xz
unity: Only do narrowing of responder's TS if we received 0.0.0.0/0
iOS and Mac OS X clients establish individual IPsec SAs for the traffic selectors received in Split-Include attributes (might have been different in earlier releases). If we return 0.0.0.0/0 as TSr that either results in a bunch of Quick Mode exchanges (for each TS), or with the latest client releases an error notify (ATTRIBUTES_NOT_SUPPORTED). We also can't install the IPsec SA with all configured subnets as that would cause conflicts if the client later negotiates SAs for other subnets, which iOS 8 does based on traffic to such subnets. For Shrew and the Cisco client, which propose 0.0.0.0/0, we still need to override the narrowed TS with 0.0.0.0/0, as they otherwise won't accept the Quick Mode response. Likewise, we also have to narrow the TS before installing the IPsec SAs and policies. So we basically have to follow the client's proposal and only modify TSr if we received 0.0.0.0/0. Since we don't get the original TS in the narrow hook we handle the inbound QM messages and make note of IKE_SAs on which we received a TSr of 0.0.0.0/0. Fixes #737.
Diffstat (limited to 'src/libstrongswan/crypto/diffie_hellman.c')
0 files changed, 0 insertions, 0 deletions