Context Navigation

Changes between Version 55 and Version 56 of SftpFrontend

v55	v56
21	21	Since Tahoe uses capability access control rather than Unix-style permissions, the permission bits seen by SFTP clients 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.
22	22
23		See the last section of [[http://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/frontends/FTP-and-SFTP.txt docs/frontends/FTP-and-SFTP.rst] for information on how the SFTP frontend treats immutable and mutable files.
	23	See the last section of [http://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/frontends/FTP-and-SFTP.txt docs/frontends/FTP-and-SFTP.rst] for information on how the SFTP frontend treats immutable and mutable files.
24	24
25	25	The '{{{ctime}}}' and '{{{mtime}}}' attributes will always be the same, and are set from the Tahoe {{{linkmotime}}} timestamp, which is changed only when the link from the parent directory is modified (see the 'About the metadata' section of [source:doc/frontends/webapi.rst webapi.rst]). These fields are not updated when the contents of a mutable file are changed. The SFTP protocol and the server are able to represent dates up to the year 2106, but some clients may print dates incorrectly after 2037.