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, 40 insertions, 0 deletions

diff --git a/src/tls/tls_heartbeats.h b/src/tls/tls_heartbeats.h
new file mode 100644
index 000000000..4fa49501b
--- /dev/null
+++ b/src/tls/tls_heartbeats.h
@@ -0,0 +1,40 @@
+/*
+* TLS Heartbeats
+* (C) 2012 Jack Lloyd
+*
+* Released under the terms of the Botan license
+*/
+
+#ifndef BOTAN_TLS_HEARTBEATS_H__
+#define BOTAN_TLS_HEARTBEATS_H__
+
+#include <botan/secmem.h>
+
+namespace Botan {
+
+namespace TLS {
+
+class Heartbeat_Message
+   {
+   public:
+      enum Type { REQUEST = 1, RESPONSE = 2 };
+
+      MemoryVector<byte> contents() const;
+
+      const MemoryRegion<byte>& payload() const { return m_payload; }
+
+      bool is_request() const { return m_type == REQUEST; }
+
+      Heartbeat_Message(const MemoryRegion<byte>& buf);
+
+      Heartbeat_Message(Type type, const byte payload[], size_t payload_len);
+   private:
+      Type m_type;
+      MemoryVector<byte> m_payload;
+   };
+
+}
+
+}
+
+#endif