With the administration now recommending memory safe languages, I'm assuming the RNC platform is going to talk about preserving our god-given freedom as Americans to overwrite the stack whenever and wherever we want.
@mattblaze You'll have to pry this assembler from my cold dead hands!
@mattblaze “An unregulated memory model, being necessary for the creation of powerful systems, the right to bear pointers shall not be infringed.”
@SteveBellovin @mattblaze in a secular society the right to practice multiple indirection should always be upheld.
@SteveBellovin @mattblaze this is utterly perfect. thank you for putting this on the internet.
@SteveBellovin @mattblaze Congress shall make no law respecting the management of memory, or prohibiting the free exercise thereof
@adamshostack @SteveBellovin @mattblaze The freedom to call free() whenever is a God-given, unalienable right.
@mattblaze Duh…. We all have the right to be stupid. Some just exercise that right more than others.
@mattblaze just wait until there are recommendations wrt race conditions
@mattblaze there will be no end of accusations from them of heap grooming.
@mattblaze Do they consider Larry Flon prophet or apostate?
@mattblaze If GOTO was good enough for Jesus, then it's good enough for me.
@mattblaze and don't get them started on polymorphism.
@colinrosenthal @mattblaze that object is just a struct and could never be anything else
@mattblaze - Overwriting to start, no doubt, with the Proud Boys Stack Formation on January 6th. To be erased from the history books.

@mattblaze since I'm not seeing it on your replies already, nobody can't take away your god-given right to segfault

https://github.com/Speykious/cve-rs

GitHub - Speykious/cve-rs: Blazingly 🔥 fast 🚀 memory vulnerabilities, written in 100% safe Rust. 🦀

Blazingly 🔥 fast 🚀 memory vulnerabilities, written in 100% safe Rust. 🦀 - Speykious/cve-rs

GitHub
@mattblaze I guess this *would* be in the interest of their Russian backers.
@mattblaze Smashing The State For Fun And Profit
@mattblaze C ... was here BEFORE the Rust compiler. So you can give your heart to Ritchie. But your code, belongs, to the borrow checker!
Dev (@dev@discuss.systems)

Attached: 1 image

discuss.systems
@mattblaze And when they segfault, just say to pick yourself up by your BIOS boot-straps

@mattblaze Smashing the stack for God and country

—Phrack 49:14

@mattblaze exclusion of liability for compiler manufacturers in case of wrongful process overwrite or thread death

@mattblaze

You don't tell *me* I can't follow a null pointer. I'll follow any damn pointer I want!

Hold m'beer.

#beer #WatchThis #pointer #null #JumpToNowhere

@mattblaze If C was good enough for Jesus then it's good enough for me
@mattblaze reference counters and borrow checks are stealing jobs from real american garbage collectors

@mattblaze Curiously, in the 1980s, I wrote a simulator that would sometimes purposely overwrite the stack to provide multi-threading. This did not occur often enough for performance to be an issue, but it let me use the existing symbolic debuggers. That saved enough programmer time + debugging runs to pay for the inefficiency.

Needless to say, we don't have to resort to that today.

@mattblaze Additionally, all prototypes must be brought to production, even if the product is considered non-viable.
@stevegrunwell that was literally the PL/C model - the compiler never aborts, no matter how nonviable the code.
@mattblaze The 2nd amendment states clearly the people have the right to own and bear footguns
@mattblaze the right to bear footguns shall not be infringed!

@mattblaze Land of the free(), home of the brave?

I heard that your candidate's memory model is really weak.

@mattblaze "You can take my malloc from my cold dead hands."