… | |
… | |
13 | TODO: socket prepare callbacks, can they easily signal failure as well? |
13 | TODO: socket prepare callbacks, can they easily signal failure as well? |
14 | |
14 | |
15 | TODO: Олег Г <verdrehung@gmail.com>, empty A record response causes |
15 | TODO: Олег Г <verdrehung@gmail.com>, empty A record response causes |
16 | AnyEvent::resolve_sockaddr to eventually call pack_sockaddr with undef - |
16 | AnyEvent::resolve_sockaddr to eventually call pack_sockaddr with undef - |
17 | broken dns server, but maybe improve the response. |
17 | broken dns server, but maybe improve the response. |
18 | |
18 | |
|
|
19 | 7.16 Fri Jul 19 18:00:21 CEST 2019 |
|
|
20 | - add ffdhe group dh parameters from RFC 7919, and use ffdhe3072 |
|
|
21 | as new default, instead of schmorp1539. |
19 | - AnyEvent::Log did not reassess logging status of |
22 | - AnyEvent::Log did not reassess logging status of |
20 | AnyEvent::Log::logger's when contexts were changed with |
23 | AnyEvent::Log::logger's when contexts were changed with |
21 | ->attach/detach/slaves, causing them to not log even though a |
24 | ->attach/detach/slaves, causing them to not log even though a |
22 | recent attach should have caused them to log. |
25 | recent attach should have caused them to log. |
23 | - added some more logging configuration examples. |
26 | - added some more logging configuration examples. |
|
|
27 | - mention RFC 8482 in AnyEvent::DNS. |
24 | |
28 | |
25 | 7.15 Tue Feb 26 03:07:42 CET 2019 |
29 | 7.15 Tue Feb 26 03:07:42 CET 2019 |
26 | - INCOMPATIBLE CHANGE: AnyEvent::Handle's tls_detect documentation gave |
30 | - INCOMPATIBLE CHANGE: AnyEvent::Handle's tls_detect documentation gave |
27 | separate major and minor versions, while code passed only a single |
31 | separate major and minor versions, while code passed only a single |
28 | value. This version follows the documentation and now passes separate |
32 | value. This version follows the documentation and now passes separate |