[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] anonymous ftp question
- Subject: Re: [cobalt-users] anonymous ftp question
- From: "Brian Curtis" <admin@xxxxxxxxxxx>
- Date: Fri Nov 17 05:37:01 2000
- Organization: Pomfret Computer Technologies
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
> I'm trying to setup an anonymous FTP site where our clients can go in and
> download a select few files I make available. I've created some
directories
> and uploaded files in the /incoming/ directory but when an anonymous user
> logs in they cannot see the files or directories that are available.
This is the "normal" behavior for an anonymous FTP incoming directory.
Which can be changed by modifying the FTP configuration.
> What I want to do is this.
>
> Create an uploads directory within /incoming/ where a user can upload
files
> (if possible, without anyone having the ability to view or download them
> until we approve). All the other directories within /incoming/ (clients,
> tools, misc) I want to be so they can view the contents and download only.
>
> How can I do this?
>
> Thankie,
> Amanda.
I would recommend a directory structure as such:
ftp/
|- incoming/ (for uploaded files, strict permissions)
|- pub/ (for publicly available files, read permission)
|- clients/
|- tools/
|- misc/
the dir "incoming" is normally know as *the* directory to upload to. Since
it is for uploading, the permissions should be as strict as possible (no
read permission necessary). This is why you should separate the outgoing
from the incoming, instead of nesting one within the other. ProFTPDs access
rules are inherited by subdirectories, so unless you really know how to
configure ProFTPD, nesting the incoming/outgoing under the other will be
more work than it's worth.
HTH
--
Brian Curtis