Return-Path: Delivered-To: apmail-httpd-docs-archive@httpd.apache.org Received: (qmail 11127 invoked by uid 500); 20 Aug 2002 14:24:20 -0000 Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: docs@httpd.apache.org Delivered-To: mailing list docs@httpd.apache.org Received: (qmail 11116 invoked from network); 20 Aug 2002 14:24:19 -0000 Message-ID: <3D62510F.2040502@slive.ca> Date: Tue, 20 Aug 2002 10:24:15 -0400 From: Joshua Slive User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020721 X-Accept-Language: en-us, en, fr MIME-Version: 1.0 To: docs@httpd.apache.org Subject: Re: Security docs References: <02082009435001.28849@rigmor> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Thomas Sj=F6gren wrote: > In the TODO file better organization / more content is wanted for the=20 > security documentation and since i now (finally) got some time left=20 > over this weekend i thought i would update the doc with more info. >=20 > any ideas/recommendations of what to write about? Personally, I'm stumped about what to do with that doc, or I would have=20 taken a stab at it myself. The problem is that "security" means so many = things (authentication/authorization/access control/ssl/tls/filesystem=20 permissions/properly audited cgi/ssi/etc/etc/etc). Perhaps the best we can do is have a listing of some "best practices"=20 that we recommend to users. Joshua. --------------------------------------------------------------------- To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org For additional commands, e-mail: docs-help@httpd.apache.org