Conversation

Notices

1. Alex Gleason (alex@gleasonator.com)'s status on Wednesday, 13-Sep-2023 00:14:03 JST Alex Gleason
   Looks like Chrome has a remote code execution vulnerability. Aka viewing a particular image in the browser can give an attacker access to your whole computer. Upgrade now.
   
   https://www.timesnownews.com/technology-science/update-now-critical-google-chrome-flaw-exploited-article-103597437
   • Holly Jolly D-Droid (d-droid@poa.st)'s status on Wednesday, 13-Sep-2023 00:14:02 JST Holly Jolly D-Droid

     in reply to
     How the fuck, how is current coding so bad.
   • PunishedD (punishedd@poa.st)'s status on Wednesday, 13-Sep-2023 00:14:02 JST PunishedD

     in reply to

     • Holly Jolly D-Droid
     @D-Droid @alex That's what happens when you move away from jpg, gif, and png. WebP was a compromise with Satan and now the harvest is being reaped.
     xianc78 likes this.
   • xianc78@gameliberty.club's status on Wednesday, 13-Sep-2023 00:14:52 JST xianc78

     in reply to

     • teknomunk

     @teknomunk @alex Wrong link.
     https://librewolf.net/

   • teknomunk (teknomunk@apogee.polaris-1.work)'s status on Wednesday, 13-Sep-2023 00:14:54 JST teknomunk

     in reply to
     @alex
     
     Yes, update now: https://www.mozilla.org/en-US/firefox/new/
     Disinformation Purveyor :verified_think: likes this.
   • Tadano ❄️🎅 (tadano@amala.schwartzwelt.xyz)'s status on Wednesday, 13-Sep-2023 00:33:04 JST Tadano ❄️🎅

     in reply to
     @alex WebP haters vindicated :gilliathgang:
     Disinformation Purveyor :verified_think: likes this.
   • Holly Jolly D-Droid (d-droid@poa.st)'s status on Wednesday, 13-Sep-2023 03:44:00 JST Holly Jolly D-Droid

     in reply to

     • Holly Jolly D-Droid
     It's google so that's most of the reason but holy shit.
     How does google still operate with consistent quality this bad
     Machismo repeated this.
   • :niggy: (niggy@poa.st)'s status on Wednesday, 13-Sep-2023 03:44:00 JST :niggy:

     in reply to

     • Holly Jolly D-Droid

     the code bases are massive, 10s of millions of lines + all the 3rd party libraries, and these bugs are tiny and very hard to find. these are the kind of mistakes that cause memory corruption exploits:

     • indexing an array at 1 instead of 0
     • freeing an object, then using that object somewhere else
     • freeing an object twice

     these bugs are rarely even found by humans, but automated fuzzing. it’ll find the most obscure complicated edge-cases that cause these conditions, which a human can’t find by reading the code