mirror of
https://github.com/ezyang/htmlpurifier.git
synced 2025-03-23 14:27:02 +00:00
Fix a few things in the YouTube documentation as mentioned by Everah and kuza55 (sorry kuza55, still haven't acted completely on your requests).
git-svn-id: http://htmlpurifier.org/svnroot/htmlpurifier/trunk@619 48356398-32a2-884e-a903-53898d9a118a
This commit is contained in:
parent
688b1833f5
commit
4c54283642
@ -26,9 +26,9 @@ content in their pages is something that a lot of people like.</p>
|
|||||||
you will definitely be slammed by a manner of nasties that can be
|
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
|
embedded in things from your run of the mill Flash movie to
|
||||||
<a href="http://blog.spywareguide.com/2006/12/myspace_phish_attack_leads_use.html">Quicktime movies</a>.
|
<a href="http://blog.spywareguide.com/2006/12/myspace_phish_attack_leads_use.html">Quicktime movies</a>.
|
||||||
Allowing users to tell the browser to load content from other websites
|
Even <code>img</code> tags, which HTML Purifier allows by default, can be
|
||||||
is intrinsically dangerous: there already security risks associated with
|
dangerous. Be distrustful of anything that tells a browser to load content
|
||||||
letting users include images from other sites!</p>
|
from another website automatically.</p>
|
||||||
|
|
||||||
<p>Luckily for us, however, whitelisting saves the day. Sure, letting users
|
<p>Luckily for us, however, whitelisting saves the day. Sure, letting users
|
||||||
include any old random flash file could be dangerous, but if it's
|
include any old random flash file could be dangerous, but if it's
|
||||||
@ -147,13 +147,18 @@ 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
|
the amount of digits allowed in the regex or using a callback to check the
|
||||||
number.</p>
|
number.</p>
|
||||||
|
|
||||||
<h3>Trusts YouTube's security</h3>
|
<h3>Trusts media's host's security</h3>
|
||||||
|
|
||||||
<p>By allowing this code onto our website, we are trusting that YouTube has
|
<p>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
|
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
|
code into the Flash files. An exploit on YouTube means an exploit on your
|
||||||
site, and when you start allowing shadier sites, remember that trust
|
site. Even though YouTube is run by the reputable Google, it
|
||||||
is important.</p>
|
<a href="http://ha.ckers.org/blog/20061213/google-xss-vuln/">doesn't</a>
|
||||||
|
mean they are
|
||||||
|
<a href="http://ha.ckers.org/blog/20061208/xss-in-googles-orkut/">invulnerable.</a>
|
||||||
|
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.</p>
|
||||||
|
|
||||||
<h3>Poorly written adaptations compromise security</h3>
|
<h3>Poorly written adaptations compromise security</h3>
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user