aboutsummaryrefslogtreecommitdiff
path: root/doc/plugins/contrib
diff options
context:
space:
mode:
authorfr33domlover <fr33domlover@web>2014-10-24 06:19:54 -0400
committeradmin <admin@branchable.com>2014-10-24 06:19:54 -0400
commitb531e56eef5eff5aea79c343d6d15295768f5b32 (patch)
treebe5f5e378f9b5e0a70c74f60c724530284f8f3ec /doc/plugins/contrib
parentbb964f69a3a5a4554fb9351b93fd98a3af7e3c3a (diff)
downloadikiwiki-b531e56eef5eff5aea79c343d6d15295768f5b32.tar
ikiwiki-b531e56eef5eff5aea79c343d6d15295768f5b32.tar.gz
Update comment
Diffstat (limited to 'doc/plugins/contrib')
-rw-r--r--doc/plugins/contrib/compile/discussion.mdwn4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/plugins/contrib/compile/discussion.mdwn b/doc/plugins/contrib/compile/discussion.mdwn
index 7777750ec..96269d4e4 100644
--- a/doc/plugins/contrib/compile/discussion.mdwn
+++ b/doc/plugins/contrib/compile/discussion.mdwn
@@ -7,7 +7,9 @@ Problem: Any user can change the command to something dangerous that deletes fil
causes irreversible damage to the system. I can even happen by mistake.
Suggestion: Add an option to the setup file that forbids to override the build command in the
-directive, and then only the setup file can configure build commands (if you want).
+directive, and then only the setup file can configure build commands (if you want). Another
+idea, an option to validate the build command, either against a regex or using an arbitrary
+script specified in setup file - then e.g. you can choose which commands are allowed.
What do you think?