An SSH server on AROS might look like a sysadmin detail, but in practice it’s one of the dividing lines between “I spun up a VM out of curiosity” and “I can actually develop on this without losing my mind.” The AROS port of BebboSSH starts exactly here: making an Amiga-like machine reachable from a modern host, with remote commands, file transfer and repeatable tests.
The context is Telegram Amiga, the experimental project that uses the Telegram Bot API as a testbed for networking, TLS, JSON, polling and controlled message sending on Amiga-like systems. When the target is AROS, manually copying binaries around, juggling disk images or relying on hand-made exchanges inside a VM works for the first five minutes. After that it’s just friction. And when you’re chasing network and TLS bugs, friction isn’t romanticism: it’s noise.
With BebboSSH on AROS, the loop changes: from a Mac or a Linux box you can reach the system, upload a binary, fire a command, watch the output, repeat. It doesn’t turn AROS into a modern Unix server, and it doesn’t have to. What it does is give it just enough admin surface to treat it like a real technical target, not like a nostalgic postcard.
The technical point: SSH as infrastructure, not convenience
Right now there are builds of bebbosshd and bebbosshkeygen available for AROS i386/32-bit and x86_64/64-bit. The i386 AROS One alt-abiv0 line is the most mature for a publishable runtime kit; the x86_64 branch has come a long way and mainly needs broader testing across different installs. Caution is still warranted, but we’re well past the classic “it starts once and then nobody breathe” phase.
The tests described in the workspace cover the parts that actually matter for a remote development tool: starting the SSH daemon, password authentication, generating Ed25519 host keys with bebbosshkeygen, simple remote commands from OpenSSH, propagation of exit statuses, a minimal interactive shell, transfers via SCP and SFTP, round-trip with small files and 1 MiB files, repeated connections and running Telegram Amiga tests over SSH on hosted AROS.
This is not a decorative checklist. Every item removes a form of manual work. If SCP works, the binary arrives with no rituals. If exit statuses propagate correctly, scripts can decide whether a test failed. If the daemon stays stable across errors, transfers and repeated connections, then you can start thinking in terms of workflow, not just demos.
AROS, Telegram Amiga and the value of hybrid machines
AROS is an interesting RetroLab playground because it lives in a hybrid zone: it inherits Amiga ideas and sensibilities, but also runs in more modern, virtualized or hosted environments. That makes it useful for experimenting with toolchains, network backends, OpenSSL, cross-builds and faster test cycles than you’d get on a single historical physical target.
In the Telegram Amiga project, AROS already has a TCP backend based on bsdsocket.library, native builds and i386 alt-abiv0 cross-builds, offline tests, TCP/HTTP diagnostics, HTTPS, preflight, getMe, read-only polling and controlled message sending. The TLS side uses OpenSSL from the AROS SDK, with explicit certificate verification when a CA bundle is provided. These are not flashy details, but they are exactly what separates a serious experiment from a pretty screen that exists only to be screenshotted.
BebboSSH fits right at this level: it’s not the editorial protagonist, it’s the bench gear. Without a reliable remote channel, every test on AROS is slower, more fragile and harder to automate. With SSH, the retro-compatible target plugs into a modern development chain: sources and orchestration on a current machine, execution and verification on the system that actually has to carry the program.
What really changes
The practical outcome is not “wow, SSH on AROS,” even if it is that a little, let’s admit it. The real point is that an Amiga-like system can become part of a repeatable development process. That changes the kind of software you can even attempt to port: not just simple programs compiled once, but tools that need constant trials, logs, networking, TLS, transfers, regression testing and feedback from multiple installs.
Living retrocomputing means exactly this: not worshipping the machine because it’s old, but building around its limits an environment where it can still do actual technical work. AROS with BebboSSH doesn’t pretend to be Linux. It does something more interesting: it exposes enough hooks for a modern workflow to respect its constraints instead of working around them with ever more fragile manual procedures.
In short
- BebboSSH on AROS makes the target reachable via SSH, SCP and SFTP from modern machines.
- The work is tied to the development of Telegram Amiga, where repeatable tests and fast binary transfer are essential.
- The i386 AROS One alt-abiv0 line is the most mature target; x86_64 is promising but needs broader feedback.
- The value is not nostalgic: SSH makes AROS more observable, automatable and genuinely useful as a real lab.