diff --git a/Doxyfile b/Doxyfile index 9c31af60..3fed194f 100644 --- a/Doxyfile +++ b/Doxyfile @@ -4,7 +4,7 @@ # Project related configuration options #--------------------------------------------------------------------------- PROJECT_NAME = HTML Purifier -PROJECT_NUMBER = 1.3.0 +PROJECT_NUMBER = 1.3.2 OUTPUT_DIRECTORY = "C:/Documents and Settings/Edward/My Documents/My Webs/htmlpurifier/docs/doxygen" CREATE_SUBDIRS = NO OUTPUT_LANGUAGE = English diff --git a/NEWS b/NEWS index a4e27fb0..e7ecfe4d 100644 --- a/NEWS +++ b/NEWS @@ -9,6 +9,20 @@ NEWS ( CHANGELOG and HISTORY ) HTMLPurifier . Internal change ========================== +1.3.2, released 2006-12-25 +! HTMLPurifier object now accepts configuration arrays, no need to manually + instantiate a configuration object +! Context object now accessible to outside +! Added enduser-youtube.html, explains how to embed YouTube videos. See + also corresponding smoketest preserveYouTube.php. +! Added purifyArray(), which takes a list of HTML and purifies it all +! Added static member variable $version to HTML Purifier with PHP-compatible + version number string. +- Fixed fatal error thrown by upper-cased language attributes +- printDefinition.php: added labels, added better clarification +. HTMLPurifier_Config::create() added, takes mixed variable and converts into + a HTMLPurifier_Config object. + 1.3.1, released 2006-12-06 ! Added HTMLPurifier.func.php stub for a convenient function to call the library - Fixed bug in RemoveInvalidImg code that caused all images to be dropped diff --git a/TODO b/TODO index b29e320f..7bfd2389 100644 --- a/TODO +++ b/TODO @@ -10,6 +10,7 @@ TODO List 1.4 release # More extensive URI filtering schemes (see docs/proposal-new-directives.txt) # Allow for background-image and list-style-image (intrinsically tied to above) + # Add hooks for custom behavior (for instance, YouTube preservation) - Aggressive caching ? Rich set* methods and config file loaders for HTMLPurifier_Config ? Configuration profiles: sets of directives that get set with one func call @@ -66,7 +67,6 @@ Unknown release (on a scratch-an-itch basis) - Append something to duplicate IDs so they're still usable (impl. note: the dupe detector would also need to detect the suffix as well) - Have 'lang' attribute be checked against official lists - - Docs on how to embed YouTube videos (and friends) without patches Encoding workarounds - Non-lossy dumb alternate character encoding transformations, achieved by @@ -84,7 +84,18 @@ Requested 3. Extend the tag exclusion system to specify whether or not the contents should be dropped or not (currently, there's code that could do something like this if it didn't drop the inner text too.) - - Accept array input, by iterating and purifying all of the items + - More user-friendly warnings when %HTML.Allow* attempts to specify a + tag or attribute that is not supported + - Allow specifying global attributes on a tag-by-tag basis in + %HTML.AllowAttributes + - Parse TinyMCE whitelist into our %HTML.Allow* whitelists + - XSS-attempt detection + - More user-friendly warnings when %HTML.Allow* attempts to specify a + tag or attribute that is not supported + - Allow specifying global attributes on a tag-by-tag basis in + %HTML.AllowAttributes + - Parse TinyMCE whitelist into our %HTML.Allow whitelists + - XSS-attempt detection Wontfix - Non-lossy smart alternate character encoding transformations (unless diff --git a/docs/enduser-youtube.html b/docs/enduser-youtube.html new file mode 100644 index 00000000..3e363267 --- /dev/null +++ b/docs/enduser-youtube.html @@ -0,0 +1,179 @@ + + +
+ + + + +Clients like their YouTube videos. It gives them a warm fuzzy feeling when +they see a neat little embedded video player on their websites that can play +the latest clips from their documentary "Fido and the Bones of Spring". +All joking aside, the ability to embed YouTube videos or other active +content in their pages is something that a lot of people like.
+ +This is a bad idea. The moment you embed anything untrusted,
+you will definitely be slammed by a manner of nasties that can be
+embedded in things from your run of the mill Flash movie to
+Quicktime movies.
+Even img
tags, which HTML Purifier allows by default, can be
+dangerous. Be distrustful of anything that tells a browser to load content
+from another website automatically.
Luckily for us, however, whitelisting saves the day. Sure, letting users +include any old random flash file could be dangerous, but if it's +from a specific website, it probably is okay. If no amount of pleading will +convince the people upstairs that they should just settle with just linking +to their movies, you may find this technique very useful.
+ +Below is custom code that allows users to embed +YouTube videos. This is not favoritism: this trick can easily be adapted for +other forms of embeddable content.
+ +Usually, websites like YouTube give us boilerplate code that you can insert +into your documents. YouTube's code goes like this:
+ ++<object width="425" height="350"> + <param name="movie" value="http://www.youtube.com/v/AyPzM5WK8ys" /> + <param name="wmode" value="transparent" /> + <embed src="http://www.youtube.com/v/AyPzM5WK8ys" + type="application/x-shockwave-flash" + wmode="transparent" width="425" height="350" /> +</object> ++ +
There are two things to note about this code:
+ +<embed>
is not recognized by W3C, so if you want
+ standards-compliant code, you'll have to get rid of it.What point 2 means is that if we have code like <span
+class="embed-youtube">AyPzM5WK8ys</span>
your
+application can reconstruct the full object from this small snippet that
+passes through HTML Purifier unharmed.
+<?php + +class HTMLPurifierX_PreserveYouTube extends HTMLPurifier +{ + function purify($html, $config = null) { + $pre_regex = '#<object[^>]+>.+?'. + 'http://www.youtube.com/v/([A-Za-z0-9]+).+?</object>#'; + $pre_replace = '<span class="youtube-embed">\1</span>'; + $html = preg_replace($pre_regex, $pre_replace, $html); + $html = parent::purify($html, $config); + $post_regex = '#<span class="youtube-embed">([A-Za-z0-9]+)</span>#'; + $post_replace = '<object width="425" height="350" '. + 'data="http://www.youtube.com/v/\1">'. + '<param name="movie" value="http://www.youtube.com/v/\1"></param>'. + '<param name="wmode" value="transparent"></param>'. + '<!--[if IE]>'. + '<embed src="http://www.youtube.com/v/\1"'. + 'type="application/x-shockwave-flash"'. + 'wmode="transparent" width="425" height="350" />'. + '<![endif]-->'. + '</object>'; + $html = preg_replace($post_regex, $post_replace, $html); + return $html; + } +} + +$purifier = new HTMLPurifierX_PreserveYouTube(); +$html_still_with_youtube = $purifier->purify($html_with_youtube); + +?> ++ +
There is a bit going on here, so let's explain.
+ +HTMLPurifierX
because it's
+ userspace code. Don't use HTMLPurifier
in front of your
+ class, since it might clobber another class in the library.new HTMLPurifier
to new
+ HTMLPurifierX_PreserveYouTube
. There's other ways to go about
+ doing this: if you were calling a function that wrapped HTML Purifier,
+ you could paste the PHP right there. If you wanted to be really
+ fancy, you could make a decorator for HTMLPurifier.There are a number of possible problems with the code above, depending +on how you look at it.
+ +The width and height of the final YouTube movie cannot be adjusted. This +is because I am lazy. If you really insist on letting users change the size +of the movie, what you need to do is package up the attributes inside the +span tag (along with the movie ID). It gets complicated though: a malicious +user can specify an outrageously large height and width and attempt to crash +the user's operating system/browser. You need to either cap it by limiting +the amount of digits allowed in the regex or using a callback to check the +number.
+ +By allowing this code onto our website, we are trusting that YouTube has +tech-savvy enough people not to allow their users to inject malicious +code into the Flash files. An exploit on YouTube means an exploit on your +site. Even though YouTube is run by the reputable Google, it +doesn't +mean they are +invulnerable. +You're putting a certain measure of the job on an external provider (just as +you have by entrusting your user input to HTML Purifier), and +it is important that you are cognizant of the risk.
+ +This should go without saying, but if you're going to adapt this code +for Google Video or the like, make sure you do it right. It's +extremely easy to allow a character too many in the final section and +suddenly you're introducing XSS into HTML Purifier's XSS free output. HTML +Purifier may be well written, but it cannot guard against vulnerabilities +introduced after it has finished.
+ +It would probably be a good idea if this code was added to the core +library. Look out for the inclusion of this into the core as a decorator +or the like.
+ + + \ No newline at end of file diff --git a/docs/index.html b/docs/index.html index 26d37e2a..12d839db 100644 --- a/docs/index.html +++ b/docs/index.html @@ -23,7 +23,10 @@ information for casual developers using HTML Purifier.Click here to see the unpurified version (breaks validation).
+ + +