Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
addresses for now)
|
|
|
|
confuse remotes before and after reconfiguration"
This reverts commit 4475652054616ded16485341b081abf42cc6c08e.
|
|
remotes before and after reconfiguration
|
|
|
|
functions
|
|
|
|
|
|
|
|
Not a single implementation was using them...
|
|
|
|
invalid aliasing (hopefully)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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
|
|
|