Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Shuffle things around. Add NIST X.509 test to build. | lloyd | 2014-01-01 | 1 | -78/+0 |
| | |||||
* | Fairly huge update that replaces the old secmem types with std::vector | lloyd | 2012-05-18 | 1 | -6/+6 |
| | | | | | | using a custom allocator. Currently our allocator just does new/delete with a memset before deletion, and the mmap and mlock allocators have been removed. | ||||
* | Huge pile of post merge fixups, mtn really fucked that merge | lloyd | 2012-04-25 | 1 | -1/+1 |
| | |||||
* | Add support for TLS heartbeats (RFC 6520). Heartbeat initiations from | lloyd | 2012-04-16 | 1 | -0/+78 |
the peer are automatically responded to. TLS::Channel::heartbeat can initiate a new heartbeat if the peer allows it. Heartbeat replies are passed back to the application processing function with an Alert value of HEARTBEAT_PAYLOAD (a 'fake' value, 256, which is out of range of the valid TLS alert space), along with the sent payload. The RFC requires us to have no more than one heartbeat 'in flight' at a time, ie without getting a response (or a timeout in the case of DTLS). Currently we do not prevent an application from requesting more. |