From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <2c7e553ddb8fda4e20382c4a3b730a76@quintile.net>
From: "Steve Simon" <steve@quintile.net>
Date: Fri, 18 Apr 2008 19:00:44 +0100
To: 9fans@9fans.net
In-Reply-To: <20080416023112.389B81E8C56@holo.morphisms.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] sshserve.c
Topicbox-Message-UUID: 947ab30c-ead3-11e9-9d60-3106f5b1d025

Sshfs uses ssh to start a file server program (generally called sftp) on the remote server.

Under sshv2 this is described as an external subsystem, i.e. a specific message is sent
to the server to start the file server subsystem.

Under sshv1 which is what the plan9 ssh server supports, the client needs to envoke
sftp binary directly.

I believe the sftp binary from the openssh port should "just work" if the fuse sshfs port
is capable of working with sshv1 and being told the command to send.

sftp in this context is unrelated to the port 115 simple file transfer protocol (sadly also
known as SFTP) nor to the traditional port 21 ftp server.

an sftp client for plan9 has been on my todo list for... years.

-Steve