- 06 Jul, 2020 2 commits
-
-
Evan Hunt authored
'ddns-confgen' is now an alias for 'tsig-keygen', rather than the other way around.
-
Mark Andrews authored
-
- 02 Jul, 2020 2 commits
-
-
Michał Kępień authored
-
Evan Hunt authored
-
- 01 Jul, 2020 5 commits
-
-
Evan Hunt authored
-
Ondřej Surý authored
-
Witold Krecicki authored
-
Ondřej Surý authored
-
Evan Hunt authored
-
- 30 Jun, 2020 1 commit
-
-
Matthijs Mekking authored
-
- 29 Jun, 2020 1 commit
-
-
Evan Hunt authored
-
- 26 Jun, 2020 1 commit
-
-
Evan Hunt authored
CHANGES notes were accidentally omitted from the previous merge.
-
- 25 Jun, 2020 2 commits
-
-
Evan Hunt authored
such addresses broke some YAML parsers.
-
Mark Andrews authored
-
- 23 Jun, 2020 2 commits
-
-
Ondřej Surý authored
-
Mark Andrews authored
-
- 22 Jun, 2020 1 commit
-
-
Ondřej Surý authored
-
- 19 Jun, 2020 2 commits
-
-
Evan Hunt authored
-
Mark Andrews authored
-
- 18 Jun, 2020 5 commits
-
-
Michał Kępień authored
-
Mark Andrews authored
-
Michał Kępień authored
-
Mark Andrews authored
-
Mark Andrews authored
-
- 17 Jun, 2020 1 commit
-
-
Ondřej Surý authored
-
- 11 Jun, 2020 1 commit
-
-
Mark Andrews authored
-
- 10 Jun, 2020 1 commit
-
-
Witold Krecicki authored
There's a possibility of a race in TCP accepting code: T1 accepts a connection C1 T2 accepts a connection C2 T1 tries to accept a connection C3, but we hit a quota, isc_quota_cb_init() sets quota_accept_cb for the socket, we return from accept_connection T2 drops C2, but we race in quota_release with accepting C3 so we don't see quota->waiting is > 0, we don't launch the callback T1 accepts a connection C4, we are able to get the quota we clear the quota_accept_cb from sock->quotacb T1 drops C1, tries to call the callback which is zeroed, sigsegv.
-
- 05 Jun, 2020 3 commits
-
-
Witold Krecicki authored
-
Mark Andrews authored
-
Mark Andrews authored
-
- 04 Jun, 2020 5 commits
-
-
Mark Andrews authored
-
Mark Andrews authored
-
Witold Krecicki authored
With netmgr we're creating separate socket for each IPv6 interface, just as with IPv4 - update documentation accordingly.
-
Michal Nowak authored
-
Ondřej Surý authored
-
- 03 Jun, 2020 3 commits
-
-
Ondřej Surý authored
-
Ondřej Surý authored
-
Ondřej Surý authored
-
- 02 Jun, 2020 2 commits
-
-
Matthijs Mekking authored
When creating the successor, the current active key (predecessor) should change its goal state to HIDDEN. Also add two useful debug logs in the keymgr_key_rollover function.
-
Matthijs Mekking authored
The logic in `keymgr_key_has_successor(key, keyring)` is flawed, it returns true if there is any key in the keyring that has a successor, while what we really want here is to make sure that the given key has a successor in the given keyring. Rather than relying on `keymgr_key_exists_with_state`, walk the list of keys in the keyring and check if the key is a successor of the given predecessor key.
-