Xe :verified:@cadey@pony.social
"No way to prevent this" says users of only programming language where this regularly happens
Xe :verified:@cadey@pony.social
Xe :verified:@cadey@pony.social
the syslog() function in glibc has a buffer overflow that lets attackers get root. it's had it SINCE FUCKING 1993. FOR MY ENTIRE TIME ON THIS PLANET.
When will enough be fucking enough and we ban the writing of new programs in C from an industry standards level?
Xe :verified:@cadey@pony.social
When will us fricking fricks learn that our actions have consequences?
Xe :verified:@cadey@pony.social
Ideally, I'd like to see libc get ported to another more sane programming language, but that take would get me pilloried by neckbeards that insist that C is possible to write safely.
At least I don't have to be pager bitch for THIS time when the entire internet broke due to C.
0xC0DEC0DE07E9@c0dec0dec0de@hachyderm.io
@cadey@pony.social it’s possible to write C safely like it’s possible for observable size objects to quantum tunnel (teleport spontaneously): the math allows for it, but the likelihood is insanely low and gets lower the larger the thing is.