Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
is used.
|
|
|
|
|
|
|
|
config requests.
|
|
|
|
|
|
|
|
enforce on the inbound side.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Windows again
|
|
|
|
|
|
|
|
series of MATCHes that are ORed.
|
|
|
|
any flag" is generally what we want.
|
|
|
|
|
|
|
|
|
|
|
|
(thanks JG@DCVC!), and clean up some cruft in Network.
|
|
item presented to controller by nodes (to facilitate future meshiness).
|
|
since they will need them to push auth for multicast stuff, (2) added a bunch of rate limit circuit breakers for anti-DOS, (3) cleanup.
|
|
do not handle OK packets we did not expect. This hardens up a few potential edge cases around security, since such messages might be used to e.g. pollute a cache and DOS under certain conditions.
|
|
since we could get pushed one that is newer.
|
|
REDIRECT behavior and semantics.
|
|
|
|
|