summaryrefslogtreecommitdiff
path: root/doc/forum/Allow_overriding_of_symlink_restriction.mdwn
diff options
context:
space:
mode:
authorhttp://www.cse.unsw.edu.au/~willu/ <http://www.cse.unsw.edu.au/~willu/@web>2008-07-18 21:45:35 -0400
committerJoey Hess <joey@kitenet.net>2008-07-18 21:45:35 -0400
commit974a0ec09ee0751d08ef76ac26e2be4a7c11556b (patch)
tree73c31864025a3fcaa9e15e643e364c09439f8af8 /doc/forum/Allow_overriding_of_symlink_restriction.mdwn
parent15fb518cc2bc38a510b54003b59e0152c28c0eec (diff)
Discussion about option to optionally turn off an overly restrictive security measure
Diffstat (limited to 'doc/forum/Allow_overriding_of_symlink_restriction.mdwn')
-rw-r--r--doc/forum/Allow_overriding_of_symlink_restriction.mdwn36
1 files changed, 36 insertions, 0 deletions
diff --git a/doc/forum/Allow_overriding_of_symlink_restriction.mdwn b/doc/forum/Allow_overriding_of_symlink_restriction.mdwn
new file mode 100644
index 000000000..88f9312b4
--- /dev/null
+++ b/doc/forum/Allow_overriding_of_symlink_restriction.mdwn
@@ -0,0 +1,36 @@
+There is currently a restriction in ikiwiki that there cannot be any symlinks in the source path. This is to deal with a security issue discussed [[here|security#index29h2]]. The issue, as I understand it, is that someone might change a symlink and so cause things on the server to be published when the server admin doesn't want them to be.
+
+I think there are two issues here:
+
+ - Symlinks with the source dir path itself, and
+ - Symlinks inside the source directory.
+
+The first appears to me to be less of a security issue. If there is a way for a malicious person to change where that path points, then you have problems this check isn't going to solve. The second is quite clearly a security issue - if someone were to commit a symlink into the source dir they could cause lots of stuff to be published that shouldn't be.
+
+The current code seems to check this constraint at the top of IkiWiki/Render.pm at the start of refresh(). It seems to only check the source dir itself, not the subdirs. Then it uses File::Find to recuse which doesn't follow symlinks.
+
+Now my problem: I have a hosted server where I cannot avoid having a symlink in the source path. I've made a patch to optionally turn off the symlink checking in the source path itself. The patch would still not follow symlinks inside the source dir. This would seem to be ok security-wise for me as I know that path is ok and it isn't going to change on me.
+
+Is there a huge objection to this patch?
+
+(note: patch inline - look at the source to get it. And I didn't re-indent the code when I added the if...)
+
+index 990fcaa..d7cb37e 100644
+--- a/IkiWiki/Render.pm
++++ b/IkiWiki/Render.pm
+@@ -260,6 +260,7 @@ sub prune ($) { #{{{
+
+ sub refresh () { #{{{
+ # security check, avoid following symlinks in the srcdir path
++ if (! $config{allowsrcdirlinks}) {
+ my $test=$config{srcdir};
+ while (length $test) {
+ if (-l $test) {
+@@ -269,6 +270,7 @@ sub refresh () { #{{{
+ $test=dirname($test);
+ }
+ }
++ }
+
+ run_hooks(refresh => sub { shift->() });
+