mc/vfs
1998-10-23 10:38:22 +00:00
..
extfs Marked security holes as such 1998-10-14 19:43:21 +00:00
samba * samba/configure.in: Require Autoconf 2.52 to make Debian 1997-01-01 01:23:31 +00:00
.cvsignore update .cvsignore 1998-09-25 20:11:21 +00:00
callback.h Fixed number of callbacks, added prototype of function to set 1998-06-08 13:00:29 +00:00
ChangeLog Removed debugging messages and fixed Makefile.in. 1998-10-23 10:38:22 +00:00
container.c Changed license to LGPL, added passing of vfs * (acting as self), so 1998-09-27 19:27:58 +00:00
container.h Initial revision 1998-02-27 04:54:42 +00:00
COPYING.LGPL Changed license to LGPL, added passing of vfs * (acting as self), so 1998-09-27 19:27:58 +00:00
direntry.c BIG changes: tar now uses brand-new direntry.c. Hope it does not hurt 1998-10-23 08:26:25 +00:00
direntry.h BIG changes: tar now uses brand-new direntry.c. Hope it does not hurt 1998-10-23 08:26:25 +00:00
extfs.c BIG changes: tar now uses brand-new direntry.c. Hope it does not hurt 1998-10-23 08:26:25 +00:00
extfs.h static's added, do_reget hack removed 1998-10-12 22:07:53 +00:00
fish.c BIG changes: tar now uses brand-new direntry.c. Hope it does not hurt 1998-10-23 08:26:25 +00:00
fish.h static's added, do_reget hack removed 1998-10-12 22:07:53 +00:00
ftpfs.c BIG changes: tar now uses brand-new direntry.c. Hope it does not hurt 1998-10-23 08:26:25 +00:00
ftpfs.h Thu Oct 22 20:41:50 1998 Norbert Warmuth <nwarmuth@privat.circular.de> 1998-10-22 20:17:49 +00:00
local.c static's added, do_reget hack removed 1998-10-12 22:07:53 +00:00
Make-mc.in Minor Makefile bug fix 1998-10-15 22:38:00 +00:00
Makefile.am libgnome: 1998-09-28 18:58:36 +00:00
Makefile.in Removed debugging messages and fixed Makefile.in. 1998-10-23 10:38:22 +00:00
mcfs.c BIG changes: tar now uses brand-new direntry.c. Hope it does not hurt 1998-10-23 08:26:25 +00:00
mcfs.h static's added, do_reget hack removed 1998-10-12 22:07:53 +00:00
mcserv.c Integration of Pavel Machek's vfs code split and vfs syntax change. 1998-05-26 00:53:24 +00:00
names.c static's added, do_reget hack removed 1998-10-12 22:07:53 +00:00
names.h Initial revision 1998-02-27 04:54:42 +00:00
README.fish More makefile fixes -mig 1998-09-25 20:00:42 +00:00
sfs.c Removed debugging messages and fixed Makefile.in. 1998-10-23 10:38:22 +00:00
shared_ftp_fish.c Small bugs... 1998-10-15 15:18:12 +00:00
shared_tar_ext.c BIG changes: tar now uses brand-new direntry.c. Hope it does not hurt 1998-10-23 08:26:25 +00:00
tar.c Removed debugging messages and fixed Makefile.in. 1998-10-23 10:38:22 +00:00
tar.h BIG changes: tar now uses brand-new direntry.c. Hope it does not hurt 1998-10-23 08:26:25 +00:00
tcputil.c Changed license to LGPL, added passing of vfs * (acting as self), so 1998-09-27 19:27:58 +00:00
tcputil.h Initial revision 1998-02-27 04:54:42 +00:00
undelfs.c static's added, do_reget hack removed 1998-10-12 22:07:53 +00:00
undelfs.h Initial revision 1998-02-27 04:54:42 +00:00
util-alone.c static's added, do_reget hack removed 1998-10-12 22:07:53 +00:00
util-alone.h Files I had forgotten to add from Pavel's VFS split. 1998-05-26 05:08:10 +00:00
utilvfs.c static's added, do_reget hack removed 1998-10-12 22:07:53 +00:00
vfs.c BIG changes: tar now uses brand-new direntry.c. Hope it does not hurt 1998-10-23 08:26:25 +00:00
vfs.h BIG changes: tar now uses brand-new direntry.c. Hope it does not hurt 1998-10-23 08:26:25 +00:00

		FIles transferred over SHell protocol (V 0.0.2)
		~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This protocol was designed for transferring files over a remote shell
connection (rsh and compatibles). It can be as well used for transfers over 
rsh, and there may be other uses.

Client sends requests of following form:

#FISH_COMMAND
equivalent shell commands,
which may be multiline

Only fish commands are defined here, shell equivalents are for your
information only and will probably vary from implementation to
implementation. Fish commands always have priority: server is
expected to execute fish command if it understands it. If it does not,
however, it can try the luck and execute shell command.

Server's reply is multiline, but alwyas ends with

### 000<optional text>

line. ### is prefix to mark this line, 000 is return code. Return
codes are superset to those used in ftp.

There are few new exit codes defined:

000 don't know; if there were no previous lines, this marks COMPLETE
success, if they were, it marks failure.

001 don't know; if there were no previous lines, this marks
PRELIMinary success, if they were, it marks failure

				Connecting
				~~~~~~~~~~
Client uses "echo FISH:;/bin/sh" as command executed on remote
machine. This should make it possible for server to distinguish FISH
connections from normal rsh/ssh.

				Commands
				~~~~~~~~
#FISH
echo; start_fish_server; echo '### 200'

This command is sent at the begining. It marks that client wishes to
talk via FISH protocol. #VER command must follow. If server
understands FISH protocol, it has option to put FISH server somewhere
on system path and name it start_fish_server.

#VER 0.0.2 <feature1> <feature2> <...>
echo '### 000'

This command is the second one. It sends client version and extensions
to the server. Server should reply with protocol version to be used,
and list of extensions accepted.

VER 0.0.0 <feature2>
### 200

#PWD
pwd; echo '### 200'

Server should reply with current directory (in form /abc/def/ghi)
followed by line indicating success.

#LIST /directory
ls -lLa $1 | grep '^[^cbt]' | ( while read p x u g s m d y n; do echo "P$p $u.$g
S$s
d$m $d $y
:$n
"; done )
ls -lLa $1 | grep '^[cb]' | ( while read p x u g a i m d y n; do echo "P$p $u.$g
E$a$i
dD$m $d $y
:$n
"; done )
echo '### 200'

This allows client to list directory or get status information about
single file. Output is in following form (any line except :<filename>
may be ommited):

P<unix permissions> <owner>.<group>
S<size>
d<3-letters month name> <day> <year or HH:MM>
D<year> <month> <day> <hour> <minute> <second>[.1234]
E<major-of-device>,<minor>
:<filename>
L<filename symlink points to>
<blank line to separate items>

Unix permissions are of form X--------- where X is type of
file. Currently, '-' means regular file, 'd' means directory, 'c', 'b'
means character and block device, 'l' means symbolic link, 'p' means
FIFO and 's' means socket.

'd' has three fields: month (one of strings Jan Feb Mar Apr May Jun
Jul Aug Sep Oct Nov Dec), day of month, and third is either single
number indicating year, or HH:MM field (assume current year in such
case). As you've probably noticed, this is pretty broken; it is for
compatibility with ls listing.

#RETR /some/name
ls -l /some/name | ( read a b c d x e; echo $x ); echo '### 100'; cat /some/name; echo '### 200'

Server sends line with filesize on it, followed by line with ### 100
indicating partial success, then it sends binary data (exactly
filesize bytes) and follows them with (with no preceeding newline) ###
200.

Note that there's no way to abort running RETR command - except
closing the connection.

#STOR <size> /file/name
> /file/name; echo '### 001'; ( dd bs=4096 count=<size/4096>; dd bs=<size%4096> count=1 ) 2>/dev/null | ( cat > %s; cat > /dev/null ); echo '### 200'

This command is for storing /file/name, which is exactly size bytes
big. You probably think I went crazy. Well, I did not: that strange
cat > /dev/null has purpose to discard any extra data which was not
written to disk (due to for example out of space condition).

[Why? Imagine uploading file with "rm -rf /" line in it.]

#CWD /somewhere
cd /somewhere; echo '### 000'

It is specified here, but I'm not sure how wise idea is to use this
one: it breaks stateless-ness of the protocol.

Following commands should be rather self-explanatory:

#CHMOD 1234 file
chmod 1234 file; echo '### 000'

#DELE /some/path
rm -f /some/path; echo '### 000'

#MKD /some/path
mkdir /some/path; echo '### 000'

#RMD /some/path
rmdir /some/path; echo '### 000'

#RENAME /path/a /path/b
mv /path/a /path/b; echo '### 000'

#LINK /path/a /path/b
ln /path/a /path/b; echo '### 000'

#SYMLINK /path/a /path/b
ln -s /path/a /path/b; echo '### 000'

#CHOWN user /file/name
chown user /file/name; echo '### 000'

#CHGRP group /file/name
chgrp group /file/name; echo '### 000'

#READ <offset> <size> /path/and/filename
cat /path/and/filename | ( dd bs=4096 count=<offset/4096> > /dev/null;
dd bs=<offset%4096> count=1 > /dev/null;
dd bs=4096 count=<offset/4096>;
dd bs=<offset%4096> count=1; )

Returns ### 200 on successfull exit, ### 291 on successfull exit when
reading ended at eof, ### 292 on successfull exit when reading did not
end at eof.

#WRITE <offset> <size> /path/and/filename

Hmm, shall we define these ones if we know our client is not going to
use them?


That's all, folks!
						pavel@ucw.cz