If you’re interested in computer system exploitation via memory corruption you might want to follow my @PrincessOfCats account and the #CH4R0 hashtags for the next week
This is a problem for me personally, so I’ll be thinking allowed and pointing out my own faults as we teach. #CH4R0
Our secondary, occult discussion to go along with #CH4R0 will be focused on the mental and spiritual aspect of hacking as it relates to lust of result.
Gonna be tooting my thoughts as we teach “Click Here for Ring 0” class again this year. #CH4R0

#CH4R0
Any probabilistic behavior needs to be tested an absolute minimum of 1,000 times. 100 isn’t a sample size at all and 10 is barely noise.

10,000 tests per platform is preferred.

#CH4R0
To destroy an exploit before it has fulfilled its purpose of owning is to pervert its Final Cause and thusly the act corrupts a vital part of the soul of the destroyer through akrasia.

To own with an exploit is the exercise of virtue.

#CH4R0
Homework:

#ch4r0
Your first reaction to any problem should be to open your debugger. Getting a divorce? Open the debugger! Cut yourself badly? Open the debugger!

If, on the path to enlightment the buddha stands in your way, debug him.

#CH4R0
Think about exploit dev like the scene in Apollo 13 where they dump that box out on the table.
- Think of your goal first,
- Second build the box of junk parts
- Last figure out how to put your parts together to achieve the goal
#CH4R0
ANY time someone adds an optimization to a system you can either 1) control the path the system takes if you control the info the optimization is based on or 2) learn the information the optimization works on based on the timing of the system.