X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/32200025ccdef4ff43c7bf90eeb44699844b704b..2198b5d4e5864df4719f1f6da7afcafcfdd5dc18:/doc/forum/Apache_XBitHack.mdwn?ds=sidebyside

diff --git a/doc/forum/Apache_XBitHack.mdwn b/doc/forum/Apache_XBitHack.mdwn
index 5def2f817..d5da0825e 100644
--- a/doc/forum/Apache_XBitHack.mdwn
+++ b/doc/forum/Apache_XBitHack.mdwn
@@ -13,3 +13,16 @@ I gather from the [[security]] page that having the executable bit set on files
 > would result in a html page that can be run as an executable. So an
 > option that makes all files rendered from mdwn or other markups 
 > get the x bit set would be pretty safe even with untrusted editors. --[[Joey]] 
+
+>> So how about this: if something has a page-type (i.e. mdwn or whatever authorized page types there are)
+>> then add something at the end of the process (would that be the "changes" hook?)
+>> which sets the x bit on the generated page file.  Would that work?
+
+>> Or is there a way to say "tell me all the generated files that end in .html" and use that as a list to start from?
+
+>> --[[KathrynAndersen]]
+
+>>> Yes, the `change` hook is passed the names of source files that got
+>>> built. Use `pagetype` to check which got htmlized (and filter out ones
+>>> that got copied), and then use `htmlpage` to get the name of the html
+>>> file that was generated, and chmod it. --[[Joey]]