Bug#1038243: unbound: error log flooding when unbound is configured with a DNS over TLS upstream server

2023-09-17 Thread Michael Tokarev
Speaking of stable p-u, it'd be interesting to fix the two new bugs in there too, which I haven't noticed before your friendly ping (apparently something's wrong with my subscription to bugs) -- #1051817 and #1051818. Should be easy to fix, lemme take a look.. /mjt

Bug#1038243: unbound: error log flooding when unbound is configured with a DNS over TLS upstream server

2023-09-17 Thread Michael Tokarev
16.09.2023 22:34, Timo Sigurdsson wrote: Dear maintainers, could you please also backport the fix for this issue to the current stable distribution via the proposed-updates channel? The next point release for bookworm is scheduled for October 7. I really hope the fix for this annoying issue

Bug#1038243: unbound: error log flooding when unbound is configured with a DNS over TLS upstream server

2023-09-16 Thread Timo Sigurdsson
Dear maintainers, could you please also backport the fix for this issue to the current stable distribution via the proposed-updates channel? The next point release for bookworm is scheduled for October 7. I really hope the fix for this annoying issue makes it into the next point release.

Bug#1038243: unbound: error log flooding when unbound is configured with a DNS over TLS upstream server

2023-07-18 Thread Timo Sigurdsson
tags 1038243 confirmed patch fixed-upstream thanks I can confirm this bug. I also stumbled over this after upgrading a machine from Bullseye to Bookworm. I can also confirm that the upstream fix (commit d7e77611) [1] on top of the unbound package currently found in Debian Bookworm, 1.17.1-2,

Bug#1038243: unbound: error log flooding when unbound is configured with a DNS over TLS upstream server

2023-06-16 Thread Wolfgang
Package: unbound Version: 1.17.1-2 Severity: important Hello, I upgraded from bullseye to bookworm and after the upgrade unbound in version 1.17.1-2 is flooding the journal with the error messages."error: could not SSL_read crypto error:0A000126:SSL routines::unexpected eof while reading“.