I assume this is an okay link to post out loud because the book claims to be Creative Commons ShareAlike, despite also being published by MIT Press.
(h/t @yaaps for the hint!)
From the introduction, and already I'm feeling sad, and not for this book:
<< A number of early programming language designs in effect made a design commitment to reflect the style of hardware organization called the Harvard architecture: the code is here, the data is there,
and the job of the code is to massage the data. But an inflexible, arm's-length separation between code and data turns out to be a significant limitation on program organization. >>
A truth we all learned in school back in the 1980s because the Harvard Architecture seemed like a weird remnant of ancient times, like EBCDIC and punched cards.
Why am I feeling sad?
Because guess what's the new hotness in Enterprise Security Best Practices, here in the enlightened future year 2021!
If you guessed "frantically reimplementing the Harvard Architecture by banning compilers and forbidding running EXEs from user home directories" you guessed right.
@natecull this is going to make me really sad and frustrated but is there any intro reading into that?
@natecull oh Ive read this book, I meant the enterprise buzzword type articles about why this is best practice all of a sudden
Oh. Um. Well anything from Microsoft really? Specifically Defender and AppLocker, which they're pushing *hard*. And anything to do with ransomware and "preventing lateral movement" or "living off the land" I guess.
"Living off the land" is Security Expert buzzword for OMG I JUST LEARNED THERE'S A COMMAND SHELL ON EVERY COMPUTER AND WORSE, THERE MIGHT BE A COMPILER SOMEWHERE
Nice, always good to see a fresh take on this.
