this post was submitted on 07 Jun 2023
142 points (99.3% liked)

Asklemmy

43945 readers
572 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago
MODERATORS
 

What opinion just makes you look like you aged 30 years

you are viewing a single comment's thread
view the rest of the comments
[–] argv_minus_one@beehaw.org 1 points 1 year ago

Yeah, but there’s by lot more security improvement by having ability to apply fix for severe vulnerability ASAP than weakening from possible incompativilities.

Um, we're talking about undefined behavior here. That creates potential RCE vulnerabilities—the most severe kind of vulnerability. So no, a botched dynamically-linked library update can easily create a vulnerability worse than the one it's meant to fix.

Also, i wonder why i never brought it up, shared libs are shared, so you can use them across many programming languages.

Shared libraries are shared among processes, not programming languages.