Manual:Image authorization

This article is for system administrators who wish to restrict access to images and files based on user and/or 1>Special:MyLanguage/Manual:$wgGroupPermissions|user group permissions.

Uploaded files are generally served directly by the web server, not through MediaWiki. While there is a minimal level of security through obscurity with path encryption (eg. /c/c4/...), the path can be calculated easily from the file name and does not provide true protection.

This is not a recommended configuration; MediaWiki is not designed to be a CMS, or to protect sensitive data. To the contrary, it was designed to be as open as possible. Thus it does not inherently support full featured, air-tight protection of private content. Any administrator wishing to use this functionality should carefully review Security issues with authorization extensions

Overview
By default, all uploaded images (and files) are accessible directly by the web server. If you wish to allow access only to authorized users within the MediaWiki framework, two conditions must be met:


 * 1) The actual directory must be protected from direct access and;
 * 2) MediaWiki Authorization must be invoked when an Image/File access occurs by executing a script when any url containing that directory is requested.

The fundamental implementation requires:


 * 1) The images directory () should be moved outside the web root on the file system or otherwise protected
 * 2) The upload path () should point to img_auth.php.

The mechanisms for both are dependent on the web server platform. This article gives detailed instructions for two platforms:


 * 1) Apache (most versions)
 * 2) Microsoft Internet Information Server (IIS), version 6.0 and higher

For all instruction, assume that my MediaWiki is installed in "/path/to".

For example in:

http://wiki.yourwiki.org/MyWiki

"/path/to" is "/MyWiki"

How Does "img_auth.php" Work?
Image authorisation works by "intercepting" the URL and checking to see if the remainder (PATH_INFO) is in an area where the user has access based on the standard User ID and any Namespace, etc. protections you've assigned. When you've set up the upload path , to point to a directory that automatically redirects to include a script in the path, the script is executed and determines whether or not the file should be accessed.

What is really happening is this. If your pointer to the image/file is set up to, this is translated to    by MW and the server actually executes img_auth.php passing it   in the PATH_INFO server variable.

img_auth.php then checks to see if the user has access to that particular file and if so, streams it back. If not, it displays a standard 403 error.

Configuring File Uploads
Before attempting this configuration it is very important you understand Configuring file uploads. Please take a few moments to review and understand this article - it will save you a lot of time.

PHP PATH_INFO Support
This requires that your PHP setup support PATH_INFO (many CGI configurations do not) and you need to be in  mode or else, there wouldn't be a point ... unless you just like a more secure MW install; see below.

Another Scenario, Security Motivated (Apache/Unix ONLY)
Even if you don't want to restrict access to your images you might want to make use of the img_auth.php mechanism: to avoid publicly accessible directories, where the web server has write permissions. Though a web server writable directory is not insecure in itself, it is the first half of a successful attack to your web server. The second half then would be some exploitable (php) script, be it MW or, most likely, some other script. If the attacker can exploit the broken script to upload or generate another script intented to help him with further attacks/spamming etc, the attacker still needs a place to store that script in, writable by the web server ... and has it available and well known in the 'images' directory of MW standard installations.

A very first security measure against this will be to place a .htaccess file inside the 'images' directory with this content:

php_admin_flag engine off
 * 1) No php execution in the upload area

And that .htaccess must not be writable by the web server! It is a pity, that MW doesn't come with this by default (at least not in 1.6.10).

But even better will be to also move the web server writable 'images' directory outside of the document root, renaming it to something unguessable (e.g. the MD5 hash of &lt;whatever&gt;) and streaming the images via 'img_auth.php', so that the real directory name never ever shows up.

To accomplish that follow these steps:

cd &lt;/absolute/path/to/your/doc_root&gt;/.. mkdir &lt;dir_name_unguessable&gt; chgrp &lt;your_web_server_group&gt; &lt;dir_name_unguessable&gt; chmod 770 &lt;dir_name_unguessable&gt; cd &lt;dir_name_unguessable&gt; echo 'php_admin_flag engine off' &gt; .htaccess chmod 444 .htaccess  = "/img_auth.php"; = '&lt;/absolute/path/to/your/doc_root&gt;/../&lt;dir_name_unguessable&gt;'; = true; = false; = false;</tt> NOTE: The following img_auth.php hacks should not be needed.
 * 1) login in to a shell of your web server (similar actions are often possible with your FTP client, if not, ask your provider to assist you)
 * 2) create the unguessable images/upload directory outside of (in parallel to) your document root (note the /..</tt> at the end of the path):
 * 1) make it read/writeable for the web server:
 * 1) create the .htaccess file as noted above and make it readable only (this is paranoia, because the web server never looks here, only PHP not taking care of .ht* files normally, but just in case this directory ever will be made available to the web server directly) :
 * 1) change your LocalSettings.php config file:
 * 1) We don't wanna restrict access, just make our MW install more secure

(actually this doesn't work properly.. you need to hack your img_auth.php  and remove the check for logged in users and if the image is in the whitelist.. comment these lines:

if( !$wgUser->getId && ( !is_array( $wgWhitelistRead ) || !in_array( $title, $wgWhitelistRead ) ) ) { wfDebugLog( 'img_auth', "Not logged in and `{$title}` not in whitelist." ); wfForbidden; }

if anyone could make that a configuration option, it would be great!) Or you can change it to:

if( !$wgGroupPermissions['*']['read'] && !$wgUser->getId && ( !is_array( $wgWhitelistRead ) || !in_array( $title, $wgWhitelistRead ) ) ) { wfDebugLog( 'img_auth', "Not logged in and `{$title}` not in whitelist." ); wfForbidden; }

which should do the right thing without any additional configuration.

If you are using Mediawiki 1.15.1 (and want to use img_auth.php in a public wiki) you also need to comment the following lines

if ( in_array( 'read', $perms, true ) ) { wfDebugLog( 'img_auth', 'Public wiki' ); wfPublicError; }

That should do the job for web servers with PHP running as an Apache module. No further Apache config file changes are neccessary. You then will never see the path to your images, img_auth.php intercepts all read accesses. But all of your images are served, including thumbs.

If you use CGI or IIS your milage may vary.

Apache Instructions
Most administrators have found implementation in an Apache Environment straightforward and fairly simple.

If you are using a GoDaddy shared hosting account, you may need to reference the following thread if you are having problems viewing uploaded images with img_auth.php: http://www.mwusers.com/forums/showthread.php?16235-image_auth.php-wgUploadPath-GoDaddy&p=53612&viewfull=1#post53612

Apache Step 1. Protect Images Directory from Internet Access
In your [/path/to]/images directory, create an .htaccess containing one line:

Deny from All

If you have not moved your directory, you do not have to change <tvar|UploadDirectory></>

Apache Step 2.1. Change <tvar|UploadPath></> in LocalSettings.php
$wgUploadPath = "[/path/to]/img_auth.php";

is the URL path, not the file system path, so if img_auth.php is in, the line would read:

$wgUploadPath = "/mediawiki/img_auth.php";

Be sure to add a leading slash  if   is actually in your root-directory. Images won't be displayed at all if you forget to do so:

$wgUploadPath = "/img_auth.php";

Apache Step 2.2. Create aliases to execute img_auth.php
Note: This step is only necessary if you wish to continue using URLs containing direct paths to your images. MediaWiki should never require this, if you have successfully completed the previous configuration changes.

Edit the httpd.conf file and add the two following aliases:

Alias [/path/to]/images/ [/path/to]/img_auth.php/ Alias [/path/to]/images [/path/to]/img_auth.php

The second [/path/to] on each line should be the absolute path on the file system, and it may be necessary to add a trailing frontslash to img_auth.php (i.e., use [/path/to]/img_auth.php/).

Apache Step 1. Download the cgi-supporting image authorization script
When PATH_INFO is not available download the CGI-supporting image authorization script. Save script under the name cgi_img_auth.php in your mediawiki directory.

Apache Step 2. Protect Images Directory from Internet Access
In your [/path/to]/images directory, create an .htaccess containing one line:

Deny from All

If you have not moved your directory, you do not have to change <tvar|UploadDirectory></>

Apache Step 3.1. Change <tvar|UploadPath></> in LocalSettings.php
$wgUploadPath = "[/path/to]/cgi_img_auth.php";

Apache Step 3.2. Edit .htaccess
Edit the .htaccess to look like this

RewriteEngine on RewriteRule ^/path/to/images(.*)$ /path/to/cgi_img_auth.php/$1 [R] RewriteRule ^path/to/cgi_img_auth.php/(.*)$ path/to/cgi_img_auth.php?path=/$1

Note, however, this step is unnecessary on some installations.

Apache - Compatibilize with clean URLs
If your website is rewriting URLs through .htaccess, then you will need an exception before the custom rewrites:

RewriteCond %{REQUEST_URI} /img_auth\.php/ RewriteRule ^ - [L]

(This means: in case of img_auth called, stop rules)

Example of .htaccess:

RewriteEngine On RewriteCond %{REQUEST_URI} /img_auth\.php/ RewriteRule ^ - [L] RewriteCond ... RewriteRule ...
 * 1) First condition&rule:
 * 1) Rest of rules:

Apache - Deny the directory list
If you don't want user to list your images folder set this up on your apache configuration:

<Directory /var/www/wiki/images> Options -Indexes </Directory>

IIS Instructions
Implementation in IIS is more complex because it lacks the inherent 'pipe' capabilities of Apache or Unix in general. However using a few tricks, IIS can be made to execute the CGI and achieve protection.

WARNING: The img_auth approach ONLY works with the PHP ISAPI mode on the WIMP (Windows, IIS, MySQL, PHP) platform. If you followed the standard windows installation instructions, your wiki will be using CGI (php-cgi.exe) and you will have to convert to ISAPI. Instructions for doing so are in the discussion area. There is a bug in the php-cgi approach in parsing PATH_INFO that will show up as "CGI Error: The specified CGI application misbehaved by not returning a complete set of HTTP headers" on some files in the restricted path. This is a PHP/IIS issue, not a MediaWiki problem.

IIS Step 1. Protect Images Directory from Anonymous Internet Access
With IIS it is important that users cannot access images or files by using alternative URL paths to the bypass the virtual directory redirect. Therefore, a new directory outside the MediaWiki root must be created.

IIS Step 1.1 Create New Physical Directory
Create a new physical directory. This directory should not be inside any other existing web directories or virtual web directories:

Example:

c:\inetpub\wwwroot\MyWikiImg

IIS Step 1.2 Check/Set Directory Security
The Directory security must allow read, write, modify for the Internet Guest Account (usually IUSR_[server name]). Don't worry, you're going to regulate this in subsequent steps.

IIS Step 2. Execute Script img_auth.php for all Accesses to Image Directory
In IIS this is done by creating a virtual directory with the same name as the physical directory (if your directory is off the root web).

IIS Step 2.1 Create Virtual Directory with Same Name as Physical Directory
Create a new virtual directory using Start->Administrative Tools->Internet Information Services (IIS) Manager in the web service you are using for MediaWiki.

Right click on the web service->New Virtual Directory. ..

In the wizard, create a new virtual directory with the same name as the physical directory and point it to that directory.

IIS Step 2.2 Redirect New Virtual Directory to img_auth.php
Still in IIS Manager, right click on the new virtual directory->Properties select the 'Virtual Directory' tab and change the 'The content for this resource should come from:' to 'A redirection to a URL'. Fill in the 'Redirect To:' with the URL to img_auth in your MediaWiki.

Example:

http://wiki.yourwiki.org/MyWiki/img_auth.php

Remember to Click Apply!

IIS Step 3 Copy Old Image Directory to New
Copy the contents of the old images directory ($ip/image) and subdirectories into the new directory you created. Note: The 'image' directory will not exist in the new directory. The new directory should not appear as:

Wrong:

MyWikiImg images 0   1    . ..

Right:

MyWikiImg 0 1  . ..

IIS Step 4.1 Change <tvar|UploadPath></> in LocalSettings.php
$wgUploadPath = "[NewVirtualDirPath]";

Example:

$wgUploadPath = "/MyWikiImg";

IIS Step 4.2 Change <tvar|UploadDirectory></> in LocalSettings.php
$wgUploadDirectory = "[NewVirtualDirImages]";

Example:

$wgUploadDirectory = "D:\Inetpub\wwwroot\MyWikiImg";

IIS Step 4.4 Troubleshoot IIS PATH_INFO
If your installation is not working, it may be because img_auth.php requires the server to return PATH_INFO to know exactly which file you wish to access (eg., everything in the URL after the virtual directory).

There have been several articles and hints that some versions of IIS may disallow the server variables PATH_INFO and PATH_TRANSLATE 'for security reasons'. While we did not have this problem on the current server and patch level (IIS 6.0) it is a noted issue for IIS 4.0 (and possibly prior), you may want to investigate if img_auth.php is not working for you.

The full knowledgebase article may be found at Using PATH_INFO and PATH_TRANSLATED from CGI Applications. The article instructs you on how to run a program written in MS Visual Basic (you may need to load CScript).