* Close the new connection if Zebra unexpectedly generates a duplicate random nonce * Add a missing test module comment * Avoid peer attacks that replay self-connection nonces to manipulate the nonce set (needs tests) * Add a test that makes sure network self-connections fail * Log an info level when self-connections fail (this should be rare) * Just use plain blocks for mutex critical sections * Add a missing space |
||
|---|---|---|
| .. | ||
| proptest-regressions | ||
| src | ||
| tests | ||
| Cargo.toml | ||