Post B4oGRJGwj7hQMitAZM by lethalbit@chaos.social
 (DIR) More posts by lethalbit@chaos.social
 (DIR) Post #B4oGO0y6K9PajCVEsC by lethalbit@chaos.social
       0 likes, 0 repeats
       
       It's a cool feeling:tm: when your code breaks because an API changed due to fixing a CVE.Even in Rust you can accidentally rely on unsound behaviour, oops, lol.
       
 (DIR) Post #B4oGRJGwj7hQMitAZM by lethalbit@chaos.social
       0 likes, 0 repeats
       
       (For reference it was CVE-2025-64345)
       
 (DIR) Post #B4oH14ONWnwmdmPuS0 by ddr@pony.social
       0 likes, 0 repeats
       
       @lethalbit Hmm. Interesting - seems like a straight-forward fix, at least!It's inconvenient, but perhaps better than what I feel would be the C++ equivalent of saying "well don't do that if it causes problems"?