> > It is _possible_ to make an exception for the 'dropbox' case, and grant > stat() permission to the owner but not let them read the file, since > preventing the owner from reading the file is enforced by the client and > not by the fileserver. > > I'm not sure how desirable that is, though, and making even more > special-cases to the dropbox case doesn't sound appealing...
I think it is just what I need. My user case is ftp server. Every customer has own chrooted directory and the ftp server file space is under /afs When customer log in the customers home directory looks like this: upload ( permissions are "li") donwload ( permissions are "lr) Now customer can upload files to the upload directory and be sure that no one else can read/over write uploaded files (even if customers passwd is stolen). Customer don't know afs-permissions but one thing they do is "ls -la" after uploading files and if output is something like -????????? ? ? ? ? ? uploaded_files they think that uploading is failed. _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
