Hey! No ed25519.

The original SSH2DOS implementation is from a putty version from around 2005. The parts I added/updated are from 0.70 (from 2017). Other ciphers etc from that version would be relatively easy to be added to this project. Anything after that version would more or less require a big rewrite.

I haven't forgotten about this project and I'm hoping to have some time to spend on it again.

Longer term better solution would be to do a new, full port of the latest putty. One day!

Just passing by this thread to say I have added AI-generated ed25519 code on my fork here:
https://github.com/Toyoyo/ssh2dos
It's tested working against OpenSSH 10 on Debian Trixie and OpenSSH 7.9p1 on Debian Buster with password authentication only.

I don't know the stance here about AI-generated code, so feel free to remove my post if it's against the rules 😀

Azami wrote on Today, 14:45:

I don't know the stance here about AI-generated code, so feel free to remove my post if it's against the rules 😀

I think there's no problem with AI-generated code, as long as it's tested working.

What hardware you've tested it on at the client side?
Any idea what's the minimum CPU/memory for that new version?

The test retro rig is a PIII-550Mhz on which connection is almost instant on both 16-bit and 32-bit versions.

I wonder if it would be practical to design some kind of ISA card or parallel port dongle with a cheap microcontroller and use it as a hardware accelerator for SSH on older vintage computers.

The Picovox, although primarily being designed as a sound device, could be programmed to offer such functionality. Same with the PicoMEM and the XTMax, of course.