Ssh has such a large surface, I don't see why they would do this. I also hope they allow you to use openssh as a fall back.
Ssh has such a large surface, I don't see why they would do this. I also hope they allow you to use openssh as a fall back.
As a matter of fact there are dozens if not hundreds of them out there. For a time, I was tracking some of them to figure out which ones support which particular protocol extension; the result is https://ssh-comparison.quendi.de and the list there is really incomplete (and sadly also outdated -- PRs welcome ;-)), I think I could easily double the number of entries there if I resumed work on it.
The one concern I'd have for a custom implementation is when they roll their own crypto... On a quick glance, that seems (?) to be the case here, see <https://docs.rs/crate/thrussh/0.28.0/source/src/cipher/chach...>, albeit only for chacha20poly1305 which is relatively easy to implement "right" and "securely", but one can still mess that up...
I'm the author, and you just made my day. Thanks.
> On a quick glance, that seems (?) to be the case here
Nope, I don't do crypto, I wouldn't work on other stuff if I did.
That particular file you point to implements decoding from SSH packets, and passes everything on to libsodium.
Second reason: SSH on Windows used to be the most nightmarish thing you can imagine.
Ssh deals with keys and accounts and all that which SSL/TLS don't do.
And being able to use pijul (or git) over plain old ssh is a pretty nice feature.