Anonymous FTP uses incoming folder, why?

[thewitt]

Where is proftpd being told to use the incoming directory for an anonymous ftp setup?

I can't find any reference to the incoming directory in any of the config files for proftpd.

What I'm trying to do is set up limit rules for anonymous ftp users so that they can write files but not read them back. Anonymous FTP access today opens up the directory for warez users to share files all they want... They found my system in three days and transferred 150g a day until I found them tonight...

I've have placed the following .ftpaccess file inside the incoming directory to restrict files from being downloaded - hoping that they will get tired of uploading files that cannot be downloaded - but I would rather not use a .ftpaccess file for this if I can avoid it.

<Limit ALL>
DenyAll
</Limit>
<Limit CDUP CWD XCWD XCUP STOR STOU>
AllowAll
</Limit>

Thanks,

-t

 

[ramdiamond]

Have you tried to run "grep -r 'incoming' /etc" from ssh?

 

[DirectAdmin Support]

Hello,

I don't believe it's set anywhere.
It's just chmod to allow write, but not directory read.
Anonymous logins run as "nobody".
Check the chmod permissions on your incoming folder.

drwx--x-wx

The .ftpaccess would allow more control over these types of settings, as you've described.

John