←back to thread

3883 points kuroguro | 2 comments | | HN request time: 0.752s | 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 #
saagarjha ◴[] No.26298012[source]
The number one way to get the patience to do this is to have impatience for software that is slow.
replies(1): >>26298526 #
1. meibo ◴[] No.26298526[source]
And with most RE software(especially the mentioned inaccessible interactive disassembling tool) you'll get that by default, waiting for a 70mb binary to analyze isn't fun :)
replies(1): >>26300663 #
2. saagarjha ◴[] No.26300663[source]
Fortunately, software engineers can be bad at making time value judgments ;)