Hacker News new | ask | show | jobs
by marcusr 1940 days ago
My school had a classroom of BBC Micros which were connected over a primitive network to a "server" which I guess must have had a hard drive for saving files too. I can't take the credit but a school friend worked out how to view the memory of another machine over the network, from which we made the first remote keystroke capture I had ever seen, which got us the teachers' passwords.

Our first hack was born - with their password we could get onto the server and print out the password file (in plain text of course). The teachers started to realise they'd been hacked but I think thought it more likely we'd observed their typing when sat nearby and so changed their passwords. Of course we could just keep watching their passwords being entered at a distance.

I think we were caught in the end red handed with the password file printing out and unable to stop it printing when they came in the room. Luckily back then it was seen as experimentation not criminal!

2 comments

That sounds very familiar!

There was essentially no security on those Econet networks. If you had a copy of the executable that could read and write the memory of a remote computer, you were good to go.

I remember I had a print-out of a hex dump of the REMOTE command and used it with exactly that key capture attack. I just typed in the executable then told the teacher I'd forgotten my password and needed it reset. I watched remotely as he logged on to his admin account.

The next day, all the BBC micros in the lab played Captain Pugwash when they started: very beep-heavy given the ability of a BBC to create sound.

Eventually I was caught re-entering the hex dump and my printout was confiscated. I didn't have another copy.

With the *REMOTE, *VIEW and *NOTIFY commands you could also have a huge amount of fun in class (much of it invisible to the teacher).

We also found a privilege escalation endpoint, and were only caught when the network server was upgraded to an Archimedes and the special badging on admin accounts in the GUI gave our MRBIG account away.

Don’t forget to change *PROT to *PR0T in the teachers !BOOT file.
I vaguely remember editing one of the boot files so it'd start up and display a fake > prompt. This was then used to print out an insult. Also because everyone just hit break you could set it with a *KEY0 command to just run the program and insult them some more. I remember getting in trouble more than exactly what I did - was a long time ago now! :)