[Proftpd-user] bug or misfeature with "limit" groups, inheritance?

Stephen Dowdy <[email protected]>
Newsgroups gmane.network.proftpd.user
Message-ID <[email protected]>
# proftpd --version
ProFTPD Version 1.3.5b


for anonymous i have:

     <Directory *>
         <Limit WRITE>
             DenyAll
         </Limit>
     </Directory>


and later on i have:

     <Directory incoming>
         <Limit ALL>
             AllowAll
         </Limit>
     </Directory>
     <Directory incoming/*>
         <Limit ALL>
             AllowAll
         </Limit>
     </Directory>


This presents me with a DISALLOWance on the client end when i try to 'put' a file to /incoming/.
(i believe the "incoming/*" should be superflouus, but i'm still debugging)


I found that If i change "ALL" to "WRITE ALL" i can now write.  e.g.:

         <Limit WRITE ALL

So.....  my understanding is that "ALL" should mean *ALL*, not "Everything but some implicit previous control"
Apparently "WRITE" is somehow being processed as a LITERAL string that doesn't match "ALL".
(not as a "group" of underlying FTP commands as the documentation suggests).

What am i missing here -- and what's the best-practice way to do this?

thanks,
--stephen

-- 
Stephen Dowdy  -  Systems Administrator  -  NCAR/RAL
303.497.2869   -  [email protected]        -  http://www.ral.ucar.edu/~sdowdy/



_______________________________________________
ProFTPD Users List   <[email protected]>
Unsubscribe problems?
http://www.proftpd.org/list-unsub.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.