this post was submitted on 16 Feb 2024
145 points (99.3% liked)

Selfhosted

39435 readers
7 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Researchers recently found a vulnerability in the way DNS resolvers handle DNSSEC validation that allow attackers to DoS resolvers with a single DNS request

https://www.theregister.com/2024/02/13/dnssec_vulnerability_internet/

It is highly recommended to upgrade your resolvers to the following versions:

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 8 months ago (5 children)

My unbound is on v1.13.1 (Raspbian) after update/upgrade. I've read it lags behind the main release by alot, should I trust the process that everything is fine.

[–] [email protected] 11 points 8 months ago (2 children)

Its up to your distros package maintainer to make the patched version available. You can find who maintains it and contact them so they are aware.

[–] [email protected] 4 points 8 months ago

Debian usually backports security fixes to older versions, so you may wanna check to Debian if they have an updated version of the package with the security fix.

This can be done by taking the CVE number related to this vulnerability and look at the package changelog.

load more comments (1 replies)
load more comments (3 replies)