Files transferred over shell protocol: Difference between revisions

Revision as of 02:58, 19 June 2014

Revision as of 17:26, 3 December 2014

Line 3:

'''Files transferred over Shell protocol''' ('''FISH''') is a network [[Protocol (computing)|protocol]] that uses [[Secure Shell]] (SSH) or [[Remote Shell]] (RSH) to [[file transfer|transfer files]] between computers and manage remote files.

The advantage of FISH is that all it requires on the server-side is an SSH or RSH implementation, [[Unix shell]], and a set of standard [[Unix]] utilities (like [[ls]], [[cat (Unix)|cat]] or [[dd (Unix)|dd]]--unlike—unlike other methods of remote access to files via a remote shell, [[Secure copy|scp]] for example, which requires ''scp'' on the server side). Optionally, there can be a special FISH server program (called ''start_fish_server'') on the server, which executes FISH commands instead of Unix shell and thus speeds up operations.

The protocol was designed by Pavel Machek in 1998 for the [[Midnight Commander]] software tool.

Line 22:

### xyz<optional text>

line. <ttcode>###</ttcode> is a prefix to mark this line, <ttcode>xyz</ttcode> is the return code.

Return codes are 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 ==

The client initiates SSH or RSH connection with <ttcode>echo FISH:;/bin/sh<tt/code> 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 <ttcode>FISH</ttcode> and <ttcode>VER</ttcode> to negotiate FISH protocol, its version and extensions.

#FISH