Interview Questions

PHP interview questions
Web UI developer
Archives
PHP Framework

PHP Tutorial

PHP Introduction
PHP Variables
PHP Comments
PHP Operators

PHP Conditional Statements

PHP Loops
PHP functions
PHP Array

Articles

Cakephp Overview
CodeIgniter Overview
Yii Overview
Zend Overview
PHP Security
  1. PHP Security

    When proposing an Internet service, you should habitually hold security in brain as you evolve your cipher. It may appear that most PHP scripts aren't perceptive to security anxieties; this is mostly due to the large number of inexperienced programmers employed in the dialect. although, there is no reason for you to have an inconsistent security policy founded on a rough guess at your code's significance. The instant you put anything financially intriguing on your server, it becomes expected that somebody will try to casually hack it. conceive a forum program or any sort of buying cart, and the probability of attack increases to a dead certainty.

    Hacking types is trivial. Yes, by utilising a stupid JavaScript knack, you may be able to limit your form to permit only the figures 1 through 5 in a rating area. The instant someone turns JavaScript off in their browser or mails made-to-order form data, your client-side validation soars out the window.

    Users interact with your scripts mainly through form parameters, and thus they're the biggest security risk. What's the lesson? habitually validate the facts and figures that gets passed to any PHP script in the PHP script. In this article, we display you how to analyze and defend against cross-site scripting (XSS) attacks, which can hijack your user's credentials (and worse). You'll furthermore glimpse how to prevent the MySQL injection attacks that can stain or decimate your facts and figures.
    Don't trust users

    Assume that every piece of facts and figures your website accumulates is laden with harmful cipher. Sanitize every piece, even if you're positive that nobody would ever try to strike your location.
    Turn off global variables

    The large-scale security aperture you can have is having the register_globals configuration parameter enabled. Mercifully, it's turned off by default in PHP 4.2 and subsequent. If register_globals is on, then you can disable this feature by turning the register_globals variable to Off in your server's php.ini document :

    register_globals = Off

    Novice programmers outlook registered globals as a convenience, but they don't realize how unsafe this setting is. A server with international variables endowed automatically assigns international variables to any form parameters. For an idea of how this works and why this is unsafe, let's gaze at an demonstration.

    Let's say that you have a script entitled process.php that goes into form data into your user database. The initial form looked like this:

    <input name="username" type="text" size="15" maxlength="64">

    When running process.php, PHP with registered globals endowed places the worth of this parameter into the $username variable. This saves some typing over accessing them through $_POST['username'] or $_GET['username']. Unfortunately, this furthermore departs you open to security troubles, because PHP sets a variable for any value sent to the script by a GET or POST parameter, and that is a large-scale difficulty if you didn't specifically initialize the variable and you don't want somebody to manipulate it.

    Take the script below, for example—if the $authorized variable is true, it shows confidential facts and figures to the client. Under usual attenuating factors, the $authorized variable is set to factual only if the user has been properly authenticated by the hypothetical authenticated_user() function. But if you have register_globals hardworking, any person could drive a GET parameter such as authorized=1 to override this: