Re: Should webapp enable an apache module if needed?

To: debian-webapps@lists.debian.org
Subject: Re: Should webapp enable an apache module if needed?
From: Tore Anderson <tore@debian.org>
Date: Tue, 10 May 2005 15:21:51 +0200
Message-id: <[🔎] 1115731311.13786.133.camel@echo.e.linpro.no>
Reply-to: debian-webapps@lists.debian.org
In-reply-to: <[🔎] 20050510121328.GA31810@seanius.net>
References: <[🔎] 20050510101954.GE6076@ibook.steinmann.cx> <[🔎] 1115722082.13786.91.camel@echo.e.linpro.no> <[🔎] 20050510121328.GA31810@seanius.net>

* sean finney

> (autogenerating a file in /etc that says "don't edit this file)

  Ick.  That, I believe, violates Policy 10.7.  If the user is not
 permitted to modify it, it is no configuration file, and shouldn't go
 in /etc.

-- 
Tore Anderson

Reply to:

Follow-Ups:
- Re: Should webapp enable an apache module if needed?
  - From: sean finney <seanius@debian.org>

References:
- Should webapp enable an apache module if needed?
  - From: uwe@steinmann.cx (Uwe Steinmann)
- Re: Should webapp enable an apache module if needed?
  - From: Tore Anderson <tore@debian.org>
- Re: Should webapp enable an apache module if needed?
  - From: sean finney <seanius@seanius.net>

Prev by Date: Re: Should webapp enable an apache module if needed?
Next by Date: Re: Should webapp enable an apache module if needed?
Previous by thread: Re: Should webapp enable an apache module if needed?
Next by thread: Re: Should webapp enable an apache module if needed?
Index(es):
- Date
- Thread