@bagder@mastodon.social I think it depends on how you (the maintainers) see curl/libcurl. If you see it as a "Swiss army knife", maybe it's okay to do it. If you see it as a "swiss army knife for file transfer", then I don't see why it should be added if you already support SFTP and whatnot. But really, I wonder why one would want to use curl/libcurl for running SSH commands. * if you need a library to run ssh commands on some remote server, then `libssh`/`libssh2` is the sane way to do it, no need to add it to libcurl. * if you need a command line tool, just use `ssh` directly. Either way, I see no reason to add this to curl.