Small update on the BebboSSH AROS port.

The AROS i386 ABIv0 port has now reached version 1.0.

The original goal was not only to bring over the SSH client itself, but to make the main BebboSSH suite available on AROS. The package now includes the core executables from the original distribution:

* bebbossh
* bebbosshd
* bebboscp
* bebbosshkeygen

along with the required libraries and support components.

This is the first release that I consider functionally complete on AROS i386 ABIv0.

The next step will be the x86_64 port. Work has already started, but there are still runtime stability issues that need further investigation before an equivalent x86_64 release can be published.

Many thanks to everyone who tested the earlier builds and reported problems during the porting process. Additional testing and feedback are always welcome.

Repository:
https://github.co...bossh-aros

Releases:
https://github.co...s/releases

Thanks, you are right.

The previous “hosted” name was only used internally for testing, not as a real public AROS target. Public builds are now named only by architecture/ABI:

• bebbossh-aros-i386-abiv0
• bebbossh-aros-x86_64

Old “hosted” pre-release packages were removed to avoid confusion.

Current x86_64 release:
https://github.co...ros-x86_64

Nice work - another way to exchange data between AROS and world!

Quick question - you have two zips "hosted" and "x86_64". Why the "hosted" build? In general the same AROS binary should work both in an linux-hosted and VM/native pc environments.

Thank you

Hi everyone,

I would like to share a new status update about my AROS port of BebboSSH.

The current tree now provides working builds of both bebbosshd and bebbosshkeygen for AROS i386/32-bit and AROS x86_64/64-bit.

This port started from a very practical need, I wanted a working SSH server on AROS to make development and testing of telegram-amiga easier. telegram-amiga is also evolving, and being able to run remote commands, upload new binaries, execute repeatable tests and automate the development loop from a modern host to an AROS machine is much better than constantly relying on manual disk image/file exchange.

The i386 AROS runtime kit is currently the most mature release target. The x86_64 path has improved a lot and is now validated in hosted AROS x86_64 for daemon startup, remote commands, SCP/SFTP transfers and repeated connection tests. I would still like broader testing on different AROS setups before calling the 64-bit package universally final, but it is no longer just a “proof of life” build.

Repository:

https://github.co...bossh-aros

Stable i386 release:
https://github.co...-aros-i386

Latest hosted/x86_64 release:
https://github.co...ros-x86_64

The goal is simple, make AROS reachable from a modern OpenSSH client, with remote commands and file transfers available without relying on disk image tricks or manual VM file exchange.

If anyone is using AROS i386 or x86_64 and wants to test the current builds, feedback would be very useful, especially about daemon stability, SCP/SFTP behavior, key generation and repeated SSH