The fish protocol is a sort of ftp over ssh, that is touted as not needing special software on the server side (unlike scp and sftp).
From a cursory glance it seems like it allows fish commands that fall back to basic shell commands if the server doesn't have the fish software installed. But why not just use the shell commands directly?
(The question linked to above explains the differences between the various protocals, but it doesn't explain the mechanism of fish, or why bother with the protocal if you are sending equivalent shell commands anyway.)
scp
andssh
don't require "special" software; a secure shell server is all that is needed, and is a core package in nearly all Unix-like distributionns. – DopeGhoti Jul 10 '17 at 17:34scp
requiresscp
binary on the server, which is not part of theopenssh-server
, but part ofopenssh-clients
. – Jakuje Jul 10 '17 at 19:42