tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

permissions 

[Imported from Trac: page SftpFrontend, version 20]
davidsarah 2010-05-30 17:50:19 +00:00
parent 71624d6fe4
commit 7328de65ce
1 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
SftpFrontend.md

@ -7,6 +7,8 @@ See source:docs/frontends/FTP-and-SFTP.txt for how to enable and set up the SFTP
Before uploading a file to a Tahoe filesystem, the whole file has to be available. This means that the upload can only start when the file has been closed in the SFTP session. Particularly when writing large files, the client may time out between sending the close request and receiving the response (ticket #1041). This is known to be a problem for at least the WinSCP client, which has a close timeout of 15 seconds.
Since Tahoe uses capability access control rather than Unix-style permissions, the permission bits seen by SFTP clients are handled differently than on a local POSIX filesystem: they are only an approximation chosen to avoid confusing client programs. In particular the 'user', 'group' and 'world' permissions on a Tahoe file will always be the same. It is possible to clear all of the 'w' bits on a file, which will prevent that file from being opened for writing, but note that its directory entry can still be replaced via a write cap to the directory.
### sshfs
@ -26,6 +28,7 @@ The MacFUSE version of sshfs stores "extended attributes" in files with names st
On Mac OS X, TextEdit and vi are known to have problems editing files on a Tahoe-via-sshfs filesystem.
### Gnome virtual filesystem (gvfs)
[gvfs](https://fedoraproject.org/wiki/Features/Gvfs) is a set of filesystem adapters provided with the Gnome window system. It can be used in two ways: either via the [GIO API](http://library.gnome.org/devel/gio/unstable/), or via a FUSE layer called gvfs-FUSE (not to be confused with sshfs).