<![CDATA[apparently some distros still haven’t patched copyfail]]>apparently some distros still haven’t patched copyfail

love obsession with version number stability

]]>https://board.circlewithadot.net/topic/813c417b-a875-4592-a5df-c3e2eeabaa9b/apparently-some-distros-still-haven-t-patched-copyfailRSS for NodeFri, 15 May 2026 00:22:36 GMTMon, 04 May 2026 05:00:05 GMT60<![CDATA[Reply to apparently some distros still haven’t patched copyfail on Mon, 04 May 2026 06:15:21 GMT]]>@charlotte@akko.chir.rs @ariadne@social.treehouse.systems hey imean , it was a weekend , after all

]]>https://board.circlewithadot.net/post/https://brain.worm.pink/objects/4373ad34-cb99-4149-a315-c48876b7398ahttps://board.circlewithadot.net/post/https://brain.worm.pink/objects/4373ad34-cb99-4149-a315-c48876b7398aMon, 04 May 2026 06:15:21 GMT<![CDATA[Reply to apparently some distros still haven’t patched copyfail on Mon, 04 May 2026 05:51:03 GMT]]>@ariadne by the time the vuln was published i was already running a fixed version on all my regular linux systems running community-maintained linux distros.

i am not convinced that red hat, a corporate provider of a paid distribution, was unable to provide a patch in a reasonable time frame despite employing one of the maintainers of the kernel crypto/ tree specifically credited in the af_alg.c file.

]]>https://board.circlewithadot.net/post/https://akko.chir.rs/objects/f263ea1b-66be-4133-81d7-1ac08557dfdahttps://board.circlewithadot.net/post/https://akko.chir.rs/objects/f263ea1b-66be-4133-81d7-1ac08557dfdaMon, 04 May 2026 05:51:03 GMT<![CDATA[Reply to apparently some distros still haven’t patched copyfail on Mon, 04 May 2026 05:42:53 GMT]]>@charlotte it is because the disclosure has been a shit show.

]]>https://board.circlewithadot.net/post/https://social.treehouse.systems/users/ariadne/statuses/116514709424987827https://board.circlewithadot.net/post/https://social.treehouse.systems/users/ariadne/statuses/116514709424987827Mon, 04 May 2026 05:42:53 GMT