Live data from Hacker News

Reverse engineering guide for beginners: Methodology and tools

0x00sec.org

21–30 of 70 posts

Re: Reverse engineering guide for beginners: Methodology and tools

#23
wow times have changed from using softice and ollydbg. When I used to RE for fun it was sad seeing how expensive programs could just be rigged by a simple NOP or JNZ/JMP change.

My best challenge was Brazil (3ds render engine). It had all types of checks that would only show up when rendering.. But that was no match.. Good times

Re: Reverse engineering guide for beginners: Methodology and tools

#25
post #18
post #5

Blank page without javascript. Bye.

0) that's most definitely not blank page, I have noscript and it does load content. 1) what kind of response is this?

Using JSBlocker here. no content. Just doing some futile effort to show web developers that to get some basic text without javascript is cool. Of course, do whatever you want with your site. Maybe I was a bit rude.

Re: Reverse engineering guide for beginners: Methodology and tools

#26
post #25
post #18

Earlier quoted context omitted.

0) that's most definitely not blank page, I have noscript and it does load content. 1) what kind of response is this?

Using JSBlocker here. no content. Just doing some futile effort to show web developers that to get some basic text without javascript is cool. Of course, do whatever you want with your site. Maybe I was a bit rude.

Noscript+Firefox here. There's full content - the entire page has a JS-disabled full text of every post wrapped in a large block.

Does jsblocker completely wipe out noscript tags or something?

Re: Reverse engineering guide for beginners: Methodology and tools

#27
post #5

Blank page without javascript. Bye.

Idiot who voluntarily breaks their web browser, then complains that it's broken. Bye!

Context: Visiting a website written by/for reverse engineering, a subset of Hacking.

Assertion: Visiting a hacking website with Javascript disabled is a bad thing.

Hmmm...

Re: Reverse engineering guide for beginners: Methodology and tools

#28
post #27

Earlier quoted context omitted.

Idiot who voluntarily breaks their web browser, then complains that it's broken. Bye!

Context: Visiting a website written by/for reverse engineering, a subset of Hacking. Assertion: Visiting a hacking website with Javascript disabled is a bad thing. Hmmm...

Not a bad thing. You are obviously more than free to configure your browser however you want. Just don't whine about it. Maybe give some constructive criticism (It would be nice if..., Maybe you could consider to...).

Or just open the developer console and inspect the source, like a hacker/reverse engineer.

Re: Reverse engineering guide for beginners: Methodology and tools

#30

After brushing up on this, if you're looking for something "fun" to work through, the NSA's 2016 Codebreaker challenge is good, granted you have a .edu email address (only US .edu too, unfortunately). https://codebreaker.ltsnet.net/challenge I think they're going to be keeping the 2016 version up for a while longer. They generally start a new one in September each year.

Damn, too bad they don't accept .ac.uk addresses :( I feel like there should be a standardised way to ensure users are students/affiliated with an educational institution (maybe an international federation on top of SAML a la the UK Access Management Federation).

I guess at the end of the day the NSA want students in the US, who are likely US citizens and thus eligible for a job.

Post reply on HN