Jump to content

Extension:Secure HTML: Difference between revisions

From mediawiki.org
Content deleted Content added
Installation: {{subst:ExtensionInstall|SecureHTML|registration=1|localsettings= $wgSecureHTMLSecrets = array( 'keyname' => 'keysecret', ); |custom-steps= * Modify $wgSecureHTMLSecrets as per below. * Go to ''Special:SecureHTML'' and use the page to create a hashed snippet of raw HTML using the key secrets defined. * Add the hashed snippet to your desired wiki page. }}
m Undid edits by ~2025-35609-0 (talk) to last version by NDG: unexplained content removal
 
(12 intermediate revisions by 8 users not shown)
Line 20: Line 20:
|example = [[finnix:Support_Finnix|{{tag|shtml|open}} tag (PayPal forms)]], [[finnix:Special:SecureHTML|Special:SecureHTML]]
|example = [[finnix:Support_Finnix|{{tag|shtml|open}} tag (PayPal forms)]], [[finnix:Special:SecureHTML|Special:SecureHTML]]
}}
}}
The '''Secure HTML''' extension lets you include arbitrary HTML in an authorized and secure way


== Rationale ==
Occasionally you need to display [[w:HTML|HTML]] within a wiki, but allowing it site-wide opens you up to various [[w:cross-site scripting|XSS]] attacks. This extension solves that problem by letting you specify arbitrary HTML, but only if the HTML includes a corresponding hash that is created by signing the HTML input with a secret that only authorized people know.
Occasionally, you need to display [[w:HTML|HTML]] within a wiki, but allowing it site-wide opens you up to various [[w:cross-site scripting|XSS]] attacks. This extension solves that problem by letting you specify arbitrary HTML, but only if the HTML includes a corresponding hash created by signing the HTML input with a secret only authorized people know.


The extension uses a special page, ''Special:SecureHTML'' which helps you build a tag, {{tag|shtml|open}}, which acts as a wrapper around raw HTML.
The extension uses a special page, ''Special:SecureHTML'' which helps you build a tag, {{tag|shtml|open}}, which acts as a wrapper around raw HTML.
Line 32: Line 34:
</syntaxhighlight>
</syntaxhighlight>


If the user uses a valid shared secret to build the hashed {{tag|shtml|open}} snippet and includes it in a wiki page, the snippet is rendered as the raw HTML contained within the tag. If the shared secret is invalid, the snippet is rendered as an error message (but not containing the HTML, obviously).
If the user uses a valid shared secret to build the hashed {{tag|shtml|open}} snippet and includes it in a wiki page, the snippet is rendered as the raw HTML contained within the tag. If the shared secret is invalid, the snippet is rendered as an error message (but does not contain the HTML).


== Installation ==
== Installation ==
Secure HTML is compatible with MediaWiki 1.23 and later.
Secure HTML is compatible with MediaWiki 1.23 and later.


{{ExtensionInstall|SecureHTML|registration=1|localsettings=
{{#if: |
$wgSecureHTMLSecrets = [
* If using {{ll|MediaWiki-Vagrant|Vagrant}}, install with <code>vagrant roles enable {{{vagrant}}} --provision</code>
; Manual installation
}}<!-- whitespace fix
-->{{trim| }}
* {{#if:
| and place the file(s) in a directory called <code>{{trim| {{#if:SecureHTML|SecureHTML|{{ROOTPAGENAME}}}} }}</code> in your <code>extensions/</code> folder.
|{{#if:SecureHTML{{#invoke:Extension|isOnGerrit}}
|[[Special:ExtensionDistributor/{{trim| {{#if:SecureHTML|SecureHTML|{{ROOTPAGENAME}}}} }}|Download]] and place the file(s) in a directory called <code>{{trim| {{#if:SecureHTML|SecureHTML|{{ROOTPAGENAME}}}} }}</code> in your <code>extensions/</code> folder.
|Download and place the file(s) in a directory called <code>{{trim| {{#if:SecureHTML|SecureHTML|{{ROOTPAGENAME}}}} }}</code> in your <code>extensions/</code> folder.
}}
}}<!-- whitespace fix
-->{{#if: |
* Only when installing from git run [[Special:MyLanguage/Composer|Composer]] to install PHP dependencies, by issuing <code>composer install --no-dev</code> in the extension directory. <small>(See {{task|T173141}} for potential complications.)</small>{{#ifeq: {{NAMESPACENUMBER}} |102 |{{#ifeq: {{SUBPAGENAME}} |en | |[[Category:Extensions requiring Composer with git{{#translation:}}]] }} }}
}}
* Add the following code at the bottom of your {{manual|LocalSettings.php}}: {{#tag:syntaxhighlight|

{{#if: | | {{#if: 1 | {{#if: | |wfLoadExtension( '{{trim| {{#if:SecureHTML|SecureHTML|{{ROOTPAGENAME}}}} }}' );}} | {{#if: | | require_once "$IP/extensions/{{trim| {{#if:SecureHTML|SecureHTML|{{ROOTPAGENAME}}}} }}/{{trim| {{#if:SecureHTML|SecureHTML|{{ROOTPAGENAME}}}} }}.php";}}}} }}
$wgSecureHTMLSecrets = array(
'keyname' => 'keysecret',
'keyname' => 'keysecret',
);
];
|custom-steps=
|lang="php"
* Modify $wgSecureHTMLSecrets as per below.
}}<!-- whitespace fix
-->{{#if: |
* Run the '''[[Special:MyLanguage/Manual:Update.php|update script]]''' which will automatically create the necessary database tables that this extension needs.}}<!-- whitespace fix
-->{{trim| * Modify $wgSecureHTMLSecrets as per below.
* Go to ''Special:SecureHTML'' and use the page to create a hashed snippet of raw HTML using the key secrets defined.
* Go to ''Special:SecureHTML'' and use the page to create a hashed snippet of raw HTML using the key secrets defined.
* Add the hashed snippet to your desired wiki page. }}
* Add the hashed snippet to your desired wiki page.
}}
* {{Done|uselang={{pagelang}}}} – Navigate to [[Special:Version]] on your wiki to verify that the extension is successfully installed.<!-- whitespace fix
-->{{#if: 1|{{#ifeq:1|required||<nowiki/>

To users running MediaWiki 1.24 or earlier:

The instructions above describe the new way of installing this extension using <code>wfLoadExtension()</code>.
If you need to install this extension on these earlier versions (MediaWiki 1.24 and earlier), instead of {{#tag:syntaxhighlight|wfLoadExtension( '{{trim| {{#if:SecureHTML|SecureHTML|{{ROOTPAGENAME}}}} }}' );|lang=php|inline=true}}, you need to use:

{{#tag:syntaxhighlight|
require_once "$IP/extensions/{{trim| {{#if:SecureHTML|SecureHTML|{{ROOTPAGENAME}}}} }}/{{trim| {{#if:SecureHTML|SecureHTML|{{ROOTPAGENAME}}}} }}.php";
|lang="php"
}}}}}}
=== Download from Git ===
{{WikimediaGitCheckout|SecureHTML}}


== Configuration ==
== Configuration ==


Secure HTML uses HMAC digests to sign a piece of raw HTML in a {{tag|shtml|open}} tag, using a shared secret key. The $wgSecureHTMLSecrets configuration array may have multiple shared secrets, and is in the format:
Secure HTML uses HMAC digests to sign a piece of raw HTML in a {{tag|shtml|open}} tag, using a shared secret key. The $wgSecureHTMLSecrets configuration array may have multiple shared secrets and is in the format:


<syntaxhighlight lang="php">
<syntaxhighlight lang="php">
$wgSecureHTMLSecrets = array(
$wgSecureHTMLSecrets = [
'Wiki admin' => 'zX6Zn2WRKlQt',
'Wiki admin' => 'zX6Zn2WRKlQt',
'developers' => '7RCkFRjw68CL',
'developers' => '7RCkFRjw68CL',
'Support department' => 'NL9g5QntWNbC',
'Support department' => 'NL9g5QntWNbC',
);
];
</syntaxhighlight>
</syntaxhighlight>


Line 111: Line 80:
</syntaxhighlight>
</syntaxhighlight>


== Special:SecureHTML ==
== Usage ==


The special page ''Special:SecureHTML'' is used to build the snippet, specifying the raw HTML, the key secret, and (optionally) the key name. If a key name is not specified, the first entry in $wgSecureHTMLSecrets is assumed. When the form is submitted, the signed snipped is displayed, and an attempt to render the snippet is made. If the key secret is incorrect, this will show you the results immediately, before you try to add the snippet to a page.
The special page ''Special:SecureHTML'' is used to build the snippet, specifying the raw HTML, the key secret, and (optionally) the key name. If a key name is not specified, the first entry in $wgSecureHTMLSecrets is assumed. When the form is submitted, the signed snip is displayed, and an attempt to render the snippet is made. If the key secret is incorrect, you will see the results immediately before adding the snippet to a page.


Special:SecureHTML is restricted to users who have the 'edit' right; the rationale being the user needs to be able to edit pages anyway to make use of this extension. If you would like to change this right, set $wgSecureHTMLSpecialRight to another right, or set to <nowiki>''</nowiki> to allow anyone to use the special page.
Special:SecureHTML is restricted to users with the 'edit' right; the rationale is that the user needs to be able to edit pages anyway to use this extension. If you want to change this right, set $wgSecureHTMLSpecialRight to another right or set it to <nowiki>''</nowiki> to allow anyone to use the special page.


Note that this restriction does not provide much extra security. If your MediaWiki installation requires users to be logged in to edit, it does provide superficial protection against anonymous dictionary attacks (checking the preview result) against a key. However, if a user already knows a key secret, they can build the signed snippet manually; the special page is not strictly needed.
Note that this restriction does not provide much extra security. If your MediaWiki installation requires users to be logged in to edit, it does provide superficial protection against anonymous dictionary attacks (checking the preview result) against a key. However, if users already know a key secret, they can build the signed snippet manually; the special page is not strictly needed.


By default, Special:SecureHTML presents a dropdown list of configured key names to select from. If you would rather not show all key names, set the following to turn the field into a freeform text input:
By default, Special:SecureHTML presents a dropdown list of configured key names from which to select. If you would rather not show all key names, set the following to turn the field into a freeform text input:


<syntaxhighlight lang="php">
<syntaxhighlight lang="php">
Line 127: Line 96:
== Hash algorithms ==
== Hash algorithms ==


Beginning with version 3.0, HMAC hash algorithms are configurable per-key. The default is HMAC SHA256 when the key value is a string (the secret), but may be extended, for example:
Beginning with version 3.0, HMAC hash algorithms are configurable per key. The default is HMAC SHA256 when the key value is a string (the secret), but may be extended, for example:


<syntaxhighlight lang="php">
<syntaxhighlight lang="php">
$wgSecureHTMLSecrets = array(
$wgSecureHTMLSecrets = [
'default sha256' => 'vwJ2prl4B4bg',
'default sha256' => 'vwJ2prl4B4bg',
'custom sha512' => array(
'custom sha512' => [
'algorithm' => 'sha512',
'algorithm' => 'sha512',
'secret' => 'RZQ8R99C95Xn',
'secret' => 'RZQ8R99C95Xn',
),
],
'custom whirlpool' => array(
'custom whirlpool' => [
'algorithm' => 'whirlpool',
'algorithm' => 'whirlpool',
'secret' => 'FXtN2QHflVPf',
'secret' => 'FXtN2QHflVPf',
),
],
);
];
</syntaxhighlight>
</syntaxhighlight>


SHA256 should be secure for most purposes, but if you do pick a custom algorithm, be careful with which one you choose. For example, adler32 would be a very bad choice for hashing.
SHA256 should be secure for most purposes, but if you pick a custom algorithm, be careful which one you choose. For example, adler32 would be a very bad choice for hashing.

Version 1.0 used a simple data + secret MD5 hash which is now considered cryptographically insecure. This format was deprecated in version 2.0 in favor of HMAC SHA256 hashes, and removed in 3.0. Any existing version 1.0 hashes must be converted to new hashes.

== Internationalization ==


Version 1.0 used a simple data + secret MD5 hash, which is now considered cryptographically insecure. This format was deprecated in version 2.0 in favor of HMAC SHA256 hashes and removed in 3.0. Any existing version 1.0 hashes must be converted to new hashes.
Translation of the extension strings is managed by [[Translatewiki.net]] ([http://translatewiki.net/w/i.php?title=Special%3ATranslate&taction=translate&group=ext-securehtml direct extension link]). Please contribute translations there.


==See also==
==See also==
* {{ll|HTML_restriction}} - list of extensions that allow for the inclusion of raw HTML
* {{ll|HTML_restriction}} - list of extensions that allow for the inclusion of raw HTML
* [[Extension:NamespaceHTML]] - Allows raw HTML in specified namespaces
* [[Extension:SaferHTMLTag]] - Allows only sysops and certain user groups to edit pages containing the {{tag|html|open}} tag
* [[Extension:SaferHTMLTag]] - Allows only sysops and certain user groups to edit pages containing the {{tag|html|open}} tag



Latest revision as of 15:48, 3 November 2025

MediaWiki extensions manual
Secure HTML
Release status: unmaintained
Implementation Tag , User rights
Description Lets you include arbitrary HTML in an authorized and secure way
Author(s) Ryan Finnie (Fo0bartalk)
Latest version 3.0 (2016-07-29)
MediaWiki 1.23+
$wgSecureHTMLSecrets, $wgSecureHTMLSpecialRight, $wgSecureHTMLSpecialDropdown, $wgSecureHTMLTag
‎<shtml> (configurable)
Licence GNU General Public License 2.0 or later
Download Download latest stable release (3.0), or:
Example ‎<shtml> tag (PayPal forms), Special:SecureHTML
Translate the Secure HTML extension if it is available at translatewiki.net

The Secure HTML extension lets you include arbitrary HTML in an authorized and secure way

Rationale

[edit | edit source]

Occasionally, you need to display HTML within a wiki, but allowing it site-wide opens you up to various XSS attacks. This extension solves that problem by letting you specify arbitrary HTML, but only if the HTML includes a corresponding hash created by signing the HTML input with a secret only authorized people know.

The extension uses a special page, Special:SecureHTML which helps you build a tag, ‎<shtml>, which acts as a wrapper around raw HTML.

Example

[edit | edit source]
<shtml
  hash="7fa503206cb1de131dd6acdca576e92262dd6d176cc3466073a343863743b8ed"
><strong>Hello world!</strong></shtml>

If the user uses a valid shared secret to build the hashed ‎<shtml> snippet and includes it in a wiki page, the snippet is rendered as the raw HTML contained within the tag. If the shared secret is invalid, the snippet is rendered as an error message (but does not contain the HTML).

Installation

[edit | edit source]

Secure HTML is compatible with MediaWiki 1.23 and later.


  • Download and move the extracted SecureHTML folder to your extensions/ directory.
    Developers and code contributors should install the extension from Git instead, using:
    cd extensions/
    git clone https://gerrit.wikimedia.org/r/mediawiki/extensions/SecureHTML
    
  • Add the following code at the bottom of your LocalSettings.php file:
    wfLoadExtension( 'SecureHTML' );
    $wgSecureHTMLSecrets = [
        'keyname' => 'keysecret',
    ];
    
  • Modify $wgSecureHTMLSecrets as per below.
  • Go to Special:SecureHTML and use the page to create a hashed snippet of raw HTML using the key secrets defined.
  • Add the hashed snippet to your desired wiki page.
  • Yes Done – Navigate to Special:Version on your wiki to verify that the extension is successfully installed.

Configuration

[edit | edit source]

Secure HTML uses HMAC digests to sign a piece of raw HTML in a ‎<shtml> tag, using a shared secret key. The $wgSecureHTMLSecrets configuration array may have multiple shared secrets and is in the format:

$wgSecureHTMLSecrets = [
    'Wiki admin' => 'zX6Zn2WRKlQt',
    'developers' => '7RCkFRjw68CL',
    'Support department' => 'NL9g5QntWNbC',
];

The first part of each pair is the key name, and the second part is the key secret. This way, you can logically segment shared secrets among several groups. If a code> parameter is not given to the ‎<shtml> tag, the first entry in $wgSecureHTMLSecrets is assumed. So, for example:

<!-- Use the default key ("Wiki admin" in the above example), signed with "zX6Zn2WRKlQt" -->
<shtml hash="ab...cd">HTML</shtml>

<!-- Or specify the key name explicitly -->
<shtml keyname="Wiki admin" hash="ab...cd">HTML</shtml>

<!-- Use the "developers" key, signed with "7RCkFRjw68CL" -->
<shtml keyname="developers" hash="ef...01">HTML</shtml>

The default tag name is shtml, but may be changed by setting e.g.:

$wgSecureHTMLTag = 'securehtml';

Usage

[edit | edit source]

The special page Special:SecureHTML is used to build the snippet, specifying the raw HTML, the key secret, and (optionally) the key name. If a key name is not specified, the first entry in $wgSecureHTMLSecrets is assumed. When the form is submitted, the signed snip is displayed, and an attempt to render the snippet is made. If the key secret is incorrect, you will see the results immediately before adding the snippet to a page.

Special:SecureHTML is restricted to users with the 'edit' right; the rationale is that the user needs to be able to edit pages anyway to use this extension. If you want to change this right, set $wgSecureHTMLSpecialRight to another right or set it to '' to allow anyone to use the special page.

Note that this restriction does not provide much extra security. If your MediaWiki installation requires users to be logged in to edit, it does provide superficial protection against anonymous dictionary attacks (checking the preview result) against a key. However, if users already know a key secret, they can build the signed snippet manually; the special page is not strictly needed.

By default, Special:SecureHTML presents a dropdown list of configured key names from which to select. If you would rather not show all key names, set the following to turn the field into a freeform text input:

$wgSecureHTMLSpecialDropdown = False;

Hash algorithms

[edit | edit source]

Beginning with version 3.0, HMAC hash algorithms are configurable per key. The default is HMAC SHA256 when the key value is a string (the secret), but may be extended, for example:

$wgSecureHTMLSecrets = [
    'default sha256' => 'vwJ2prl4B4bg',
    'custom sha512' => [
        'algorithm' => 'sha512',
        'secret' => 'RZQ8R99C95Xn',
    ],
    'custom whirlpool' => [
        'algorithm' => 'whirlpool',
        'secret' => 'FXtN2QHflVPf',
    ],
];

SHA256 should be secure for most purposes, but if you pick a custom algorithm, be careful which one you choose. For example, adler32 would be a very bad choice for hashing.

Version 1.0 used a simple data + secret MD5 hash, which is now considered cryptographically insecure. This format was deprecated in version 2.0 in favor of HMAC SHA256 hashes and removed in 3.0. Any existing version 1.0 hashes must be converted to new hashes.

See also

[edit | edit source]