2 ===================================================================
3 --- IkiWiki.pm (revision 2981)
4 +++ IkiWiki.pm (working copy)
6 memoize("file_pruned");
8 sub defaultconfig () { #{{{
9 - wiki_file_prune_regexps => [qr/\.\./, qr/^\./, qr/\/\./,
10 + wiki_file_prune_regexps => [qr/\.\./, qr/^\.(?!htaccess)/, qr/\/\.(?!htaccess)/,
11 qr/\.x?html?$/, qr/\.ikiwiki-new$/,
12 qr/(^|\/).svn\//, qr/.arch-ids\//, qr/{arch}\//],
13 wiki_link_regexp => qr/\[\[(?:([^\]\|]+)\|)?([^\s\]#]+)(?:#([^\s\]]+))?\]\]/,
17 This lets the site administrator have a `.htaccess` file in their underlay
18 directory, say, then get it copied over when the wiki is built. Without
19 this, installations that are located at the root of a domain don't get the
20 benefit of `.htaccess` such as improved directory listings, IP blocking,
21 URL rewriting, authorisation, etc.
23 > I'm concerned about security ramifications of this patch. While ikiwiki
24 > won't allow editing such a .htaccess file in the web interface, it would
25 > be possible for a user who has svn commit access to the wiki to use it to
26 > add a .htaccess file that does $EVIL.
28 > Perhaps this should be something that is configurable via the setup file
35 Hi, I would like to have my htaccess files in svn repository so ikiwiki would export that file to my webspace with every commit.
37 That way I have revision control on that file too. That may be a security concern, but I trust everybody that has svn commit
38 access and such .htaccess files should not be accessible through wiki cgi. Of course, it could default to 'off'.
40 > See [[debbug 447267]] for a patch for this.