@bagder I mean, It's inevitable. Isn't it? 😉

@bagder No.

Even less so when it's slop.

@bagder Unless it requires command line arguments to indicate this is not a pure document request, no. Just like a GET should not act as a POST, buy 1000000x worse.

Also where would it be getting the credentials? Would curl/libcurl snoop your .ssh??

@bagder Nah, just sounds like another cluster of problems.

@bagder

Initial instinct says no, it feels like feature creep. Not SSH itself (as it does SFTP already), but the command execution part.

I feel like there is little to gain here, other tools already do this and it just increases maintenance scope and security risks

@bagder initial thought: "nooooooooooooooooooo....!!!!"
Second thought: probably not :p

@bagder Nope. There's already a command for that.

@bagder

Interesting, yes. But i do not. Next to the very good reasons already mentioned here, i am also missing a convincing motivation behind this.

@bagder nope!

@bagder just the other day I was joking whether curl can be used as a transport for ssh ProxyCommand…

https://chaos.social/@zhenech/117151517621497909

@bagder Ww have SCP and SFTP. ... why we need more?

@bagder i get the feeling that this could be used for some nasty things. Or at least that or at least that this could make RCE easier in some setups where curl ist invoked with a user-supplied URL

@bagder how is it different from https://example.com/execute.api/shutdown%20-h%20now ? :)
but now: “ssh://host.example.com/command=shutdown -h now” instead of passing it with a custom -X

SSH is the transport in this case in stead of HTTPS. But otherwise, it is a ‘URL" that is requested.

For a command like “ps aux" it would make more sense in a way, as then you got a question and an answer (in plain/text or if there is a tool like ‘jq' with json mode).

You would have to come up with a proper SSH URL scheme though. But if one would do that it would fit curl better, yet another special option not so much.

@bagder I don't sense a particular demand for this feature from users.

@bagder My concern is that I don't think libssh2 uses `~/.ssh/config`. There are things that don't seem to fit in a URI. Jump hosts, identity files and agent forwarding would be the big ones from my usage. I usually use the config file to do that, but it also works on the ssh command line.

But if scp/sftp URIs already exist, maybe this would be fine?

@bagder 👀

@bagder it'd certainly be convenient sometimes... I'm far from qualified to talk about the implications of the increased attack surface area, but it kinda fits in the sense that for any long-lived tool or lib one expects gradual scope growth and hegemonisation. If the scope of curl is URI resolution, adding support for ssh scheme doesn't sound mad at all, and if it's not, where are the natural boundaries? I say do it, why not.

@bagder no. at the moment I expect curl to fetch and put things, not execute things.

also..

Assisted-by: an actual person <human@skunkwerks.at>

@bagder Seems out of scope to me, but it's your project and I'd have already made a different decision with regards to AI-generated submissions.

@bagder It would be fair only if local execution `curl --exec example.com/install` would be supported as well.

@bagder heck no. security smell & pinata for hackers. curl attracts enough scrutiny by bad actors as it is

@bagder speaking of which, I'd love to see grpc:// :)

@bagder no, because I am a strong proponent of the UNIX principle. Curl does one thing great, let ssh do that other job.

can I also remind you all that curl already speaks SCP and SFTP, in command line tool and library...

@bagder Hm, ssh can already to it: https://malcontentcomics.com/systemsboy/2006/07/send-remote-commands-via-ssh.html why mis-use curl then for this?

@bagder IMHO no; we have ssh already for that.

@bagder throw in a TUI and vim bindings while you're at it /s

and kids, don't forget that curl is even more a library than a command line tool...

@bagder No, don't do it. We've got ssh for that.