Someone Wrote a Whole New Operating System for the 1987 Macintosh SE, Just to Run SSH on It
The MIT-licensed release is three files on an SD card. The catch is time: a login takes about a minute until you flash custom firmware onto the card's own processor.

Switch on the Macintosh SE and the ROM does what it has always done: it goes looking for a disk. This time the disk is an SD card pretending to be one, and what’s on it isn’t Mac OS.
The README is blunt about this. “There is no Mac OS underneath,” it says, and Apple’s ROM “is used for one thing only, reading the kernel off the disk at start-up; after that it is never called again.” The ROM is basically a bouncer who lets the new owner in and is never spoken to again.
The handoff starts small. The ROM loads a 3 KB loader from the BlueSCSI (or a 1 KB boot block from a floppy), which draws a start-up picture and pulls in the kernel. Most login pages weigh more than that before the first font arrives. A row of small pictures fills in as each part comes up, so you can watch the machine assemble itself.
The kernel is the project’s own work: interrupts, a 60 Hz clock, a crash screen, a serial log on the modem port, and its own keyboard and mouse driver for ADB. It also has a SCSI driver and a FAT16 volume that stores your settings, trusted servers and past connections.
The SE never had WiFi, so the BlueSCSI supplies it. SSH OS talks to the card’s WiFi adapter over SCSI and runs its own network stack on top: ARP, IP, ping, UDP, DHCP, DNS and TCP. On top of that sits a real SSH client. Curve25519, Ed25519 and ChaCha20-Poly1305 are written in plain C on the 68000, and you can log in by key or by password. The README describes it as “a real SSH client on an 8 MHz 68000, with nothing in between.”
What you get at the other end is an xterm-style terminal, 85 by 32 characters, sized so full-screen programs work: editors, top, tmux, text interfaces. The SE’s own keyboard has no Page Up, Page Down, Home or End, “which is why Command with an arrow stands in for them,” the README explains. Command-Q or Control-] ends a session, and Esc cancels a connection that is still being made.
The home screen is a bar showing memory, processor load, volume, network and clock, with icons for SSH, Settings and a hardware test. The hardware test draws the SE’s logic board with a number on each part and a field for each to see and try it. Setup is also a bit of a gag: to join WiFi you click the fan at the right of the bar, click your network and type its password. The fan icon at least clears the air for first-time setup.
The project is honest about how finished it is. It runs on a real Macintosh SE (FDHD ROM, 4 MB) with a BlueSCSI, but it was developed and tested in the Snow emulator and then checked on the hardware. The repo shows 23 commits and 5 stars, so this is very early, and “what it does not do yet” lives in a notes page.
The speed is the biggest catch. SSH’s arithmetic is heavy for an 8 MHz chip, and with the BlueSCSI’s stock firmware connecting takes about a minute. The release ships a modified BlueSCSI firmware that hands that math, plus the encryption of a session’s packets, to the card’s much faster processor. SSH OS detects it on its own and announces “SSH acceleration on (BlueSCSI).” It targets a BlueSCSI v2 with a Pico W, not a Pico 2 W.
One detail is still unproven. After the first install, the firmware can be updated by dropping a .bin file on the SD card. The README says that is how BlueSCSI’s firmware describes it, and adds: “we have only used USB so far.”
The obvious prediction is that this opens a small genre: other compact Macs and old machines with SCSI ports turned into dedicated terminals, each with the same trick of leaning on a modern card to supply networking. The README points to its notes for other machines, so the author has at least thought about it, though nothing in the repo promises it.
The firmware route may matter more than the Mac. A card that does the encryption for a slow host is a pattern that could outlive this project, and the author has already shown it cuts connection time to a small fraction. Watch whether BlueSCSI’s own firmware ever picks up the addition, since that would turn a one-off patch into a normal part of the hobby.
The less glamorous prediction is that the work moves from writing the OS to maintaining it. A kernel with its own drivers, network stack and crypto ages like any other, and with one contributor and no forks yet, the first few outside bug reports will say a lot about whether it becomes a toy or a tool.
Mac OS, meanwhile, has left the chat.