Thu, 10 Sep 2020 21:58:24 +0200 util.hashes: Add SHA3 bindings
Kim Alvefur <zash@zash.se> [Thu, 10 Sep 2020 21:58:24 +0200] rev 12568
util.hashes: Add SHA3 bindings
Thu, 10 Sep 2020 21:58:24 +0200 util.hashes: Bind BLAKE2 algoritms supported by OpenSSL
Kim Alvefur <zash@zash.se> [Thu, 10 Sep 2020 21:58:24 +0200] rev 12567
util.hashes: Bind BLAKE2 algoritms supported by OpenSSL
Thu, 10 Sep 2020 21:58:25 +0200 util.hashes: Refactor PBKDF2 to deduplicate code
Kim Alvefur <zash@zash.se> [Thu, 10 Sep 2020 21:58:25 +0200] rev 12566
util.hashes: Refactor PBKDF2 to deduplicate code
Sun, 29 Nov 2020 17:58:45 +0100 util.hashes: Expose sha224 and sha384 HMAC functions
Kim Alvefur <zash@zash.se> [Sun, 29 Nov 2020 17:58:45 +0100] rev 12565
util.hashes: Expose sha224 and sha384 HMAC functions For completeness and consistency with set of plain hash functions
Sun, 29 Nov 2020 17:58:30 +0100 util.hashes: Refactor HMAC bindings (fixes #1589)
Kim Alvefur <zash@zash.se> [Sun, 29 Nov 2020 17:58:30 +0100] rev 12564
util.hashes: Refactor HMAC bindings (fixes #1589) HMAC() is deprecated As with the regular hash functions, macros like this make it awkward to apply static analysis and code formatting.
Thu, 10 Sep 2020 21:58:23 +0200 util.hashes: Refactor hash functions to use OpenSSL EVP methods (fix #1698)
Kim Alvefur <zash@zash.se> [Thu, 10 Sep 2020 21:58:23 +0200] rev 12563
util.hashes: Refactor hash functions to use OpenSSL EVP methods (fix #1698) MD5() is deprecated, but EVP_md5() is not. Functions in macros like this make it awkward to apply static analysis and code formatting.
Sun, 19 Jun 2022 19:58:12 +0200 Merge 0.12->trunk
Kim Alvefur <zash@zash.se> [Sun, 19 Jun 2022 19:58:12 +0200] rev 12562
Merge 0.12->trunk
Sun, 19 Jun 2022 19:49:32 +0200 net.unbound: Merge luaunbound and prosody defaults in absence of user config (fixes #1763) (thanks rgd) 0.12
Kim Alvefur <zash@zash.se> [Sun, 19 Jun 2022 19:49:32 +0200] rev 12561
net.unbound: Merge luaunbound and prosody defaults in absence of user config (fixes #1763) (thanks rgd) add_defaults() is supposed to merge 3 tables, the defaults in luaunbound, the defaults from prosody and any config from the prosody config file. In the case where no `unbound={}` has been in the config, it skips over the merge and returns only the prosody built-in defaults. This results in libunbound skipping reading resolv.conf and uses its default behavior of full recursive resolution. Prior to #1737 there were only two tables, the luaunbound defaults and the prosody config, where bypassing the merge and returning the former did the right thing.
Tue, 14 Jun 2022 22:06:21 +0200 mod_mam: Silence luacheck (yay warnings in CI but not locally)
Kim Alvefur <zash@zash.se> [Tue, 14 Jun 2022 22:06:21 +0200] rev 12560
mod_mam: Silence luacheck (yay warnings in CI but not locally)
Tue, 14 Jun 2022 22:03:02 +0200 mod_mam: Clarify comment (thanks chili-b)
Kim Alvefur <zash@zash.se> [Tue, 14 Jun 2022 22:03:02 +0200] rev 12559
mod_mam: Clarify comment (thanks chili-b) This was slightly inaccurate since 6e1af07921d1 because the conditions are more complicated now.
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 tip