←back to thread

3883 points kuroguro | 1 comments | | HN request time: 1.796s | source
Show context
powerfulclick ◴[] No.26296951[source]
This is really cool - how did you develop the background knowledge to solve this? I'm trying to learn more about low-level stuff and I would have no idea how to approach solving a problem like this
replies(2): >>26296987 #>>26316629 #
spuz ◴[] No.26296987[source]
I'd recommend searching HN for threads about learning reverse engineering. Here are a few that I've found:

Reverse Engineering Course: https://news.ycombinator.com/item?id=22061842

Reverse Engineering For Beginners: https://news.ycombinator.com/item?id=21640669

Introduction to reverse engineering for beginners: https://news.ycombinator.com/item?id=16104958

replies(1): >>26297283 #
the_only_law ◴[] No.26297283[source]
I love it but I don’t have the focus or patience to ever do anything more than basic analysis.

A lot of the reverse engineers I know seemingly have deep platform knowledge and can do things like cite Win32 docs from memory.

replies(2): >>26297371 #>>26298012 #
mmastrac ◴[] No.26297371[source]
I was a reverse engineer for years and never was able to do anything like quoting docs. I'd be constantly googling or using reference material. The only real attribute I'd suggest is tenacity.
replies(1): >>26298420 #
1. Graziano_M ◴[] No.26298420[source]
Tenacity is everything.

Both when looking at a particular problem, but also in sticking to RE in general for long enough to pick up the skills and tricks that make you quick. There are countless tricks you pick up that cleave off huge amounts of time that would otherwise be wasted.