public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stuart Herbert <stuart@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] webapp-config and webapps
Date: Sat, 30 Oct 2004 11:17:39 +0100	[thread overview]
Message-ID: <200410301117.39860.stuart@gentoo.org> (raw)
In-Reply-To: <200410291155.32852.pauldv@gentoo.org>

On Friday 29 October 2004 10:55, Paul de Vrieze wrote:
> Let's say how I would do this if I were an administrator for such a server.
> Well I'd take the easy road of doing the following:
> - Make a webpage that users/customers can select the desired webapps for
> their virtual host, including the version. With a big-fat warning that
> autoupdating by the app itself doesn't work.
> - Have that webpage append to a pending-transformation list.
> - Have a root cronjob that parses (strictly) the pending-transformation
> list and runs webapp-config for eacht of those transformations. Then the
> pending list is flushed.
>
> As the administrator I now only need to select the offered apps, the rest
> is left to the users.

/me nods.  I want to make it possible for others to write that kind of app.  
But you don't need webapp-config to be setuid to do that.  All you need to do 
is ensure that all files are owned by the user that apache runs as.

You can achieve that securely by using the experimental perchild MPM (which 
will soon be available through Portage), or by running each site in its own 
chroot environment.

> I still consider it bad design. Even though I understand the reasons.

Sorry - that statement's ambiguious.  What's the "it" that you are refering 
to?

Best regards,
Stu
-- 
Stuart Herbert                                              stuart@gentoo.org
Gentoo Developer                                       http://www.gentoo.org/
                                                   http://stu.gnqs.org/diary/

GnuPG key id# F9AFC57C available from http://pgp.mit.edu
Key fingerprint = 31FB 50D4 1F88 E227 F319  C549 0C2F 80BA F9AF C57C
--

--
gentoo-portage-dev@gentoo.org mailing list


  reply	other threads:[~2004-10-30 10:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-28 20:02 [gentoo-portage-dev] webapp-config and webapps Wendall Cada
2004-10-28 20:20 ` Paul de Vrieze
2004-10-28 20:34   ` Wendall Cada
2004-10-28 20:55     ` Wendall Cada
2004-10-28 21:19       ` Stuart Herbert
2004-10-28 21:28       ` Stuart Herbert
2004-10-28 21:13     ` Stuart Herbert
2004-10-28 21:48       ` Anthony Gorecki
2004-10-28 22:13         ` Stuart Herbert
2004-10-28 22:52           ` Anthony Gorecki
2004-10-28 23:31             ` Stuart Herbert
2004-10-29  1:04               ` Anthony Gorecki
2004-10-29  9:55               ` Paul de Vrieze
2004-10-30 10:17                 ` Stuart Herbert [this message]
2004-10-30 21:24                   ` Paul de Vrieze
2004-10-28 20:52 ` Grant Goodyear
2004-10-31 16:38   ` [gentoo-portage-dev] Setting an env var for a specific ebuild felix
2004-10-31 17:02     ` Sri Gupta
2004-10-31 18:22       ` Michael Stewart

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200410301117.39860.stuart@gentoo.org \
    --to=stuart@gentoo.org \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox