this post was submitted on 15 Feb 2024
112 points (97.5% liked)

Programming

17114 readers
318 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] Corngood@lemmy.ml 13 points 7 months ago (1 children)

http://freenginx.org/pipermail/nginx/2024-February/000007.html

The most recent "security advisory" was released despite the fact that the particular bug in the experimental HTTP/3 code is expected to be fixed as a normal bug as per the existing security policy, and all the developers, including me, agree on this.

And, while the particular action isn't exactly very bad, the approach in general is quite problematic.

I read something about this the other day, but I'm having trouble wrapping my head around it.

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-24989 https://my.f5.com/manage/s/article/K000138444 https://mailman.nginx.org/pipermail/nginx-announce/2024/NW6MNW34VZ6HDIHH5YFBIJYZJN7FGNAV.html

This seems to have the best discussion I've found:

https://news.ycombinator.com/item?id=39373612

[โ€“] mcherm@lemmy.world 2 points 7 months ago