On Thu, Aug 20, 2026 at 08:29:14PM +0000, Arnox wrote:
In this age of rampant AI and rampant AI-created malware, I was thinking about how Debian handles security updates, or more specifically, how it takes a comparatively long time to handle them. For example, I've seen one bad exploit in KDE take at least a month before it was finally pointed out to the Debian team
This doesn't sounds how Debian handles security issues, so it may be more useful to clarify what exactly happened, and whether the upstream process or the Debian process had problems.
This also got me thinking about if there is a way somehow for Debian to coordinate and collaborate better with upstream developers in order to ship even more stable packages than before.
Do you have anything specific in mind that is not already done?
I wonder if many upstream developers just don't want to get involved with pushing software to Debian these days simply because they find it too inconvenient and clunky compared to, say, Arch.
This sounds unrelated to what you discussed before. -- WBR, wRAR
signature.asc
Description: PGP signature
