/explore
|
You are here 
|
blog.deobfuscate.io | ||
| | | | |
maddiestone.github.io
Learn to reverse engineer Android applications! |
|
| | | | | ||
| | | | |
ogmini.github.io
Currently, writing this with no power and internet. Luckily, I made progress earlier in the day with writing a testing/validation UWP application. The 36 data types lines up with what I'm seeing and testing. I'm still working on reverse engineering the Composite Value key. |
|
| | | | | ||
| | | | |
blog.nuculabs.de
It's been some time since I've done some Reverse Engineering and today I've completed a simple challenge on . The filename of the challenge is crackme_wtf and here are some hints to get you started: Determine type of FILEs. Don't be afraid to patch and use a debugger. Try to eliminate the randomness. Maybe some functions that have to do with time, random numbers or the current process's id. If the last hint doesn't yield any results... Is the required password really needed to get to the flag? Thanks for reading and good luck! |
|
| | | | | ||
| | | | |
everythingfunctional.wordpress.com
The answer to the question of whether we should write automated test suites has largely been settled. We absolutely should write unit tests, and possibly even integration and end-to-end tests. But as acceptance of this practice grew, and adoption became more widespread, a follow-up question arose; How many tests should we write? How do we... |
|
| | | |||
