2,510 karma · joined August 11, 2015
By tying it to a particular key owned by the attacker, no other party can trigger the exploit.
~/t [main L|…1]$ gcc test.c
~/t [main L|…1]$ vi test.c
~/t [main L| 1…1]$ git diff
diff --git a/test.c b/test.c
index 33c14ce..dc93007 100644
--- a/test.c
+++ b/test.c
@@ -1,3 +1,3 @@
int main() {
- return 0;
+ return 0;
}
~/t [main L| 1…1]$ gcc test.c
test.c:2:5: error: expected expression
<U+0008>return 0;
^
1 error generated.
So, yes, this could have been made to look exactly like a meaningless whitespace change.Today, of course, I love tofu.
[0] https://en.wikipedia.org/wiki/Indentation_style#K&R_style
I could afford to take months or years off, but I’d rather let that money grow in an interest-bearing account for decades and spend it later.
There was no attempt to "lift-and-shift" anything. There are technologies that overlap and technologies that conflict and technologies that compliment one another. As with any huge layered stack, you have to figure out which from the "LinkedIn" column marry well with those in the "Azure" column.
I personally appreciate LI management's ability to be clear-eyed about whether the ROI was there.
That may sound glib, but I don't mean it to be. If there's a pilot that is hiding their mental health issues because they'll otherwise risk destitution, that's a problem that's solved by a social safety net. Such a safety net would also solve many other social ills, like people stuck with abusive employers, and so on.
This comment reminds me very strongly of myself, trying to read German. You know C, why shouldn't you be able to understand Rust? But they're not the same thing, and they communicate different things in different ways. There are concepts that simply do not map directly. Someone could very easily write the exact same post from the perspective of a Rust programmer starting with C. Where is the equivalent to Cargo.toml? What is this Makefile thing, and why doesn't it look like a configuration file? Etc. No amount of just forcing yourself to try is going to provide clarity unless you already understand the idioms and structure at play.
With that said, I have written embedded Rust and it is an amazingly freeing experience. Writing C right now feels like trying to balance a knife on my finger. With Rust I can just get work done. I strongly recommend you spend the time to learn it. Even if it doesn't convince you that C's days are numbered, it will make you a better programmer by training you to think about safety and correctness up front.
The one time I have been able to bust out my knowledge of Swedish (limited to this one phrase) in order to try and flirt, the focus of my attentions was... not impressed. I couldn't tell if it was because I was not impressive, or just a cultural mismatch. In any case, it didn't discourage me from continuing to learn.