Hi Lena, That's great. Thanks a lot. we'll test it and keep you posted
if the issue is fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080494
Title:
Hang in Unbound 1.13.1
To manage notificat
Hi Firxiao, I created a PPA that provides 1.13.2 with the CVE fixes
here:
https://launchpad.net/~lvoytek/+archive/ubuntu/unbound-1.13.2-jammy
If you would like to install and test it, you can run the following:
sudo add-apt-repository ppa:lvoytek/unbound-1.13.2-jammy
sudo apt update
sudo apt upgr
I took a quick look into making a 1.13.2 PPA, it should be noted that
there are multiple CVEs that should be addressed in that PPA.
CVE-2024-33655 (fixed in version 1.20.0)
CVE-2023-50387 (fixed in version 1.19.1)
CVE-2023-50868 (fixed in version 1.19.1)
CVE-2022-3204 (fixed in version 1.16.3)
CVE
Hi Bryce,
Thanks a lot for your support, it looks this issue only happen in specific
situation when reload unbound, after doing a full restart for all unbound
service, we've not see the issue in last few days.
Below is core dump [1] info during the issue(there are 4 threads and the first
one wa
Firxiao, we've discussed this issue in our team call. Unfortunately,
while unbound's library binaries (libunbound8 and libunbound-dev) are in
main, the rest of its binaries (including the unbound binary itself) are
in universe. This doesn't appear to be a strong candidate for pursuing
MRE, so are
I doubt we would bump to 1.13.2 in 22.04, however we could look into
putting it into a PPA, would that work for your needs?
Like Mitchell mentioned, for SRUs it's generally required that a single
distinct patch is backported, and that there are steps identified to
reproduce it. Sounds like that m
Hi Mitchell,
Thanks a lot for your reply, It seems unbound guys didn't close the Github
issue in time, from release notes
https://www.nlnetlabs.nl/projects/unbound/download/#unbound-1-13-2 it says the
#411 had been resolved.
And Yes, I can help to test the new version.
For MRE, I've read
Hi Firxiao, it seems the issues you mentioned[0][1] doesn't have a
definitive answer if it solves the problem. Would you be willing to help
test out any changes?
Ideally we would cherry-pick the upstream changes, but at a very cursory
glance it seems a decent chunk of code was changed, so merge co
server-triage-discuss, tagging you to see if unbound is a good MRE
candidate - I see no MRE has been done in the past. I'm not sure if
there's a historical reason for that. Might be a good time to consider
MRE?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i