The snide comments about "bit bucket" and /dev/null are completely unwarranted and rude.
[Your] definition of a hacker is not "the end-all, be all" - nor is mine, but that does not make my definition of "hacker" or "cracker" any less relevant nor any "less correct" than yours.
Believe me, you may see it as 'white' and I may see it as 'black' - and we BOTH could be right.
[and, yes, 'Crackers' (with or without peanut butter) often "break in" in order to do their reverse engineering]
So, you may think hackers are 'non-mailicious,' but you would be wrong - only the 'hackers themselves' consider themselves 'non-malicious.' :)
Notice in the definition below, the 'semi-colons' and the 2nd statment within: "bypasses passwords or licenses in computer programs;" - and also notice the -->"or"<-- in the related chain of semi-colons; thus, the cracker might do ONE [or] ALL of those things, but some crackers ONLY 'crack codes' - which was my point.
Many pure 'crackers' only crack codes (per my brother, who is a professional at that), though some crackers also 'hack.' My brother does not 'hack;' i.e., "hack into systems;" he only uses IDA Pro and tools like that to 'crack codes.'
This, showing both of us are correct, from
http://searchsecurity.techtarget.com/sDefinition/0,,sid14_gci211852,00.html
- "A cracker is someone who breaks into someone else's computer system, often on a network; bypasses passwords or licenses in computer programs; or in other ways intentionally breaches computer security. A cracker can be doing this for profit, maliciously, for some altruistic purpose or cause, or because the challenge is there. Some breaking-and-entering has been done ostensibly to point out weaknesses in a site's security system. "