summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-03-10 09:02:09 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2006-03-10 09:02:09 +0000
commit9ab1c273f601cc7f1d70749b9fc8f58df67ab39f (patch)
treeaec5b28b4e4cf11d0ff51bafbf9d7c07c91c4265 /doc
parent65e3686ead9e443584e2c727eec4ccf32bfad47e (diff)
autowrapper
Diffstat (limited to 'doc')
-rw-r--r--doc/security.mdwn13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/security.mdwn b/doc/security.mdwn
index 575ccbad8..e7936b5a0 100644
--- a/doc/security.mdwn
+++ b/doc/security.mdwn
@@ -1,3 +1,5 @@
+Let's do an ikiwiki security analysis..
+
If you are using ikiwiki to render pages that only you can edit, then there
are no more security issues with this program than with cat(1). If,
however, you let others edit pages in your wiki, then some security issues
@@ -37,3 +39,14 @@ hopefully your web server will not run it.
If your web server does any parsing of special sorts of files (for example,
server parsed html files), then if you let anyone else add files to the wiki,
they can try to use this to exploit your web server.
+
+## --gen-wrapper might generate insecure wrappers
+
+ikiwiki --gen-wrapper is instended to generate a wrapper program that
+runs ikiwiki to update a given wiki. The wrapper can in turn be made suid,
+for example to be used in a [[post-commit]] hook by people who cannot write
+to the html pages, etc.
+
+If the wrapper script is made suid, then any bugs in this wrapper would be
+security holes. The wrapper is written as securely as I know how and
+there's been no problems yet.