Daniel Ziegenberg
be7f6d4834
Prior to this change, all the line endings in the imported HTMLPurifier library were using CRLF (\r\n aka Windows style), but the HTMLPurifier source and also the downloadable artefacts use LF (\n aka Linux style) as line endings. This has been the case since510d190382when with the commit "MDL-38672 import HTML Purifier 4.5.0" all line endings were changed from LF to CRLF. There was no comment in the commit on why this change was done. As the original source uses LF, this commit partly reverts510d190382and goes back to LF as line endings. Signed-off-by: Daniel Ziegenberg <daniel@ziegenberg.at>
31 lines
978 B
Plaintext
31 lines
978 B
Plaintext
URI.MungeSecretKey
|
|
TYPE: string/null
|
|
VERSION: 3.1.1
|
|
DEFAULT: NULL
|
|
--DESCRIPTION--
|
|
<p>
|
|
This directive enables secure checksum generation along with %URI.Munge.
|
|
It should be set to a secure key that is not shared with anyone else.
|
|
The checksum can be placed in the URI using %t. Use of this checksum
|
|
affords an additional level of protection by allowing a redirector
|
|
to check if a URI has passed through HTML Purifier with this line:
|
|
</p>
|
|
|
|
<pre>$checksum === hash_hmac("sha256", $url, $secret_key)</pre>
|
|
|
|
<p>
|
|
If the output is TRUE, the redirector script should accept the URI.
|
|
</p>
|
|
|
|
<p>
|
|
Please note that it would still be possible for an attacker to procure
|
|
secure hashes en-mass by abusing your website's Preview feature or the
|
|
like, but this service affords an additional level of protection
|
|
that should be combined with website blacklisting.
|
|
</p>
|
|
|
|
<p>
|
|
Remember this has no effect if %URI.Munge is not on.
|
|
</p>
|
|
--# vim: et sw=4 sts=4
|