diff options
| author | Martin Willi <martin@revosec.ch> | 2015-02-05 09:13:57 +0100 |
|---|---|---|
| committer | Martin Willi <martin@revosec.ch> | 2015-02-19 11:29:07 +0100 |
| commit | 970378c557412710c01f3100d6f8ffb380e853a3 (patch) | |
| tree | 21c65c9573dc1870d08a59d42809a4002a3386cc /src/libcharon/plugins/resolve/resolve_handler.c | |
| parent | 875f7be5fcc85b863fa79edca529a88485aecd0f (diff) | |
| download | strongswan-970378c557412710c01f3100d6f8ffb380e853a3.tar.bz2 strongswan-970378c557412710c01f3100d6f8ffb380e853a3.tar.xz | |
libtls: Don't send TLS close notifies in EAP after application succeeds
With the introduction of PT-TLS, we started sending TLS close notifies after
the application layer completes (7bbf7aa9). While this makes sense for TCP based
transports, it is not required in EAP methods. In EAP, handshake completion
can be directly signaled using the outer EAP-SUCCESS message. This also saves
one round-trip in the EAP exchange.
Windows 7/8 does not seem to like TLS close notifies at all in EAP, and either
stalls (EAP-TTLS) or disconnects (PEAP).
Fixes #556.
Diffstat (limited to 'src/libcharon/plugins/resolve/resolve_handler.c')
0 files changed, 0 insertions, 0 deletions