ouroboros/src/lib/crypt.c, branch 0.17.2

lib, ipcpd: piggyback ECDHE on flow allocation

2020-02-25T07:21:09Z

The initial implementation for the ECDHE key exchange was doing the key exchange after a flow was established. The public keys are now sent allowg on the flow allocation messages, so that an encrypted tunnel can be created within 1 RTT. The flow allocation steps had to be extended to pass the opaque data ('piggybacking'). Signed-off-by: Dimitri Staessens Signed-off-by: Sander Vrijders

build: Update copyright to 2020

2020-01-02T14:07:36Z

Signed-off-by: Dimitri Staessens Signed-off-by: Sander Vrijders

lib: Fix swapped ECDH crypt calls

2019-08-09T17:44:06Z

The client and server side were swapped. This wasn't a big issue, but now we are sure that the flow allocation response for the server has arrived at the client (packet reordering could cause the server key to arrive before the flow is allocated at the client). Signed-off-by: Dimitri Staessens Signed-off-by: Sander Vrijders

lib: Fix free in key derivation

2019-08-09T17:43:27Z

The wrong pointer was being free'd in case of a derivation error. Signed-off-by: Dimitri Staessens Signed-off-by: Sander Vrijders

lib: Add per-message encryption with OpenSSL

2019-08-03T10:10:57Z

This adds a per-message symmetric encryption using the OpenSSL library. At flow allocation, an Elliptic Curve Diffie-Hellman exchange is performed to derive a shared secret, which is then hashed using SHA3-256 to be used as a key for symmetric AES-256 encryption. Each message on an encrypted flow adds a small crypto header that includes a random 128-bit Initialization Vector (IV). If the server does not have OpenSSL enabled, the flow allocation will fail with an -ECRYPT error. Future optimizations are to piggyback the public keys on the flow allocation message, and to enable per-flow encryption that maintains the context of the encryption over multiple packets and doesn't require sending IVs. Signed-off-by: Dimitri Staessens Signed-off-by: Sander Vrijders