|
What is the general task the customer is trying to solve?
It sounds like these folks need to use some basic non-default proxies
to control the FAL default directory, and use this in conjunction with
ACLs to set up a read-only" directory, and a "write-only" directory.
There is no perceptible difference (as far as the security model is
concerned) between copying a file into a remote directory via FAL,
and editing a file (creating it) in a remote directory via FAL.
(And things get really "interesting" when one tries to mix read and
write access to a single directory.)
It is possible to use execute-only access on the parent FAL$SERVER
directory to reduce the visibility of any files present in the remote
directory. (And a set of options=default ACE entries to alter the
ownership on the files created in the directory can be used to alter
the accessability of a file, once created, in the remote directory.
This can help in the implementation of a "write-only" directory.)
--
There are non-standard extensions on some webservers that implement
"file uploads to the server". Making files available for viewing or
downloading from a webserver is trivial, and this can be combined
with a "write-only" "submission" FAL directory...
|