diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20110119/002227.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20110119/002227.html | 119 |
1 files changed, 119 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110119/002227.html b/zarb-ml/mageia-dev/20110119/002227.html new file mode 100644 index 000000000..738474f30 --- /dev/null +++ b/zarb-ml/mageia-dev/20110119/002227.html @@ -0,0 +1,119 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proofreading web applications policy + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proofreading%20web%20applications%20policy&In-Reply-To=%3C20110118233857.GD20740%40sisay.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002226.html"> + <LINK REL="Next" HREF="002228.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proofreading web applications policy</H1> + <B>Michael scherer</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proofreading%20web%20applications%20policy&In-Reply-To=%3C20110118233857.GD20740%40sisay.ephaone.org%3E" + TITLE="[Mageia-dev] Proofreading web applications policy">misc at zarb.org + </A><BR> + <I>Wed Jan 19 00:38:57 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="002226.html">[Mageia-dev] mailing list for new RPMs +</A></li> + <LI>Next message: <A HREF="002228.html">[Mageia-dev] Python Packaging Policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2227">[ date ]</a> + <a href="thread.html#2227">[ thread ]</a> + <a href="subject.html#2227">[ subject ]</a> + <a href="author.html#2227">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Tue, Jan 18, 2011 at 07:07:00PM +0100, Remy CLOUARD wrote: +><i> Hello there, +</I>><i> +</I>><i> I started to have a look at the webapps policy. +</I>><i> +</I>><i> There’s something that has been bugging me for a while, that’s the +</I>><i> apache-centric way of thinking of this policy. +</I>><i> +</I>><i> To me, there are valuable alternatives to apache that deserve to be +</I>><i> treated equally. +</I>><i> Here are the packages that provides webserver +</I>><i> +</I>><i> apache-ssl|apache-mpm-event|apache-mpm-peruser|nginx|lighttpd| +</I>><i> cherokee|apache-mpm-itk|apache-mpm-worker|thttpd|apache-mpm-rsbac| +</I>><i> apache-mpm-prefork|boa +</I>><i> +</I>><i> “These are the files that are susceptible to change during the +</I>><i> application's lifetime. They go in /var/lib/foo. If they are supposed to +</I>><i> be editable by the application directly from the web interface, they +</I>><i> should be owned by apache user and apache group.” +</I>><i> +</I>><i> Could we create a generic group (webserver for instance) to allow +</I>><i> webapps to play nice with these webserver ? +</I> +Wouldn't it be a security problem to have different +daemon sharing the same uid ? + +><i> Same goes for logfiles and config files containing sensitive +</I>><i> informations. +</I>><i> +</I>><i> I would also be in favor of creating subpackages for webapps that +</I>><i> provides better integration with apache such as files in +</I>><i> /etc/httpd/conf/webapps.d/. +</I> +That would make life difficult for user, as they would have to answer questions +about things that the package manager would have to figure by +itself. + +( like deduce what configuration file would be used based on system information ) + +I think we should aim to reduce questions rather to ask more. + +><i> That way, webapps should have a Requires on webserver, and the +</I>><i> subpackage should have one on apache. +</I>><i> +</I>><i> Another issue is the owner of /var/www. This directory is owned by +</I>><i> apache-conf. Could we instead make a generic package called +</I>><i> webserver-data for instance that would provide it ? This way each +</I>><i> package providing webserver would have to require webserver-data. +</I> +Put it in filesystem rpm then. And technically, shouldn't +we follow lsb and use /srv ? + +><i> Finally, that may be a little cosmetic detail, but I would prefer +</I>><i> template files for apache to be in a separate file in SOURCES/ that’s +</I>><i> included instead of creating it in the spec like: +</I>><i> cat > %{buildroot}%{_webappconfdir}/%{name}.conf <<EOF +</I> +Well, why ? +Inline configfile can use macros, that's usually a way to be sure +that /var/ww/%{name} is properly set +-- +Michaeli Scherer +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002226.html">[Mageia-dev] mailing list for new RPMs +</A></li> + <LI>Next message: <A HREF="002228.html">[Mageia-dev] Python Packaging Policy +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2227">[ date ]</a> + <a href="thread.html#2227">[ thread ]</a> + <a href="subject.html#2227">[ subject ]</a> + <a href="author.html#2227">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |