OffensiveCon19 - Alex Ionescu - Keynote - Reversing Without Reversing

Channel:OffensiveCon · Length:33:40 · Published:2019-04-10 · Views:19562

Watch on YouTube

Summary

Alex Ionescu's OffensiveCon 2019 keynote on how reverse engineering is done on Windows without conventional reversing. It covers legal ways to obtain names of variables, exported functions and structures.

Why HN recommends it

Cited in ReactOS threads as an authoritative account of how Windows reverse engineering works and as a rebuttal to claims about ReactOS.

I'd recommend watching Alex Ionescu's talk at OffensiveCon about how he does reverse engineering on Windows — HN, 2019

Operating systems & kernels · Security & hacking

Subtitles (excerpt)

second all right testing excellent good morning thank you as well that's a sponsor and someone who well both sponsor through crafts check is all a sponsor personally of what Miguel Lucas and all the organizers have tried to do here defensive con thanks for coming thanks for giving us conference a chance those of you who it's your first time here you know it's always a big deal to go to a newer security conference both in terms of how's the content going to be how's the behavior going to be how's the location going to be so I do think those are you use who's your first time you'll you'll really enjoyed here and thank you for coming up with such a early time in the morning to hear me speak and I'm here to talk to you about this idea of reversing without reversing and really what I mean by that is when we look at reverse engineering what does it mean how do I think some people see it and how do I think it should be seen instead and how by seeing it that way you might be able to accelerate some of the same work you're doing I'm here to speak about this because I've been doing Windows low-level reverse engineering for about 17 years now I actually had to go Google myself to figure out various years and so I found out that

On Hacker News

Well that's categorically untrue. Sure they don't release private symbols intentionally but they have done in the past accidentally. At that point it becomes a bit of a grey area, undoubtedly leaked/stolen source code is a no-no but reversing from private symbols when they do leak seem harder to quantify as you still need to reverse engineer the code, just structures/names etc are already known. … — tiraniddo, 2019-07
It was by one "I am very smart. Nobody can be as smart as me" Microsoft programmer. Who completely dismissed this explanation [VIDEO] — MikusR, 2021-02
> Last time ReactOS came up here some folks were concerned about legality too, and I think there even was a salty Microsoft employee ranting about stolen code from the source leaks. Link to the actual dicussion here with the comments of the MS employee: [LINK] ReactOS developer's explanation on how they work: [VIDEO] — dvfjsdhgfv, 2020-10
The more you write in these threads the more you sound like a fool. [VIDEO] Start around the 9 minute mark. — dingby, 2019-07
Well, now please re-read your statement Do you understand that internal data structures entirely from the NT kernel, including (why?) their names != verbatim code from NT in your source The program code is logic first of all. For the similarities of names and structures itself - the answer is in this already mentioned video [VIDEO] from the 9:53 moment of time. TL:DW there are a lot of legal ways… — jeditobe, 2019-07

Related videos