#Mediawiki create new page how to
#Mediawiki create new page update
#Mediawiki create new page password

Manual:Resetting passwords - reseting a MediaWiki user's password.Category:Authentication and login - authorization extensions available.Manual:$wgAuthManagerConfig - configuration variable used by plug-in architecture.AuthManager - describes plug-in architecture for determining user identity.

Make sure to always disallow access for non authorized persons and the public as explained, delete remains of such logfiles when they are not needed, and comment or clear the logfile lines in your LocalSettings.php. If you use such an editor, be sure to disable backup generation or move sensitive data outside the web root.Ī MediaWiki debug logfile as it is used for debugging also contains sensitive data. Similarly, editing LocalSettings.php with some text editors will leave a backup file in the same directory with an altered file extension, causing the copy to be served as plain text if someone requests, for example, LocalSettings.php~. This can help to ensure that your database password will not be compromised if a web server configuration error disables PHP execution and reveals the file's source text.

#Mediawiki create new page update

The database user only needs to have SELECT, INSERT, UPDATE and DELETE permissions for the database.Ĭonsider moving the database password or other potentially sensitive data from LocalSettings.php to another file located outside of the web document root, and including that file from LocalSettings.php (through include()). You might consider manually narrowing this or establishing the user account yourself with custom permissions from just the places you need. If you create a new MySQL/MariaDB user for MediaWiki through MediaWiki's installer, somewhat liberal access is granted to it to ensure that it will work from a second server as well as a local one. This can help prevent accidentally opening access to your server due to some unknown flaw in the database server, a mistakenly set overly broad GRANT, or a leaked password. If it will be used over a network with a limited number of client machines, consider setting the IP firewall rules to accept access to TCP port 3306 (MySQL/MariaDB's port) only from those machines or only from your local subnet, and reject all accesses from the larger internet. If it will only be used from the single machine it's running on, consider disabling networking support, or enabling local networking access only (via the loopback device, see below), so the server can only communicate with local clients over Unix domain sockets. In general, you should keep access to your MySQL or MariaDB database to a minimum. General MySQL and MariaDB recommendations Like all MediaWiki files, the php user should not be able to write to LocalSettings.php. Your LocalSettings.php file must be readable by the php user, however it should not be world readable, to prevent other processes from discovering your database password and other sensitive information. See the section below on upload security for more details. If you do accomplish this via a config file in the images directory itself, you should ensure the config file is not writable by the webserver.

#Mediawiki create new page how to

The details on how to do this varies with webserver, but on apache it can sometimes be accomplished by using php_flag engine off in a. However, it is important to disable php in the images directory.

The exception being the images directory, which must be in the web root. chown -R After doing that step you may need to re-enable write access to the images directory.ĭirectories that MediaWiki needs write access to (such as $wgCacheDirectory if that feature is enabled) should be located outside of the web root. On unix-like systems, you can do this by ensuring that the mediawiki directory/files are owned by someone other than your web server user (After doing that step, you may however need to change the owner of the image directory back to the php user, as uploaded files need to go there, so MediaWiki needs to be able to write there (e.g. On Debian-based systems this means the www-data user should not own the php files. Another very important thing you should do to secure your MediaWiki installation: Make sure the user running php does not have write access to any web-accessible file or directory that php is enabled to run on.