Well, I have stories like that too... but I still don't consider "hacking" to mean breaking into
computers. It's just something a hacker might do because there is some reason he needs
access to a computer. For example, at school we had a UNIX box and it was just awefully
admined (in my eyes). I needed tools to be installed, and ... well, I wanted to be able to
login remotely on this box without the *social* stress of people knowing that I was being
logged in. That's an AS thing... I could not "relax" while being on the net through this box
when people could see me and ask why I was there or whatever. So, I wrote a little program
that looked like the login screen. When people typed their username and pass, it would
store it and then pass it on to the real program. Once I got the root password like that
I build in seven backdoors that allowed me to get back root, among which replacing the
login executable with a recompiled version that now also wrote the root password to some
file if they used it. I never made a secret of things I did (like installing new software, or
rebooting the box when necessary), I just acted as if I was legit root, so they knew I knew
the password. Every time they changed the password, I knew it again and they couldn't
understand that, heheh. In the end I was made official sys admin of the box, because
they didn't like the situation. By making it legal it was a solved issue in their eyes...
That is, until the root did a 'who' on the box to make sure nobody was logged in, and
then rebooted the machine. 30 seconds later I called from my home, asking why the
machine was being rebooted because I was kicked out. Then they found out I had changed
several tools to 'hide' my presence and they didn't like that. I had to change it back.
That being said-- I think that only THIS type of "hacker" stories appeals to non-techies,
because they can picture something, they understand it. General hack stuff is just incomprehensible
for them (almost by definition), so they don't understand it. Ie... I hacked my compiler to
dump call graph info during compilation... I hacked my IRC client to have a case sensitive
nick highlight. I hacked my window manager so I can move windows between two different
monitors, etc. Yet still, "hacking" in general just means digging deep into something,
figuring out every detail (down to the bit), with (in the case of computers) as automatic
result that you become the master of it. This includes writing programs from scratch.
It also includes doing mathematics imho. In the past weeks I've been "hacking" an algorithm
to calculate a product of a * (a + 1) * (a + 2) * ... * (a + n - 1) as efficient as possible.
You have NO idea how deep you can go into this. Most people would be happy with
anything that worked - some with anything that looked reasonably fast, but you can also
go to the very bottom and not rest until you have the fastest possible algorithm, ever.
Well, making this way too long and I have to go to bed...
Maybe I'll write something about this algorithm in the forum later