@madcoder@infosec.exchange cover
@madcoder@infosec.exchange avatar

madcoder

@[email protected]

present: security, memory-safety wizard, Memory Integrity Enforcement | past: GCD, synchro, objc_direct, perf… | timeless: 🇫🇷 snark

This profile is from a federated server and may be incomplete. View on remote instance

@tante@tldr.nettime.org avatar tante , to random

This whole "OpenClaw" thing has made me very angry and I wrote a bit about the why. It's not that "it's AI": It is the way that kind of project invalidates decades of work and care in free software. "AI" software isn't just careless, it is actively rejecting responsibility and care.

https://tante.cc/2026/02/14/diffusion-of-responsibility/

madcoder ,
@madcoder@infosec.exchange avatar

@tante @joe I mean we were just getting rid of memory unsafety — kinda — and we invented a better idiot.

@fay59@tech.lgbt avatar fay59 , to random

RE: https://mastodon.social/@wingo/116039914443435315

This one is a classic and it’s wild because what behavior is undefined? The compiler’s? The newline at the end of a file does not have behavior!

madcoder ,
@madcoder@infosec.exchange avatar

@siguza @fay59 @thephd these compilers don’t even support c99 if they even support c89 so surely that’s not why it has to stay. Chances are no one cares :)

@madcoder@infosec.exchange avatar madcoder , to random
@madcoder@infosec.exchange avatar madcoder , to random

kalloc_type was really only the fist step, of a much larger protection.

We call it Memory Integrity Enforcement.

https://security.apple.com/blog/memory-integrity-enforcement/

@madcoder@infosec.exchange avatar madcoder , to random

I'm so glad we made this available for everyone, this is just an insane feature, I'm using it right now and I feel invicible.