MarketFiles transferred over shell protocol
Company Profile

Files transferred over shell protocol

Files transferred over Shell protocol (FISH) is a network protocol that uses Secure Shell (SSH) or Remote Shell (RSH) to transfer files between computers and manage remote files.

Protocol messages
Client sends text requests of the following form: #FISH_COMMAND arguments... equivalent shell commands, which may be multi-line Fish commands are all defined, shell equivalents may vary. Fish commands always have priority: the server is expected to execute a fish command if it understands it. If it does not, however, it can try to execute a shell command. When there is no special server program, Unix shell ignores the fish command as a comment and executes the equivalent shell command(s). Server replies are multi-line, but always end with ### xyz<optional text> line. ### is a prefix to mark this line, xyz is the return code. Return codes are a superset to those used in FTP. The codes 000 and 001 are special, their meaning depends on presence of server output before the end line. == Session initiation ==
Session initiation
The client initiates SSH or RSH connection with as the command executed on remote machine. This should make it possible for the server to distinguish FISH connections from normal RSH or SSH. The first two commands sent to the server are FISH and VER to negotiate FISH protocol, its version and extensions. The server may reply to VER command with a lines like VER 0.0.0 ### 200 which indicates supported version of the FISH protocol and supported extensions. == Implementations ==
Implementations
Midnight Commanderfar2llftp • fish:// KDE kioslave (with Konqueror, Krusader or Dolphin) • fish as tcl-vfs • FISH was implemented in Emacs TRAMP some time ago, but support was removed (although TRAMP still can use shell connections in a similar way using tramp-sh.el script file) == See also ==
tickerdossier.comtickerdossier.substack.com