cyberduck Add support to run subsystem with sudo

I often access servers, that I don’t control the configuration of, using cyberduck. They almost always are configured so that you can’t ssh as the root user. I do however have sudo access and sometimes need to switch to the root user to perform some actions.

I would save alot of time if I was able to do this using cyberduck. The windows SFTP client WinSCP has solved this, explained here:

http://winscp.net/eng/docs/faq_su#use_sudo_on_login.

Sep 18 '14 14:09 cyberduck

+1

Sep 26 '14 14:09 cyberduck

Preference for subsystem name in 4bea50e3bd90f4b3d2c1a016f4f29645a101e14e.

Oct 14 '14 15:10 cyberduck

#9188 closed as duplicate.

Dec 30 '15 15:12 cyberduck

#9309 closed as duplicate.

Feb 27 '16 17:02 cyberduck

#10728 closed as duplicate.

Oct 01 '19 19:10 cyberduck

#11636 closed as duplicate.

Mar 29 '21 11:03 cyberduck

Wow, this tickets roots back to 2014. Is there even a chance to implement this feature?

Mar 29 '21 11:03 cyberduck

Replying to [comment:10 nihebe]:

We will see that we can add support using a option in a custom connection profile.

Mar 29 '21 12:03 cyberduck

It not clear from the RFC this should work as the subsystem name must be predefined in the server configuration. As expected requesting a subsystem with a full path to the binary results in

sshd[24609]: subsystem request for /usr/libexec/openssh/sftp-server by user dkocher failed, subsystem not found

Mar 29 '21 15:03 cyberduck

Well, I would say the path should be configurable. It depends on the OS where the sftp-server binary is. For example, on a Debian 9 in my lab it is located at

/usr/lib/openssh/sftp-server

Mar 30 '21 09:03 cyberduck

Friendly bump on this topic :) It would still be a great improvement to the almost perfect Cyberduck. Do you see any problem in implementing the subsystem as a configurable parameter?

Oct 01 '21 20:10 cyberduck

still needed...