Opened at 2012-09-18T23:56:06Z
Last modified at 2015-11-01T21:59:47Z
#1811 new enhancement
9P frontend — at Initial Version
| Reported by: | davidsarah | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | undecided |
| Component: | code-frontend | Version: | 1.9.2 |
| Keywords: | 9p sftp pycrypto-lib | Cc: | |
| Launchpad Bug: |
Description
9P is a POSIXish remote filesystem protocol somewhat like SFTP (protocol spec). This ticket is to write a 9P frontend that would probably be implemented alongside other frontend protocols — web-API, SFTP and FTP — as part of a gateway node.
Just as we do for SFTP, we'd have to deal with the impedence mismatch between Tahoe's access control model and 9P's, by faking permissions sufficient to satisfy 9P clients. It is probably not necessary to distinguish owner, group and world permissions.
There is a py9p library we could use to implement the 9P server. It uses blocking socket calls but they're nicely factored into a single short class (py9p.Sock), so could easily be changed. It also depends on PyCrypto; again this dependency is fairly nicely factored (into py9p.pki and one method of py9p.sk1) so could be changed to use pycryptopp, say.
The local filesystem server example code seems as though it would be reasonably easy to adapt to call into the SFTP frontend's internal POSIXish interface (i.e. with the 9P server code taking the place of Twisted's SFTP server) instead of making OS calls.
