On Fri, 2026-10-23 at 15:44 +0200, Marius Schwarz wrote: > This may be a good starting point to reconsider handling security > differently in the light of AIs producing exploits, faster than you can > imagine.
I'd say it's rather exactly the opposite. There are so many security fixes now that it's not practical to treat them all as "special". In the past, when we got maybe one "Heartbleed" fire drill every few months, we could. Now any idiot can ask Claude to find a security vuln and slap a catchy name on it, we really can't. A few months ago we were taking special trouble to co-ordinate kernel updates with jforbes and get them pushed out quickly and update infra hosts and yadda yadda. Now we're just not because *every kernel update is a security update* and it's just not sustainable to keep doing that forever. I think this is a question of perspectives. For me and I think for releng, this is just the latest in a months-long, never-ending series of quite serious security issues found by AI. Maybe for other folks it looks somehow unique or special, but it's hard to see that from here. We did do an early F44 push to get the php update out, but F43 didn't have the karma at that point. And Kevin is on PTO, also. -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @[email protected] https://www.happyassassin.net -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
