2026-08-31 09:25 UTC
Replies (4)
-
@bagder@mastodon.social 2026-08-31 09:28
and kids, don't forget that curl is even more a library than a command line tool...
-
@oots@infosec.exchange 2026-08-31 09:40
@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.
-
@bagder@mastodon.social 2026-08-31 09:32
can I also remind you all that curl already speaks SCP and SFTP, in command line tool and library...
-
@algernon@come-from.mad-scientist.club 2026-08-31 11:27
@bagder@mastodon.social No. Even less so when it's slop.