←back to thread

388 points zdw | 1 comments | | HN request time: 0s | source
Show context
jan_Sate ◴[] No.44367108[source]
Impressive. Interesting how it took that long until someone found the triggering mechanism of this easter egg. Reverse engineering is tough.

Now that I wonder where I could learn RE? Where do I even start? Got any recommendation of online tutorial or book or something?

replies(2): >>44367414 #>>44374248 #
1. enoent ◴[] No.44374248[source]
Without discrediting the author, as it's always cool to share these findings, was anyone actively looking for this over 27 years?

A lot of the times, it just happens that someone was the first person that even bothered trying digging into the code. Specially after decompilation became much more accessible for less popular architectures with Ghidra. Give it a try, there's plenty of low hanging fruit! I've submitted another case some time ago.

Also luckily, considering other OS easter eggs, it doesn't seem like there was any obfuscation involved, like "chained xor stored in bitmap resource of badly supported executable format": https://x.com/mswin_bat/status/1504788425525719043