Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
key derivation scheme
|
|
|
|
|
|
Not setting the option produces a warning (so not having it set is deprecated
now), so we can change the default from no to yes in a few release cycles.
|
|
invalid
|
|
|
|
The monotone timestamp is near zero on linux systems, confusing fastd.
|
|
The handshakes are now schedules in a doubly-linked list that is maintained as a
part of the peer structure.
|
|
By using a global keepalive timer, the O(n) keepalive queue purge operation on
every send operation is avoided.
|
|
been established
|
|
|
|
|
|
Everything clang and GCC warn about, except GCC's missing-field-initializers
which are just stupid as they don't allow {} syntax to zero a field.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Check the length of ethernet frames, and the fastd_eth_addr_t structure must be
packed.
|
|
|
|
|
|
Without this fix, using on-establish/disestablish/verify would cause a strange
zero port when a bind with a random port was used, and a segmentation fault with
dynamic binds.
|