chiark / gitweb /
server/{keyexch,peer}.c: Maybe key-exchange messages come out of the blue.
authorMark Wooding <mdw@distorted.org.uk>
Mon, 4 Sep 2017 00:15:35 +0000 (01:15 +0100)
committerMark Wooding <mdw@distorted.org.uk>
Sat, 16 Jun 2018 18:13:41 +0000 (19:13 +0100)
commitf6994bd047a35b06aa7aed3c59487000abec2325
tree42492911ade38e8ad3f92900c80044b7b360c09f
parenta5c4a56a64e127a1a5e5d436cf52df1e7a96eb33
server/{keyexch,peer}.c: Maybe key-exchange messages come out of the blue.

Don't insist in `p_read' that key-exchange messages always come from a
known address.  Instead, leave this to `kx_message' to sort out.

This involves a change of interface to `kx_message', passing in the
sender address, and passing out an indication as to whether the address
was recognized.  It also means that there's a little extra fancy
footwork involved because `kx_message' might not have a key-exchange
control block conveniently to hand.
server/keyexch.c
server/peer.c
server/tripe.h