Quite a while ago, Greg Chaplin asked re FTP ...

>What additional security can be used?  What other capabilities are
>required for the ftp user or group?  I want to be able to ensure
>that the ftp user cannot do anything other than upload or download
>files to/from the ftp group - how can I do this?

Two things to watch out for:

a) The file access will basically restricted to what the user
   logging on can access according to file system security (or
   whatever VESOFT offers in addition).

   Thus it will usually possible to GET files from PUB.SYS (for
   example) and maybe even PUT files to the HFS directory /tmp.

   You should be aware of this! (Or use sophisticated ACD's)

b) It is a good idea to remove BA capability from the user that
   the FTP client is supposed to logon as. Otherwise they might
   attempt to PUT a job stream file and STREAM it using the SITE
   command of FTP/iX.

   You should be aware of this, too!

As far as I understand there is no "anonymous ftp" possible with
the current version of FTP/iX (and I have no knowledge if there
are enhancements planned). Moreover there is no chroot() or alike
that would allow access restrictions to just one subdirectory.

You might want to have a look into OfficeExtend FTP at the web
site of 3k Associates (http://www.3k.com) as it might offer things
like anonymous ftp. (Neither a plug nor a recommendation, I have
never used it, just noticed it's existence!)

Regards, Lars/iX ([log in to unmask])

PS: There was a lively discussion about security aspects of
    JFTPSTRT.ARPA.SYS at the SIGWEB meeting this IPROF... One
    result was, that serving files for users to download might
    sometimes be "safer" with a web server instead of "ftp get"
    as the web server does not offer an "ftp put" equivalent
    and has config options to only give access to selected
    (sub)directories of the 3000 file system.