Add support for TLS heartbeats (RFC 6520). Heartbeat initiations from

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.

1 files changed, 3 insertions, 0 deletions

diff --git a/src/tls/tls_record.h b/src/tls/tls_record.h
index fb27db5e2..38eae7823 100644
--- a/src/tls/tls_record.h
+++ b/src/tls/tls_record.h
@@ -46,6 +46,9 @@ class BOTAN_DLL Record_Writer
       void send(byte type, const byte input[], size_t length);
       void send(byte type, byte val) { send(type, &val, 1); }
 
+      void send(byte type, const MemoryRegion<byte>& input)
+         { send(type, &input[0], input.size()); }
+
       MemoryVector<byte> send(class Handshake_Message& msg);
 
       void send_alert(const Alert& alert);