diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/htmlsanitization.mdwn | 30 | ||||
| -rw-r--r-- | doc/ikiwiki.setup | 2 | ||||
| -rw-r--r-- | doc/news/sanitization.html | 7 | ||||
| -rw-r--r-- | doc/security.mdwn | 19 | ||||
| -rw-r--r-- | doc/setup.mdwn | 2 | ||||
| -rw-r--r-- | doc/todo/done/1.0_release_blockers.mdwn (renamed from doc/todo/1.0_release_blockers.mdwn) | 0 | ||||
| -rw-r--r-- | doc/usage.mdwn | 5 |
7 files changed, 55 insertions, 10 deletions
diff --git a/doc/htmlsanitization.mdwn b/doc/htmlsanitization.mdwn new file mode 100644 index 000000000..617753e86 --- /dev/null +++ b/doc/htmlsanitization.mdwn @@ -0,0 +1,30 @@ +When run with the --sanitize switch, which is turned on by default (see +[[usage]], ikiwiki sanitizes the html on pages it renders to avoid XSS +attacks and the like. + +ikiwiki excludes all html tags and attributes except for those that are +whitelisted using the same lists as used by Mark Pilgrim's Universal Feed +Parser, documented at <http://feedparser.org/docs/html-sanitization.html>. +Notably it strips `style`, `link`, and the `style` attribute. + +ikiwiki uses the HTML::Scrubber perl module to perform its html +sanitisation, and this perl module also deals with various entity encoding +tricks. + +While I beleive that this makes ikiwiki as resistant to malicious html +content as anything else on the web, I cannot guarantee that it will +actually protect every user of every browser from every browser security +hole, badly designed feature, etc. I can provide NO WARRANTY, like it says +in ikiwiki's [[GPL]] license. + +The web's security model is *fundamntally broken*; ikiwiki's HTML +sanitisation is only a patch on the underlying gaping hole that is your web +browser. + +---- + +Some examples of embedded javascript that won't be let through. + +<span style="background: url(javascript:window.location='http://example.org/')">test</span> +<span style="any: expression(window.location='http://example.org/')">test</span> +<span style="any: expression(window.location='http://example.org/')">test</span> diff --git a/doc/ikiwiki.setup b/doc/ikiwiki.setup index c77385583..9775b3194 100644 --- a/doc/ikiwiki.setup +++ b/doc/ikiwiki.setup @@ -50,4 +50,6 @@ use IkiWiki::Setup::Standard { rss => 1, # Use the Hyper Estraier search engine? #hyperestraier => 1, + # Sanitize html? + sanitize => 1, } diff --git a/doc/news/sanitization.html b/doc/news/sanitization.html new file mode 100644 index 000000000..6ce254157 --- /dev/null +++ b/doc/news/sanitization.html @@ -0,0 +1,7 @@ +ikiwiki's main outstanding security hole, lack of [[HtmlSanitization]] has +now been addressed. ikiwiki now sanitizes html by default. + +If only trusted parties can edit your wiki's content, then you might want +to turn this sanitization back off to allow use of potentially dangerous +tags. To do so, pass --no-sanitize or set "sanitize => 0," in your +[[ikiwiki.setup]]. diff --git a/doc/security.mdwn b/doc/security.mdwn index bc5e318c9..00b8e8824 100644 --- a/doc/security.mdwn +++ b/doc/security.mdwn @@ -8,21 +8,18 @@ to be kept in mind. # Probable holes -## html attacks +## XSS holes in CGI output -ikiwiki does not attempt to do any santization of the html on the wiki. -[[MarkDown]] allows embedding of arbitrary html into a markdown document. If -you let anyone else edit files on the wiki, then anyone can have fun exploiting -the web browser bug of the day. This type of attack is typically referred -to as an XSS attack ([google](http://www.google.com/search?q=xss+attack)). +ikiwiki has not yet been audited to ensure that all cgi script output is +sanitised to prevent XSS attacks. ## image files etc attacks If it enounters a file type it does not understand, ikiwiki just copies it into place. So if you let users add any kind of file they like, they can -upload images, movies, windows executables, css files, etc. If these files -exploit security holes in the browser of someone who's viewing the wiki, -that can be a security problem. +upload images, movies, windows executables, css files, etc (though not html +files). If these files exploit security holes in the browser of someone +who's viewing the wiki, that can be a security problem. Of course nobody else seems to worry about this in other wikis, so should we? @@ -193,3 +190,7 @@ would still be possible to use this attack to confuse ikiwiki into rendering the wrong thing. This is not currently possible, but must be kept in mind in the future when for example adding support for generating html pages from source with some other extension. + +## XSS attacks in page content + +ikiwiki supports [[HtmlSanitistion]], though it can be turned off. diff --git a/doc/setup.mdwn b/doc/setup.mdwn index 29ce068b8..818335257 100644 --- a/doc/setup.mdwn +++ b/doc/setup.mdwn @@ -9,7 +9,7 @@ optional support for commits from the web. Ikiwiki requires [[MarkDown]] be installed, and also uses the following perl modules: `CGI::Session` `CGI::FormBuilder` (version 3.02.02 or newer) `HTML::Template` `Mail::SendMail` `Time::Duration` `Date::Parse` - (libtimedate-perl) + (libtimedate-perl), `HTML::Scrubber` 2. Create the subversion repository for your wiki. diff --git a/doc/todo/1.0_release_blockers.mdwn b/doc/todo/done/1.0_release_blockers.mdwn index 01ec8193b..01ec8193b 100644 --- a/doc/todo/1.0_release_blockers.mdwn +++ b/doc/todo/done/1.0_release_blockers.mdwn diff --git a/doc/usage.mdwn b/doc/usage.mdwn index ca805ce33..34e6bd1d4 100644 --- a/doc/usage.mdwn +++ b/doc/usage.mdwn @@ -167,6 +167,11 @@ These options configure the wiki. Currently allows locking of any page, other powers may be added later. May be specified multiple times for multiple admins. +* --sanitize + + Enable [[HtmlSanitization]] of wiki content. On by default, disable with + --no-sanitize. + * --hyperestraier Enables use of the [[HyperEstraier]] search engine for full test page |