LinuxSecurity.com
Share your story
The central voice for Linux and Open Source security news
Home News Topics Advisories HOWTOs Features Newsletters About Register

Welcome!
Sign up!
EnGarde Community
Login
Polls
What is the most important Linux security technology?
 
Advisories
Community
Linux Events
Linux User Groups
Link to Us
Security Center
Book Reviews
Security Dictionary
Security Tips
SELinux
White Papers
Featured Blogs
All About Linux
DanWalsh LiveJournal
Securitydistro
Latest Newsletters
Linux Security Week: March 16th, 2010
Linux Advisory Watch: March 14th, 2010
Subscribe
LinuxSecurity Newsletters
E-mail:
Choose Lists:
About our Newsletters
RSS Feeds
Get the LinuxSecurity news you want faster with RSS
Powered By

  
PHP 5.3.1 Released, Security Beefed Up Print E-mail
User Rating:      How can I rate this item?
Source: WDVL - Posted by Alex   
Security Projects The PHP development team recently introduced the latest version of the new PHP 5.3 branch, PHP 5.3.1. This version essentially does not change the essential core 5.3 PHP engine, but by focusing on stability and security, the PHP team has introduced more than 100 bug fixes and tweaks to the overall framework. Something that I find very encouraging is the PHP team's very conscious drive to empower the security features of PHP. There was a time not so long ago when PHP was considered rather unsafe for commercial purposes, but now I think that sentiment is changing and the world is becoming open to the power of PHP, as well as it's usefulness.

The most significant and security-conscious addition in PHP 5.3.1 is the inclusion of a max_file_uploads INI directive, making it possible to limit file uploads per request to 20 files by default. This is extremely important in circumventing denial of service (DoS) attacks.

If you have not heard of denial of service attacks, the basic principle is that a website gets pounded with hundreds or even thousands of requests at the same time, thus rendering the server essentially useless because all of its sources are being consumed in serving the attack. Thus, a user having unlimited upload possibilities certainly could bring a production server to its knees by constantly uploading something like one hundred files repeatedly from various machines. You could in effect have 1000 or more files being uploaded at the same time, and a slow or shared server will not handle that well at all. Even a dedicated server would struggle considerably. So, what max_file_uploads does is make sure that no more than 20 files can be uploaded at a time on that server.

Read this full article at WDVL

Only registered users can write comments.
Please login or register.

Powered by AkoComment!

 
< Prev   Next >
    
Partner:

 

Latest Features
Vulnerabilities in Web Applications
A Secure Nagios Server
HowTo: Secure your Ubuntu Apache Web Server
Creating Snort Rules with EnGarde
What You Need to Know About Linux Rootkits.
Introduction: Buffer Overflow Vulnerabilities
Network Security Audit (Part II)
Yesterday's Edition
Google patches 11 vulnerabilities in Chrome days before hacking contest
Revised draft of Cybersecurity Act introduced in Senate
Security updates for Drupal modules
Exploit code with DNS tunnel
What Are the Most Underrated Security Technologies?
Get to the root of security threats
Kernel vulnerabilities discovered in Ubuntu
Partner Sponsor

Community | HOWTOs | Blogs | Features | Book Reviews | Networking
 Security Projects |  Latest News |  Newsletters |  SELinux |  Privacy |  Home
 Hardening |   About Us |   Advertise |   Legal Notice |   RSS |   Guardian Digital
(c)Copyright 2010 Guardian Digital, Inc. All rights reserved.