Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-04-21 13:37:30 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 91

Update incorrect sentence on risk (#42454)

Browse source 
Fixing non-sense statement "A vulnerability in a shared library can
affect dozens of applications, but only if you know which devices have
it installed."

A vuln in a shared library affects all systems, even when you don't know
where it is installed. And THAT is the risk. Can't fix what you don't
know about.
This commit is contained in:
Dan Gordon 2026-03-26 08:19:17 -07:00 committed by GitHub
parent eb73c02737
commit 8f64ec7416
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
articles/unlocking-linux-productivity-securing-apps-and-updating-certificates.md
View file

@ -17,7 +17,7 @@ Computers are not intrinsically productive or secure. Their value comes from tru
If you manage Linux workstations, you know there's no single package format or unified app store. Debian-based systems use `apt`, Red Hat-based systems use `dnf,` and SUSE uses Zypper. Then there's Flatpak, Snap, and AppImage on top. Compare this with macOS or Windows, where software distribution is more standardized. On Linux, there's no single ecosystem, so teams that support multiple Linux distributions must manage across all of them simultaneously.
This fragmentation creates real challenges. Each package manager resolves dependencies differently. Each distribution maintains its own repositories with its own release schedules. When your team installs a library from a third-party PPA or compiles software from source, that package often falls outside any centralized tracking. A vulnerability in a shared library can affect dozens of applications, but only if you know which devices have it installed.
This fragmentation creates real challenges. Each package manager resolves dependencies differently. Each distribution maintains its own repositories with its own release schedules. When your team installs a library from a third-party PPA or compiles software from source, that package often falls outside any centralized tracking. A vulnerability in a shared library can affect dozens of applications, increasing risk if you don't know which devices have it installed.
## The software chain of trust