sftp transfer status feedback?

[Damien Miller]

On 24 May 2001, Patrick Higgins wrote:

> My project seems to be getting more and more difficult...my sftp-server
> needs to be able to track successful uploads and downloads, and to
> report these to a an external program when the client disconnects.
>
> It looks like the sftp protocol is driven entirely by the client--it
> makes requests and receives response codes and data. The server doesn't
> seem to receive any feedback from the client about whether or not
> something completed successfully. For instance, a client might request
> an open followed by enough reads to get half of the file, and then
> request a close. Without coding sophisticated (and mostly useless)
> tracking, it would be difficult to know if the file was read in it's
> entirety. Is my (limited) understanding more or less correct?

This is correct - draft-ietf-secsh-filexfer looks a lot like the
Unix block API, others have compared it with NFS.

You could infer whether entire files were read, etc by looking at
lseek(fd, 0, SEEK_CUR) at close() time, or by instrumenting
"struct Handle" further.

-d

-- 
| Damien Miller <djm at mindrot.org> \ ``E-mail attachments are the poor man's
| http://www.mindrot.org          /   distributed filesystem'' - Dan Geer