Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | libtls: Don't send TLS close notifies in EAP after application succeeds | Martin Willi | 2015-02-19 | 1 | -1/+3 |
| | | | | | | | | | | | | | 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. | ||||
* | Implemented TLS session resumption both as client and as server | Martin Willi | 2011-12-31 | 1 | -2/+2 |
| | |||||
* | Check if the application layer has completed successfully | Martin Willi | 2010-08-24 | 1 | -0/+7 |
| | |||||
* | Implemented TLS Alert handling | Martin Willi | 2010-08-23 | 1 | -5/+6 |
| | |||||
* | added generic TLS application data handler and specific EAP-TTLS instantiation | Andreas Steffen | 2010-08-12 | 1 | -1/+4 |
| | |||||
* | Moved TLS stack to its own library | Martin Willi | 2010-08-03 | 1 | -0/+77 |