From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] CGI
Date: Tue, 12 Feb 2002 20:56:41 -0500 [thread overview]
Message-ID: <0b2d2983d74801054ecef163df5906a7@plan9.bell-labs.com> (raw)
In increasing order of complexity, I see four choices:
1. Make the file world writable (chmod 666).
Then anyone on your server can edit the file;
maybe you don't like that.
2. Make the file world writable but append-only,
restructuring your program so that it's okay that
the file is only appended to. Then anyone on the
server can append to the file, but you can't lose
a previous state of the file.
3. Run the web server as alice through whatever
mechanism you like. Then if a script kiddie hacks
it, he can pretend to be alice.
4. Write a file server to moderate access to B
so that the web server programs don't have to
be privileged and you can restrict the set of
allowed operations as much as you want.
As an example, if I were particularly concerned,
I could run the wikifs as a special "wiki" user
and then the web server programs could still
interact with wikifs through the file system as none.
In fact, I'm not concerned, so I run the wikifs
as none, and all the wiki data is chmod 666.
Russ
next reply other threads:[~2002-02-13 1:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 1:56 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-14 13:01 arisawa
2002-02-13 3:20 presotto
2002-02-13 1:17 Russ Cox
2002-02-13 0:34 arisawa
2002-02-13 0:05 arisawa
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=0b2d2983d74801054ecef163df5906a7@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).