4 ms·
Econet was awesome --- by default the Econet ROM for BBC Micros ran a server which supported a variety of useful RPCs. These included: PEEK - allows one machin
by david-given 10y ago
Econet was awesome --- by default the Econet ROM for BBC Micros ran a server which supported a variety of useful RPCs. These included:
PEEK - allows one machine to read an arbitrary chunk of memory from another.
POKE - allows one machine to write an abitrary chunk of memory to another.
JSR - allows one machine to send an executable chunk of memory to another station, which then executes it (max size 128 bytes).
HALT/CONTINUE - allows one machine to freeze another (so that you can use the above calls to fiddle with its memory).
These were system calls and required programming skills to use, but the ROM provided various human-usable commands like * VIEW (which copies a remote machine's screen to yours), or * REMOTE (which slaves a remote machine's keyboard to yours). You could tell your machine to stop listening to all this stuff with * PROT, but it was all on by default. (And * PROT wouldn't protect you from commands sent from particular privileged addresses.)
[Note: system shell commands on Acorn operating systems traditionally started with a * , but HN is having trouble rendering it. Ignore the spaces between the * and the command name above.]
It's not like they weren't aware of the security issues; you only found out about the commands above if you looked at the special manual (http://chrisacorns.computinghistory.org.uk/docs/Acorn/Manuals/Acorn_Econet_AdvancedUG.pdf http://chrisacorns.computinghistory.org.uk/docs/Acorn/Manual...). Or, you know, if you looked at the ROM, which had a handy list of all the commands in the table at the top. Did I mention that Econet was heavily used by schools?
Oh, and the file server sent all authentication information over the wire in plain text, but if you got far enough into the system to realise this, you were already past the point where hashing the passwords would have been useful.
It was a different age.
To be fair, for the early 80s, Econet was pretty awesome. With care you could run it up to 60kB/s, which was blisteringly fast for an 8-bit system; faster than the BBC Micro's floppy disk, which was already pretty fast (10-20kB/s; C64 users would weep when they saw how fast a BBC Micro could load off disk); at the low level it supported multiple networks with bridging, individual machine addresses and ports, allowing you to write proper client/server code --- a printer server came as standard; the built-in network file system was superb, supporting multiple users with authentication and unix-like file permissions; and it was properly hierarchical, of course. Its comfort zones was big networks of BBC Micros (and, later, ARM machines) all talking to a central file server, and it did that pretty well. But secure it wasn't.
- Theodores 10y agoSadly I didn't get to play with EcoNet even though our school had a computer room full of BBC B micros (and one 380Z). Having been deprived, I am wondering how Econet actually was supposed to be wired up. Was it like early thin net ethernet with DIN instead of BNC cabling? Or was it 'hub and spoke'? I can't imagine there were ethernet style routers/hubs for EcoNet but the teachers were supposed to have some type of god-like power over pupils' machines so I would like to know how that was supposed to work too.
- david-given 10y agoThe bus itself was two twisted pairs, one for clock and one for data (he says after looking it up), mediated by a MC68B54 data controller. Computers appear to have been patched in in parallel. Each segment had to have a terminator at each end plus a powered clock driver, which meant that setting up ad-hoc Econet links was basically too hard. The speed of the clock determined the transfer rate of the network. There were routers, which would bridge between multiple networks --- they connected to multiple Econet segments and just relayed packets addressed to the other network. Apparently their primary purpose was to speed-match between BBC Micro networks, which had to be quite slow, and Archimedes networks, which could be much faster. The hardware's painfully antiquated by modern standards, of course; I2C is faster and cheaper and doesn't need clocks or terminators or any of that nonsense. Also, from flipping through the Advanced User Guide, it looks like it's entirely packet based, but it does a four-way handshake for every packet --- effectively setting up a connection and tearing it down again! Which gives you reliable delivery but at a huge cost. We forget just how good TCP/IP is. I suspect the god-like power mentioned was simply having a copy of the Advanced Users Guide and knowing about * VIEW and * REMOTE. Also apparently there was an Econet interface available for the 380Z, so your school was totally missing out there.