The latter - <br>
<br>
Having the uploads/directory automatically receive a .htaccess file containing the
<div class="indent"><code>Order Deny,Allow</code><br> <code>Deny from all,</code>
</div>
along with having $EnableDirectDownload=0; in the local/config.php<br>
<br>
- is what I was suggesting/requesting, since it (appears to) make things work the way I always thought they already did.<br>
<br>
If not that, then somehow the fact that uploaded files do NOT have the
same read-protection as the wikigroups with which they're associated
should be much more prominently discussed. Perhaps as part of the
"Securing your Wiki Checklist" that's being discussed.<br><br><div><span class="gmail_quote">On 12/7/05, <b class="gmail_sendername">Patrick R. Michaud</b> <<a href="mailto:pmichaud@pobox.com">pmichaud@pobox.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Answering a separate item.<br><br>On Wed, Dec 07, 2005 at 01:35:59PM -0600, Tegan Dowling wrote:
<br>> (BTW: could Secure Attachments (the version in which the special .htaccess<br>> file is included in the uploads directory) be considered for the core<br>> distribution?)<br><br>By this are you asking for the information in Secure Attachments to
<br>be included in the core documentation, or are you asking that the uploads/<br>directory automatically receive a .htaccess file?<br><br>Pm<br><br></blockquote></div><br>