cvs: phpweb / release_4_1_0.php release_4_1_1.php release_4_1_2_win32.php release_4_2_0.php release_4_2_0_fr.php
| From: | Gabor Hojtsy | Date: | Thu, 14 Aug 2003 12:21:39 +0000 |
| Subject: | cvs: phpweb / release_4_1_0.php release_4_1_1.php release_4_1_2_win32.php release_4_2_0.php release_4_2_0_fr.php | ||
| Groups: | php.mirrors | ||
| Request: | Send a blank email to php-mirrors+get-20274@lists.php.net to get a copy of this message | ||
goba Thu Aug 14 08:21:39 2003 EDT
Modified files:
/phpweb release_4_1_0.php release_4_1_1.php release_4_1_2_win32.php
release_4_2_0_fr.php release_4_2_0.php
Log:
Release annoucement fixes:
- make these pages really stand on their own, not look
like as if they were copied from the homepage...
- use new headers and footers
- use correct identation and adhere to standards
Index: phpweb/release_4_1_0.php diff -u phpweb/release_4_1_0.php:1.11 phpweb/release_4_1_0.php:1.12 --- phpweb/release_4_1_0.php:1.11 Fri Apr 26 17:33:53 2002 +++ phpweb/release_4_1_0.php Thu Aug 14 08:21:39 2003 @@ -1,92 +1,107 @@ <?php -/* if you're reading this, it isn't because you've found a security hole. - this is an open source website. read and learn! */ - -header("Cache-Control: public, max-age=600"); - -require_once 'prepend.inc'; - -commonHeader("Hypertext Preprocessor"); -echo "\n<!--$MYSITE-->\n"; +// $Id: release_4_1_0.php,v 1.12 2003/08/14 12:21:39 goba Exp $ +$_SERVER['BASE_PAGE'] = 'release_4_1_0.php'; +include_once $_SERVER['DOCUMENT_ROOT'] . '/include/prepend.inc'; +site_header("PHP 4.1.0 Release Announcement"); ?> -<h1> -PHP 4.1.0 Release Announcement -</h1> +<h1>PHP 4.1.0 Release Announcement</h1> -<p>A <a href="release_4_1_0_fr.php">French translation</a> of this -announcement is also available.</p> +<p> + A <a href="release_4_1_0_fr.php">French translation</a> of this + announcement is also available. +</p> + +<p> + After a lengthy QA process, PHP 4.1.0 is <a href="/downloads.php">finally out</a>! +</p> -<p>After a lengthy QA process, PHP 4.1.0 is <a href="http://www.php.net/downloads.php">finally out</a>!</p> - -<p>PHP 4.1.0 includes several other key improvements:</p> +<p> PHP 4.1.0 includes several other key improvements:</p> <ul> <li>A new input interface for improved security (read below)</li> <li>Highly improved performance in general</li> - <li>Revolutionary performance and stability improvements under + <li> + Revolutionary performance and stability improvements under Windows. The multithreaded server modules under Windows (ISAPI, Apache, etc.) perform as much as 30 times faster under load! We want to thank Brett Brewer and his team in Microsoft for working - with us to improve PHP for Windows.</li> - <li>Versioning support for extensions. Right now it's barely being + with us to improve PHP for Windows. + </li> + <li> + Versioning support for extensions. Right now it's barely being used, but the infrastructure was put in place to support separate version numbers for different extensions. The negative side effect is that loading extensions that were built against old versions of PHP will now result in a crash, instead of in a nice clear message. - Make sure you only use extensions built with PHP 4.1.0.</li> + Make sure you only use extensions built with PHP 4.1.0. + </li> <li>Turn-key output compression support</li> - <li><b>LOTS</b> of fixes and new functions</li> + <li><strong>LOTS</strong> of fixes and new functions</li> </ul> -<p>As some of you may notice, this version is quite historic, as it's -the first time in history we actually incremented the middle digit! :) -The two key reasons for this unprecedented change were the new input -interface, and the broken binary compatibility of modules due to the -versioning support.</p> - -<p>Following is a description of the new input mechanism. For a full list of -changes in PHP 4.1.0, see the <a href="ChangeLog-4.php">changelog</a>.</p> +<p> + As some of you may notice, this version is quite historic, as it's + the first time in history we actually incremented the middle digit! :) + The two key reasons for this unprecedented change were the new input + interface, and the broken binary compatibility of modules due to the + versioning support. +</p> + +<p> + Following is a description of the new input mechanism. For a full list of + changes in PHP 4.1.0, see the <a href="ChangeLog-4.php">changelog</a>. +</p> <hr /> -<h2>SECURITY: NEW INPUT MECHANISM</h2> +<h2>SECURITY: NEW INPUT MECHANISM</h2> -<p>First and foremost, it's important to stress that regardless of -anything you may read in the following lines, PHP 4.1.0 <b>still supports</b> -the old input mechanisms from older versions. Old applications -should go on working fine without modification!</p> +<p> + First and foremost, it's important to stress that regardless of + anything you may read in the following lines, PHP 4.1.0 <strong>still + supports</strong> the old input mechanisms from older versions. + Old applications should go on working fine without modification! +</p> <p>Now that we have that behind us, let's move on :)</p> -<p>For various reasons, PHP setups which rely on register_globals -being on (i.e., on form, server and environment variables becoming -a part of the global namespace, automatically) are very often -exploitable to various degrees. For example, the piece of code:</p> +<p> + For various reasons, PHP setups which rely on register_globals + being on (i.e., on form, server and environment variables becoming + a part of the global namespace, automatically) are very often + exploitable to various degrees. For example, the piece of code: +</p> -<?php highlight_string('<?php +<?php highlight_php('<?php if (authenticate_user()) { $authenticated = true; } ... ?>');?> -<p>May be exploitable, as remote users can simply pass on 'authenticated' -as a form variable, and then even if authenticate_user() returns false, -$authenticated will actually be set to true. While this looks like a -simple example, in reality, quite a few PHP applications ended up being -exploitable by things related to this misfeature.</p> - -<p>While it is quite possible to write secure code in PHP, we felt that the -fact that PHP makes it too easy to write insecure code was bad, and we've -decided to attempt a far-reaching change, and deprecate register_globals. -Obviously, because the vast majority of the PHP code in the world relies -on the existence of this feature, we have no plans to actually remove it -from PHP anytime in the foreseeable future, but we've decided to encourage -people to shut it off whenever possible.</p> - -<p>To help users build PHP applications with register_globals being off, -we've added several new special variables that can be used instead of the -old global variables. There are 7 new special arrays:</p> +<p> + May be exploitable, as remote users can simply pass on 'authenticated' + as a form variable, and then even if authenticate_user() returns false, + $authenticated will actually be set to true. While this looks like a + simple example, in reality, quite a few PHP applications ended up being + exploitable by things related to this misfeature. +</p> + +<p> + While it is quite possible to write secure code in PHP, we felt that the + fact that PHP makes it too easy to write insecure code was bad, and we've + decided to attempt a far-reaching change, and deprecate register_globals. + Obviously, because the vast majority of the PHP code in the world relies + on the existence of this feature, we have no plans to actually remove it + from PHP anytime in the foreseeable future, but we've decided to encourage + people to shut it off whenever possible. +</p> + +<p> + To help users build PHP applications with register_globals being off, + we've added several new special variables that can be used instead of the + old global variables. There are 7 new special arrays: +</p> <ul> <li>$_GET - contains form variables sent through GET</li> @@ -94,51 +109,65 @@ <li>$_COOKIE - contains HTTP cookie variables</li> <li>$_SERVER - contains server variables (e.g., REMOTE_ADDR)</li> <li>$_ENV - contains the environment variables</li> - <li>$_REQUEST - a merge of the GET variables, POST variables and Cookie variables. - In other words - all the information that is coming from the user, - and that from a security point of view, cannot be trusted.</li> + <li> + $_REQUEST - a merge of the GET variables, POST variables and Cookie variables. + In other words - all the information that is coming from the user, + and that from a security point of view, cannot be trusted. + </li> <li>$_SESSION - contains HTTP variables registered by the session module</li> </ul> -<p>Now, other than the fact that these variables contain this special information, -they're also special in another way - they're automatically global in any -scope. This means that you can access them anywhere, without having to -'global' them first. For example:</p> +<p> + Now, other than the fact that these variables contain this special information, + they're also special in another way - they're automatically global in any + scope. This means that you can access them anywhere, without having to + 'global' them first. For example: +</p> -<?php highlight_string('<?php +<?php highlight_php('<?php function example1() { print $_GET["name"]; // works, \'global $_GET;\' is not necessary! } ?>');?> -<p>would work fine! We hope that this fact would ease the pain in migrating -old code to new code a bit, and we're confident it's going to make writing -new code easier. Another neat trick is that creating new entries in the -$_SESSION array will automatically register them as session variables, as -if you called session_register(). This trick is limited to the session -module only - for example, setting new entries in $_ENV will *not* perform -an implicit putenv().</p> - -<p>PHP 4.1.0 still defaults to have register_globals set to on. It's a -transitional version, and we encourage application authors, especially -public ones which are used by a wide audience, to change their applications -to work in an environment where register_globals is set to off. Of course, -they should take advantage of the new features supplied in PHP 4.1.0 that -make this transition much easier.</p> +<p> + would work fine! We hope that this fact would ease the pain in migrating + old code to new code a bit, and we're confident it's going to make writing + new code easier. Another neat trick is that creating new entries in the + $_SESSION array will automatically register them as session variables, as + if you called session_register(). This trick is limited to the session + module only - for example, setting new entries in $_ENV will *not* perform + an implicit putenv(). +</p> + +<p> + PHP 4.1.0 still defaults to have register_globals set to on. It's a + transitional version, and we encourage application authors, especially + public ones which are used by a wide audience, to change their applications + to work in an environment where register_globals is set to off. Of course, + they should take advantage of the new features supplied in PHP 4.1.0 that + make this transition much easier. +</p> -<p>As of the next semi-major version of PHP, new installations of PHP will -default to having register_globals set to off. No worries! Existing -installations, which already have a php.ini file that has register_globals -set to on, will not be affected. Only when you install PHP on a brand new -machine (typically, if you're a brand new user), will this affect you, and -then too - you can turn it on if you choose to.</p> - -<p>Note: Some of these arrays had old names, e.g. $HTTP_GET_VARS. These names -still work, but we encourage users to switch to the new shorter, and -auto-global versions.</p> - -<p>Thanks go to Shaun Clowes (shaun@securereality.com.au) for pointing out this -problem and for analyzing it.</p> +<p> + As of the next semi-major version of PHP, new installations of PHP will + default to having register_globals set to off. No worries! Existing + installations, which already have a php.ini file that has register_globals + set to on, will not be affected. Only when you install PHP on a brand new + machine (typically, if you're a brand new user), will this affect you, and + then too - you can turn it on if you choose to. +</p> + +<p> + Note: Some of these arrays had old names, e.g. $HTTP_GET_VARS. These names + still work, but we encourage users to switch to the new shorter, and + auto-global versions. +</p> + +<p> + Thanks go to Shaun Clowes (shaun@securereality.com.au) for pointing out this + problem and for analyzing it. +</p> -<?php commonFooter(); ?> +<?php site_footer(); ?> \ No newline at end of file Index: phpweb/release_4_1_1.php diff -u phpweb/release_4_1_1.php:1.4 phpweb/release_4_1_1.php:1.5 --- phpweb/release_4_1_1.php:1.4 Sun Feb 3 16:42:12 2002 +++ phpweb/release_4_1_1.php Thu Aug 14 08:21:39 2003 @@ -1,44 +1,64 @@ <?php -require_once 'prepend.inc'; - -commonHeader("PHP 4.1.1 Release Announcement"); +// $Id: release_4_1_1.php,v 1.5 2003/08/14 12:21:39 goba Exp $ +$_SERVER['BASE_PAGE'] = 'release_4_1_1.php'; +include_once $_SERVER['DOCUMENT_ROOT'] . '/include/prepend.inc'; +site_header("PHP 4.1.1 Release Announcement"); ?> -<h1> -PHP 4.1.1 Release Announcement -</h1> +<h1>PHP 4.1.1 Release Announcement</h1> + +<p> + Due to a few bugs in PHP 4.1.0, we decided to release PHP 4.1.1. The bugs + that were fixed are not major ones but minor ones, which could be annoying + if you get bitten by them. +</p> -<p>Due to a few bugs in PHP 4.1.0, we decided to release PHP 4.1.1. The bugs -that were fixed are not major ones but minor ones, which could be annoying -if you get bitten by them.</p> +<p> + Our recommendation is that people who already upgraded to PHP 4.1.0 do + <strong>not</strong> upgrade to <a href="/downloads.php">PHP 4.1.1</a>, + unless they're experiencing one of the described bugs. +</p> -<p>Our recommendation is that people who already upgraded to PHP 4.1.0 do -<b>not</b> upgrade to <a href="http://www.php.net/downloads.php">PHP 4.1.1</a>, -unless they're experiencing one of the described bugs.</p> +<p> + <strong>No</strong> new features or security updates are available + in this release. +</p> -<p><b>No</b> new features or security updates are available in this release.</p> +<p>Full list of fixes:</p> -<p>Full list of fixes: <ul> -<li>Fixed incompatibility with Windows .NET / IIS 6 - may improve stability - under other versions of IIS. (Zeev)</li> -<li>Fixed bug that caused crashes or error notices on shutdown on threaded - platforms. (Zeev)</li> -<li> Fixed several crash bugs in the xslt extension. (Markus, Derick)</li> -<li>Fixed problem with dbase not returning very large (larger than long) - integers properly. (Vlad)</li> -<li>Fixed several bugs and memleaks in the domxml extension. (Markus)</li> -<li>Fixed bug in gmmktime() which was one hour off during standard time - - bug #9878. Patch by bfoddy@mediaone.net. (jmoore)</li> -<li>Fixed bug in gmdate() timezone handling on Windows - bug #13885. (jmoore)</li> -<li>Fixed several crash bugs in the mcrypt extension. (Derick)</li> -<li>Made the mcrypt extension compile with the libmcrypt 2.2 series again. - (Sterling)</li> -<li>Fixed a bug where the is_file() family of functions would in-correctly give - an error when they were given filenames that didn't exist. (Sterling)</li> -<li>Fixed a bug in the strtotime() function where it was incorrectly recognizing - GMT +0100 and GMT -0100. (Derick)</li> + <li> + Fixed incompatibility with Windows .NET / IIS 6 - may improve stability + under other versions of IIS. (Zeev) + </li> + <li> + Fixed bug that caused crashes or error notices on shutdown on threaded + platforms. (Zeev) + </li> + <li>Fixed several crash bugs in the xslt extension. (Markus, Derick)</li> + <li> + Fixed problem with dbase not returning very large (larger than long) + integers properly. (Vlad) + </li> + <li>Fixed several bugs and memleaks in the domxml extension. (Markus)</li> + <li> + Fixed bug in gmmktime() which was one hour off during standard time - + bug #9878. Patch by bfoddy@mediaone.net. (jmoore) + </li> + <li>Fixed bug in gmdate() timezone handling on Windows - bug #13885. (jmoore)</li> + <li>Fixed several crash bugs in the mcrypt extension. (Derick)</li> + <li> + Made the mcrypt extension compile with the libmcrypt 2.2 series again. + (Sterling) + </li> + <li> + Fixed a bug where the is_file() family of functions would in-correctly give + an error when they were given filenames that didn't exist. (Sterling) + </li> + <li> + Fixed a bug in the strtotime() function where it was incorrectly recognizing + GMT +0100 and GMT -0100. (Derick) + </li> </ul> -</p> -<?php commonFooter(); ?> +<?php site_footer(); ?> Index: phpweb/release_4_1_2_win32.php diff -u phpweb/release_4_1_2_win32.php:1.1 phpweb/release_4_1_2_win32.php:1.2 --- phpweb/release_4_1_2_win32.php:1.1 Tue Mar 12 06:39:27 2002 +++ phpweb/release_4_1_2_win32.php Thu Aug 14 08:21:39 2003 @@ -1,49 +1,56 @@ <?php -require_once 'prepend.inc'; - -commonHeader("Hypertext Preprocessor"); +// $Id: release_4_1_2_win32.php,v 1.2 2003/08/14 12:21:39 goba Exp $ +$_SERVER['BASE_PAGE'] = 'release_4_1_2_win32.php'; +include_once $_SERVER['DOCUMENT_ROOT'] . '/include/prepend.inc'; +site_header("PHP 4.1.2 Windows (Win32) Release Announcement"); ?> -<h1> -PHP 4.1.2 Windows (Win32) Release Announcement -</h1> +<h1>PHP 4.1.2 Windows (Win32) Release Announcement</h1> <p> -Due to an issue with the Windows binary allowing any user to read or execute the contents of a -file directly from the PHP binary, we have delayed the 4.1.2 release of PHP for Windows to allow -for this fix. This release also fixes the file upload security problem.</p> - -<p>With this new release, we introduce 2 new php.ini settings, which MUST be set to make the binary -work. It's worth noting, at this point, that this particular fix only applies to the CGI binary. The -SAPI module will still work as expected, and it's use is encouraged.</p> + Due to an issue with the Windows binary allowing any user to read or + execute the contents of a file directly from the PHP binary, we have + delayed the 4.1.2 release of PHP for Windows to allow for this fix. + This release also fixes the file upload security problem. +</p> <p> -The new settings are: - <ul> - <li>cgi.force_redirect 0|1</li> - <li>cgi.redirect_status_env ENV_VAR_NAME</li> - </ul> + With this new release, we introduce 2 new php.ini settings, which + <strong>MUST</strong> be set to make the binary work. It's worth + noting, at this point, that this particular fix only applies to + the CGI binary. The SAPI module will still work as expected, + and it's use is encouraged. </p> +<p>The new settings are:</p> +<ul> + <li><tt>cgi.force_redirect 0|1</tt></li> + <li><tt>cgi.redirect_status_env ENV_VAR_NAME</tt></li> +</ul> + <h2>WebServers affected by this vulnerability</h2> <p> -It is known that Apache (any version) and iPlanet servers are vulnerable to this issue, however -Microsoft IIS is not. Since cgi.force_redirect takes a value of either 1 or 0, (on or off) you -should set it to 1 if you are running Apache or iPlanet servers, and to 0 for IIS. If you are -unsure of which you need, set it to 1 and see if your scripts execute. You will need to stop and -restart your server when you change your php.ini file, for the changes to have effect. + It is known that Apache (any version) and iPlanet servers are + vulnerable to this issue, however Microsoft IIS is not. Since + cgi.force_redirect takes a value of either 1 or 0, (on or off) + you should set it to 1 if you are running Apache or iPlanet + servers, and to 0 for IIS. If you are unsure of which you need, + set it to 1 and see if your scripts execute. You will need to + stop and restart your server when you change your php.ini file, + for the changes to have effect. </p> <p> -if cgi.force_redirect is turned on, and you are not running under Apache or Netscape -(iPlanet) web servers, you MAY need to set an environment variable name that PHP -will look for to know it is OK to continue execution. Setting this variable MAY -cause security issues, so check what you are doing first. + If cgi.force_redirect is turned on, and you are not running under + Apache or Netscape (iPlanet) web servers, you MAY need to set an + environment variable name that PHP will look for to know it is OK + to continue execution. Setting this variable MAY cause security + issues, so check what you are doing first. </p> <p> -More information can be found <a href="http://security.e-matters.de/advisories/012002.html">here</a> -relating to the form upload exploit that caused the release of 4.1.2 initially. + More information can be found <a href="http://security.e-matters.de/advisories/012002.html">here</a> + relating to the form upload exploit that caused the release of 4.1.2 initially. </p> -<?php commonFooter(); ?> \ No newline at end of file +<?php site_footer(); ?> Index: phpweb/release_4_2_0_fr.php diff -u phpweb/release_4_2_0_fr.php:1.5 phpweb/release_4_2_0_fr.php:1.6 --- phpweb/release_4_2_0_fr.php:1.5 Sun Mar 2 11:56:37 2003 +++ phpweb/release_4_2_0_fr.php Thu Aug 14 08:21:39 2003 @@ -1,77 +1,91 @@ <?php -header("Cache-Control: public, max-age=600"); -require_once 'prepend.inc'; -header("Content-language: fr"); -commonHeader("Hypertext Preprocessor"); -echo "\n<!--$MYSITE-->\n"; +// $Id: release_4_2_0_fr.php,v 1.6 2003/08/14 12:21:39 goba Exp $ +$_SERVER['BASE_PAGE'] = 'release_4_2_0_fr.php'; +include_once $_SERVER['DOCUMENT_ROOT'] . '/include/prepend.inc'; +site_header("Annonce de publication de PHP 4.2.0"); ?> -<h1> -Annonce de PHP 4.2.0 -</h1> +<h1>Annonce de publication de PHP 4.2.0</h1> -<p>Après avoir passé avec succès le processus qualité, PHP 4.2.0 est officiellement <a href="http://www.php.net/downloads.php">publié</a>!</p> +<p> + Après avoir passé avec succès le processus + qualité, PHP 4.2.0 est officiellement <a href="/downloads.php">publié</a>! +</p> <h2>Variables externes</h2> <p> -Le changement le plus important de PHP 4.2.0 concerne la gestion des - variables. Les <b>variables externes (issues de l'environnement d'exécution, -des requêtes HTTP, des cookies ou du serveur web) ne sont plus enregistrées -dans l'environnement d'exécution global par défaut.</b> La méthode recommandée -pour accéder aux variables externes est d'utiliser les nouveaux tableaux globaux, -introduits en PHP 4.1.0. Pour plus d'informations sur ces modifications : + Le changement le plus important de PHP 4.2.0 concerne la gestion des + variables. Les <strong>variables externes (issues de l'environnement d'exécution, + des requêtes HTTP, des cookies ou du serveur web) ne sont plus enregistrées + dans l'environnement d'exécution global par défaut.</strong> + La méthode recommandée pour accéder aux variables + externes est d'utiliser les nouveaux tableaux globaux, introduits en + PHP 4.1.0. Pour plus d'informations sur ces modifications: +</p> <ul> <li><a href="http://www.php.net/manual/en/language.variables.predefined.php">PHP Manual : Predefined variables</a></li> <li><a href="http://www.php.net/release_4_1_0.php">Annonce de PHP 4.1.0</a></li> <li><a href="http://www.zend.com/zend/art/art-oertli.php">Article de Thomas Oertli sur la programmation sécurisée en PHP</a></li> <li><a href="http://www.phpinfo.net/?p=articles&rub=globals">Article de Jean Pierre Dézelus sur les variables globales</a></li> </ul> -</p> <h2>Compatibilité</h2> <p> -L'ASF (Apache Software Foundation) a récemment publié sa première -version publique d'Apache 2. PHP 4.2.0 dispose du support - <b>EXPERIMENTAL</b> d'Apache 2. Vous pouvez compiler un module + L'ASF (Apache Software Foundation) a récemment publié sa première + version publique d'Apache 2. PHP 4.2.0 dispose du support + <strong>EXPERIMENTAL</strong> d'Apache 2. Vous pouvez compiler un module DSO pour Apache 2 avec l'option --with-apxs2. Nous recommandons - de <b>ne pas</b> utiliser cette combinaison en environnement de + de <strong>ne pas</strong> utiliser cette combinaison en environnement de production. </p> -<p>Il manque encore à PHP 4.2.0 des fonctionnalités clés -sur MacOSX et sur Darwin. PHP n'est donc pas officiellement -supporté par le PHP group sur ces plates-formes. Spécifiquement, -compiler PHP comme module Apache dynamiquement chargé n'est pas -encore supporté. PHP 4.3.0, dont la publication est prévue pour -Août 2002, sera la première version qui supportera officiellement -Mac OS X. Cette version, aussi bien pour les futures versions de +<p> + Il manque encore à PHP 4.2.0 des fonctionnalités clés + sur MacOSX et sur Darwin. PHP n'est donc pas officiellement + supporté par le PHP group sur ces plates-formes. Spécifiquement, + compiler PHP comme module Apache dynamiquement chargé n'est pas + encore supporté. PHP 4.3.0, dont la publication est prévue pour + Août 2002, sera la première version qui supportera officiellement + Mac OS X. Cette version, aussi bien pour les futures versions de Mac OS X et Apache, sera totalement synchronisé avec les autres - plates-formes PHP.</p> + plates-formes PHP. +</p> <h2>Améliorations</h2> -<p>PHP 4.2.0 inclut de nombreuses innovations : </p> + +<p>PHP 4.2.0 inclut de nombreuses innovations:</p> <ul> - <li><b>Les variables externes (issues de l'environnement d'exécution, -des requêtes HTTP, des cookies ou du serveur web) ne sont plus enregistrées -dans l'environnement d'exécution global par défaut. -</b></li> + <li> + <strong>Les variables externes (issues de l'environnement + d'exécution, des requêtes HTTP, des cookies ou du serveur web) + ne sont plus enregistrées dans l'environnement d'exécution + global par défaut. + </strnong> + </li> <li>Remise en état générale de l'extension socket</li> <li>Performances révolutionnaires des uploads de fichiers</li> - <li>Les extensions satellite (corba) et mailparse ont été placées sous PECL, - et ne sont plus fournies directement avec la distribution officielle de PHP.</li> + <li> + Les extensions satellite (corba) et mailparse ont été placées sous PECL, + et ne sont plus fournies directement avec la distribution officielle de PHP. + </li> <li>L'extension POSIX a été nettoyée</li> <li>L'extension iconv a été améliorée</li> - <li>Le support de la bufferisation d'affichage, introduite en PHP 4.1.0, - a été stabilisée.</li> - <li>Gain de performance notable et amélioration de la stabilité de l'extension domxml</li> + <li> + Le support de la bufferisation d'affichage, introduite en PHP 4.1.0, + a été stabilisée. + </li> + <li> + Gain de performance notable et amélioration de la + stabilité de l'extension domxml + </li> <li>Support des expressions régulières multi-octets</li> - <li><b>ENORMMENT</b> de corrections, et de nouvelles fonctions.</li> + <li><strong>ENORMMENT</strong> de corrections, et de nouvelles fonctions.</li> </ul> <p> -Pour une liste complète de changements en PHP 4.2.0, voyez le fichier -<a href="/ChangeLog-4.php">NEWS</a>, dans la distribution. + Pour une liste complète de changements en PHP 4.2.0, voyez le fichier + <a href="/ChangeLog-4.php#4.2.0">NEWS</a>, dans la distribution. </p> -<?php commonFooter(); ?> +<?php site_footer(); ?> Index: phpweb/release_4_2_0.php diff -u phpweb/release_4_2_0.php:1.12 phpweb/release_4_2_0.php:1.13 --- phpweb/release_4_2_0.php:1.12 Fri Apr 26 17:33:58 2002 +++ phpweb/release_4_2_0.php Thu Aug 14 08:21:39 2003 @@ -1,77 +1,82 @@ <?php -/* if you're reading this, it isn't because you've found a security hole. - this is an open source website. read and learn! */ - -header("Cache-Control: public, max-age=600"); - -require_once 'prepend.inc'; - -commonHeader("Hypertext Preprocessor"); -echo "\n<!--$MYSITE-->\n"; +// $Id: release_4_2_0.php,v 1.13 2003/08/14 12:21:39 goba Exp $ +$_SERVER['BASE_PAGE'] = 'release_4_2_0.php'; +include_once $_SERVER['DOCUMENT_ROOT'] . '/include/prepend.inc'; +site_header("PHP 4.2.0 Release Announcement"); ?> -<h1> -PHP 4.2.0 Release Announcement -</h1> +<h1>PHP 4.2.0 Release Announcement</h1> - -<p>After an orderly QA process, PHP 4.2.0 is <a href="/downloads.php">out</a>!<br> +<p>After an orderly QA process, PHP 4.2.0 is <a href="/downloads.php">out</a>!<br /> [ <a href="/release_4_2_0_fr.php">Version Française</a> ] </p> <h2>External variables</h2> -<p>The biggest change in PHP 4.2.0 concerns variable handling. <b>External +<p> + The biggest change in PHP 4.2.0 concerns variable handling. <strong>External variables (from the environment, the HTTP request, cookies or the web server) - are no longer registered in the global scope by default.</b> The preferred + are no longer registered in the global scope by default.</strong> The preferred method of accessing these external variables is by using the new Superglobal - arrays, introduced in PHP 4.1.0. More information about this change: + arrays, introduced in PHP 4.1.0. More information about this change:</p> + <ul> <li><a href="/manual/en/language.variables.predefined.php">PHP Manual: Predefined variables</a></li> <li><a href="/release_4_1_0.php">The PHP 4.1.0 release announcement</a></li> <li><a href="http://www.zend.com/zend/art/art-oertli.php">Thomas Oertli's article on secure programming in PHP</a></li> </ul> -</p> <h2>Compatibility</h2> -<p>The Apache Software Foundation recently released their first +<p> + The Apache Software Foundation recently released their first General Availability version of Apache 2. PHP 4.2.0 will have - <b>EXPERIMENTAL</b> support for this version. You can - build a DSO module for Apache 2 with --with-apxs2. We do <b>not</b> recommend - that you use this in a production environment. + <strong>EXPERIMENTAL</strong> support for this version. You can + build a DSO module for Apache 2 with --with-apxs2. We do + <strong>not</strong> recommend that you use this in a production + environment. </p> -<p>PHP 4.2.0 still lacks certain key features on Mac OS X and +<p> + PHP 4.2.0 still lacks certain key features on Mac OS X and Darwin, and isn't officially supported by the PHP Group on these platforms. Specifically, building PHP as a dynamically loaded Apache module isn't supported at this time. PHP 4.3.0, due to be released in August, 2002, will be the first PHP release to officially support Mac OS X. It, along with future Mac OS X and Apache releases, will enable full feature parity - with other PHP platforms. <b>Update:</b> + with other PHP platforms. <strong>Update:</strong> <a href="http://www.entropy.ch/software/macosx/php/">Instructions on - overcoming these limitations</a></p> + overcoming these limitations</a> +</p> <h2>Improvements</h2> + <p>PHP 4.2.0 includes several improvements:</p> + <ul> - <li><b>External variables (from the environment, the HTTP request, cookies or - the web server) are no longer registered as global variables</b></li> + <li> + <strong>External variables (from the environment, the HTTP request, cookies or + the web server) are no longer registered as global variables</strong> + </li> <li>Overhaul of the sockets extension</li> <li>Highly improved performance with file uploads</li> - <li>The satellite and mailparse extensions were moved to PECL and are no longer - bundled with the official PHP release</li> + <li> + The satellite and mailparse extensions were moved to PECL and are no longer + bundled with the official PHP release + </li> <li>The posix extension has been cleaned up</li> <li>iconv handling has been improved</li> - <li>Output buffering support, which was introduced in PHP 4.1.0 has - been stabilized</li> + <li> + Output buffering support, which was introduced in PHP 4.1.0 has + been stabilized + </li> <li>Improved performance and stability of the domxml extension</li> <li>New multibyte regular expression support</li> - <li><b>LOTS</b> of fixes and new functions</li> + <li><strong>LOTS</strong> of fixes and new functions</li> </ul> <p> -For a full list of changes in PHP 4.2.0, see the -<a href="/ChangeLog-4.php">NEWS</a> file. + For a full list of changes in PHP 4.2.0, + <a href="/ChangeLog-4.php#4.0.2">see the ChangeLog</a>. </p> -<?php commonFooter(); ?> +<?php site_footer(); ?>
Index: phpweb/release_4_1_0.php diff -u phpweb/release_4_1_0.php:1.11 phpweb/release_4_1_0.php:1.12 --- phpweb/release_4_1_0.php:1.11 Fri Apr 26 17:33:53 2002 +++ phpweb/release_4_1_0.php Thu Aug 14 08:21:39 2003 @@ -1,92 +1,107 @@ <?php -/* if you're reading this, it isn't because you've found a security hole. - this is an open source website. read and learn! */ - -header("Cache-Control: public, max-age=600"); - -require_once 'prepend.inc'; - -commonHeader("Hypertext Preprocessor"); -echo "\n<!--$MYSITE-->\n"; +// $Id: release_4_1_0.php,v 1.12 2003/08/14 12:21:39 goba Exp $ +$_SERVER['BASE_PAGE'] = 'release_4_1_0.php'; +include_once $_SERVER['DOCUMENT_ROOT'] . '/include/prepend.inc'; +site_header("PHP 4.1.0 Release Announcement"); ?> -<h1> -PHP 4.1.0 Release Announcement -</h1> +<h1>PHP 4.1.0 Release Announcement</h1> -<p>A <a href="release_4_1_0_fr.php">French translation</a> of this -announcement is also available.</p> +<p> + A <a href="release_4_1_0_fr.php">French translation</a> of this + announcement is also available. +</p> + +<p> + After a lengthy QA process, PHP 4.1.0 is <a href="/downloads.php">finally out</a>! +</p> -<p>After a lengthy QA process, PHP 4.1.0 is <a href="http://www.php.net/downloads.php">finally out</a>!</p> - -<p>PHP 4.1.0 includes several other key improvements:</p> +<p> PHP 4.1.0 includes several other key improvements:</p> <ul> <li>A new input interface for improved security (read below)</li> <li>Highly improved performance in general</li> - <li>Revolutionary performance and stability improvements under + <li> + Revolutionary performance and stability improvements under Windows. The multithreaded server modules under Windows (ISAPI, Apache, etc.) perform as much as 30 times faster under load! We want to thank Brett Brewer and his team in Microsoft for working - with us to improve PHP for Windows.</li> - <li>Versioning support for extensions. Right now it's barely being + with us to improve PHP for Windows. + </li> + <li> + Versioning support for extensions. Right now it's barely being used, but the infrastructure was put in place to support separate version numbers for different extensions. The negative side effect is that loading extensions that were built against old versions of PHP will now result in a crash, instead of in a nice clear message. - Make sure you only use extensions built with PHP 4.1.0.</li> + Make sure you only use extensions built with PHP 4.1.0. + </li> <li>Turn-key output compression support</li> - <li><b>LOTS</b> of fixes and new functions</li> + <li><strong>LOTS</strong> of fixes and new functions</li> </ul> -<p>As some of you may notice, this version is quite historic, as it's -the first time in history we actually incremented the middle digit! :) -The two key reasons for this unprecedented change were the new input -interface, and the broken binary compatibility of modules due to the -versioning support.</p> - -<p>Following is a description of the new input mechanism. For a full list of -changes in PHP 4.1.0, see the <a href="ChangeLog-4.php">changelog</a>.</p> +<p> + As some of you may notice, this version is quite historic, as it's + the first time in history we actually incremented the middle digit! :) + The two key reasons for this unprecedented change were the new input + interface, and the broken binary compatibility of modules due to the + versioning support. +</p> + +<p> + Following is a description of the new input mechanism. For a full list of + changes in PHP 4.1.0, see the <a href="ChangeLog-4.php">changelog</a>. +</p> <hr /> -<h2>SECURITY: NEW INPUT MECHANISM</h2> +<h2>SECURITY: NEW INPUT MECHANISM</h2> -<p>First and foremost, it's important to stress that regardless of -anything you may read in the following lines, PHP 4.1.0 <b>still supports</b> -the old input mechanisms from older versions. Old applications -should go on working fine without modification!</p> +<p> + First and foremost, it's important to stress that regardless of + anything you may read in the following lines, PHP 4.1.0 <strong>still + supports</strong> the old input mechanisms from older versions. + Old applications should go on working fine without modification! +</p> <p>Now that we have that behind us, let's move on :)</p> -<p>For various reasons, PHP setups which rely on register_globals -being on (i.e., on form, server and environment variables becoming -a part of the global namespace, automatically) are very often -exploitable to various degrees. For example, the piece of code:</p> +<p> + For various reasons, PHP setups which rely on register_globals + being on (i.e., on form, server and environment variables becoming + a part of the global namespace, automatically) are very often + exploitable to various degrees. For example, the piece of code: +</p> -<?php highlight_string('<?php +<?php highlight_php('<?php if (authenticate_user()) { $authenticated = true; } ... ?>');?> -<p>May be exploitable, as remote users can simply pass on 'authenticated' -as a form variable, and then even if authenticate_user() returns false, -$authenticated will actually be set to true. While this looks like a -simple example, in reality, quite a few PHP applications ended up being -exploitable by things related to this misfeature.</p> - -<p>While it is quite possible to write secure code in PHP, we felt that the -fact that PHP makes it too easy to write insecure code was bad, and we've -decided to attempt a far-reaching change, and deprecate register_globals. -Obviously, because the vast majority of the PHP code in the world relies -on the existence of this feature, we have no plans to actually remove it -from PHP anytime in the foreseeable future, but we've decided to encourage -people to shut it off whenever possible.</p> - -<p>To help users build PHP applications with register_globals being off, -we've added several new special variables that can be used instead of the -old global variables. There are 7 new special arrays:</p> +<p> + May be exploitable, as remote users can simply pass on 'authenticated' + as a form variable, and then even if authenticate_user() returns false, + $authenticated will actually be set to true. While this looks like a + simple example, in reality, quite a few PHP applications ended up being + exploitable by things related to this misfeature. +</p> + +<p> + While it is quite possible to write secure code in PHP, we felt that the + fact that PHP makes it too easy to write insecure code was bad, and we've + decided to attempt a far-reaching change, and deprecate register_globals. + Obviously, because the vast majority of the PHP code in the world relies + on the existence of this feature, we have no plans to actually remove it + from PHP anytime in the foreseeable future, but we've decided to encourage + people to shut it off whenever possible. +</p> + +<p> + To help users build PHP applications with register_globals being off, + we've added several new special variables that can be used instead of the + old global variables. There are 7 new special arrays: +</p> <ul> <li>$_GET - contains form variables sent through GET</li> @@ -94,51 +109,65 @@ <li>$_COOKIE - contains HTTP cookie variables</li> <li>$_SERVER - contains server variables (e.g., REMOTE_ADDR)</li> <li>$_ENV - contains the environment variables</li> - <li>$_REQUEST - a merge of the GET variables, POST variables and Cookie variables. - In other words - all the information that is coming from the user, - and that from a security point of view, cannot be trusted.</li> + <li> + $_REQUEST - a merge of the GET variables, POST variables and Cookie variables. + In other words - all the information that is coming from the user, + and that from a security point of view, cannot be trusted. + </li> <li>$_SESSION - contains HTTP variables registered by the session module</li> </ul> -<p>Now, other than the fact that these variables contain this special information, -they're also special in another way - they're automatically global in any -scope. This means that you can access them anywhere, without having to -'global' them first. For example:</p> +<p> + Now, other than the fact that these variables contain this special information, + they're also special in another way - they're automatically global in any + scope. This means that you can access them anywhere, without having to + 'global' them first. For example: +</p> -<?php highlight_string('<?php +<?php highlight_php('<?php function example1() { print $_GET["name"]; // works, \'global $_GET;\' is not necessary! } ?>');?> -<p>would work fine! We hope that this fact would ease the pain in migrating -old code to new code a bit, and we're confident it's going to make writing -new code easier. Another neat trick is that creating new entries in the -$_SESSION array will automatically register them as session variables, as -if you called session_register(). This trick is limited to the session -module only - for example, setting new entries in $_ENV will *not* perform -an implicit putenv().</p> - -<p>PHP 4.1.0 still defaults to have register_globals set to on. It's a -transitional version, and we encourage application authors, especially -public ones which are used by a wide audience, to change their applications -to work in an environment where register_globals is set to off. Of course, -they should take advantage of the new features supplied in PHP 4.1.0 that -make this transition much easier.</p> +<p> + would work fine! We hope that this fact would ease the pain in migrating + old code to new code a bit, and we're confident it's going to make writing + new code easier. Another neat trick is that creating new entries in the + $_SESSION array will automatically register them as session variables, as + if you called session_register(). This trick is limited to the session + module only - for example, setting new entries in $_ENV will *not* perform + an implicit putenv(). +</p> + +<p> + PHP 4.1.0 still defaults to have register_globals set to on. It's a + transitional version, and we encourage application authors, especially + public ones which are used by a wide audience, to change their applications + to work in an environment where register_globals is set to off. Of course, + they should take advantage of the new features supplied in PHP 4.1.0 that + make this transition much easier. +</p> -<p>As of the next semi-major version of PHP, new installations of PHP will -default to having register_globals set to off. No worries! Existing -installations, which already have a php.ini file that has register_globals -set to on, will not be affected. Only when you install PHP on a brand new -machine (typically, if you're a brand new user), will this affect you, and -then too - you can turn it on if you choose to.</p> - -<p>Note: Some of these arrays had old names, e.g. $HTTP_GET_VARS. These names -still work, but we encourage users to switch to the new shorter, and -auto-global versions.</p> - -<p>Thanks go to Shaun Clowes (shaun@securereality.com.au) for pointing out this -problem and for analyzing it.</p> +<p> + As of the next semi-major version of PHP, new installations of PHP will + default to having register_globals set to off. No worries! Existing + installations, which already have a php.ini file that has register_globals + set to on, will not be affected. Only when you install PHP on a brand new + machine (typically, if you're a brand new user), will this affect you, and + then too - you can turn it on if you choose to. +</p> + +<p> + Note: Some of these arrays had old names, e.g. $HTTP_GET_VARS. These names + still work, but we encourage users to switch to the new shorter, and + auto-global versions. +</p> + +<p> + Thanks go to Shaun Clowes (shaun@securereality.com.au) for pointing out this + problem and for analyzing it. +</p> -<?php commonFooter(); ?> +<?php site_footer(); ?> \ No newline at end of file Index: phpweb/release_4_1_1.php diff -u phpweb/release_4_1_1.php:1.4 phpweb/release_4_1_1.php:1.5 --- phpweb/release_4_1_1.php:1.4 Sun Feb 3 16:42:12 2002 +++ phpweb/release_4_1_1.php Thu Aug 14 08:21:39 2003 @@ -1,44 +1,64 @@ <?php -require_once 'prepend.inc'; - -commonHeader("PHP 4.1.1 Release Announcement"); +// $Id: release_4_1_1.php,v 1.5 2003/08/14 12:21:39 goba Exp $ +$_SERVER['BASE_PAGE'] = 'release_4_1_1.php'; +include_once $_SERVER['DOCUMENT_ROOT'] . '/include/prepend.inc'; +site_header("PHP 4.1.1 Release Announcement"); ?> -<h1> -PHP 4.1.1 Release Announcement -</h1> +<h1>PHP 4.1.1 Release Announcement</h1> + +<p> + Due to a few bugs in PHP 4.1.0, we decided to release PHP 4.1.1. The bugs + that were fixed are not major ones but minor ones, which could be annoying + if you get bitten by them. +</p> -<p>Due to a few bugs in PHP 4.1.0, we decided to release PHP 4.1.1. The bugs -that were fixed are not major ones but minor ones, which could be annoying -if you get bitten by them.</p> +<p> + Our recommendation is that people who already upgraded to PHP 4.1.0 do + <strong>not</strong> upgrade to <a href="/downloads.php">PHP 4.1.1</a>, + unless they're experiencing one of the described bugs. +</p> -<p>Our recommendation is that people who already upgraded to PHP 4.1.0 do -<b>not</b> upgrade to <a href="http://www.php.net/downloads.php">PHP 4.1.1</a>, -unless they're experiencing one of the described bugs.</p> +<p> + <strong>No</strong> new features or security updates are available + in this release. +</p> -<p><b>No</b> new features or security updates are available in this release.</p> +<p>Full list of fixes:</p> -<p>Full list of fixes: <ul> -<li>Fixed incompatibility with Windows .NET / IIS 6 - may improve stability - under other versions of IIS. (Zeev)</li> -<li>Fixed bug that caused crashes or error notices on shutdown on threaded - platforms. (Zeev)</li> -<li> Fixed several crash bugs in the xslt extension. (Markus, Derick)</li> -<li>Fixed problem with dbase not returning very large (larger than long) - integers properly. (Vlad)</li> -<li>Fixed several bugs and memleaks in the domxml extension. (Markus)</li> -<li>Fixed bug in gmmktime() which was one hour off during standard time - - bug #9878. Patch by bfoddy@mediaone.net. (jmoore)</li> -<li>Fixed bug in gmdate() timezone handling on Windows - bug #13885. (jmoore)</li> -<li>Fixed several crash bugs in the mcrypt extension. (Derick)</li> -<li>Made the mcrypt extension compile with the libmcrypt 2.2 series again. - (Sterling)</li> -<li>Fixed a bug where the is_file() family of functions would in-correctly give - an error when they were given filenames that didn't exist. (Sterling)</li> -<li>Fixed a bug in the strtotime() function where it was incorrectly recognizing - GMT +0100 and GMT -0100. (Derick)</li> + <li> + Fixed incompatibility with Windows .NET / IIS 6 - may improve stability + under other versions of IIS. (Zeev) + </li> + <li> + Fixed bug that caused crashes or error notices on shutdown on threaded + platforms. (Zeev) + </li> + <li>Fixed several crash bugs in the xslt extension. (Markus, Derick)</li> + <li> + Fixed problem with dbase not returning very large (larger than long) + integers properly. (Vlad) + </li> + <li>Fixed several bugs and memleaks in the domxml extension. (Markus)</li> + <li> + Fixed bug in gmmktime() which was one hour off during standard time - + bug #9878. Patch by bfoddy@mediaone.net. (jmoore) + </li> + <li>Fixed bug in gmdate() timezone handling on Windows - bug #13885. (jmoore)</li> + <li>Fixed several crash bugs in the mcrypt extension. (Derick)</li> + <li> + Made the mcrypt extension compile with the libmcrypt 2.2 series again. + (Sterling) + </li> + <li> + Fixed a bug where the is_file() family of functions would in-correctly give + an error when they were given filenames that didn't exist. (Sterling) + </li> + <li> + Fixed a bug in the strtotime() function where it was incorrectly recognizing + GMT +0100 and GMT -0100. (Derick) + </li> </ul> -</p> -<?php commonFooter(); ?> +<?php site_footer(); ?> Index: phpweb/release_4_1_2_win32.php diff -u phpweb/release_4_1_2_win32.php:1.1 phpweb/release_4_1_2_win32.php:1.2 --- phpweb/release_4_1_2_win32.php:1.1 Tue Mar 12 06:39:27 2002 +++ phpweb/release_4_1_2_win32.php Thu Aug 14 08:21:39 2003 @@ -1,49 +1,56 @@ <?php -require_once 'prepend.inc'; - -commonHeader("Hypertext Preprocessor"); +// $Id: release_4_1_2_win32.php,v 1.2 2003/08/14 12:21:39 goba Exp $ +$_SERVER['BASE_PAGE'] = 'release_4_1_2_win32.php'; +include_once $_SERVER['DOCUMENT_ROOT'] . '/include/prepend.inc'; +site_header("PHP 4.1.2 Windows (Win32) Release Announcement"); ?> -<h1> -PHP 4.1.2 Windows (Win32) Release Announcement -</h1> +<h1>PHP 4.1.2 Windows (Win32) Release Announcement</h1> <p> -Due to an issue with the Windows binary allowing any user to read or execute the contents of a -file directly from the PHP binary, we have delayed the 4.1.2 release of PHP for Windows to allow -for this fix. This release also fixes the file upload security problem.</p> - -<p>With this new release, we introduce 2 new php.ini settings, which MUST be set to make the binary -work. It's worth noting, at this point, that this particular fix only applies to the CGI binary. The -SAPI module will still work as expected, and it's use is encouraged.</p> + Due to an issue with the Windows binary allowing any user to read or + execute the contents of a file directly from the PHP binary, we have + delayed the 4.1.2 release of PHP for Windows to allow for this fix. + This release also fixes the file upload security problem. +</p> <p> -The new settings are: - <ul> - <li>cgi.force_redirect 0|1</li> - <li>cgi.redirect_status_env ENV_VAR_NAME</li> - </ul> + With this new release, we introduce 2 new php.ini settings, which + <strong>MUST</strong> be set to make the binary work. It's worth + noting, at this point, that this particular fix only applies to + the CGI binary. The SAPI module will still work as expected, + and it's use is encouraged. </p> +<p>The new settings are:</p> +<ul> + <li><tt>cgi.force_redirect 0|1</tt></li> + <li><tt>cgi.redirect_status_env ENV_VAR_NAME</tt></li> +</ul> + <h2>WebServers affected by this vulnerability</h2> <p> -It is known that Apache (any version) and iPlanet servers are vulnerable to this issue, however -Microsoft IIS is not. Since cgi.force_redirect takes a value of either 1 or 0, (on or off) you -should set it to 1 if you are running Apache or iPlanet servers, and to 0 for IIS. If you are -unsure of which you need, set it to 1 and see if your scripts execute. You will need to stop and -restart your server when you change your php.ini file, for the changes to have effect. + It is known that Apache (any version) and iPlanet servers are + vulnerable to this issue, however Microsoft IIS is not. Since + cgi.force_redirect takes a value of either 1 or 0, (on or off) + you should set it to 1 if you are running Apache or iPlanet + servers, and to 0 for IIS. If you are unsure of which you need, + set it to 1 and see if your scripts execute. You will need to + stop and restart your server when you change your php.ini file, + for the changes to have effect. </p> <p> -if cgi.force_redirect is turned on, and you are not running under Apache or Netscape -(iPlanet) web servers, you MAY need to set an environment variable name that PHP -will look for to know it is OK to continue execution. Setting this variable MAY -cause security issues, so check what you are doing first. + If cgi.force_redirect is turned on, and you are not running under + Apache or Netscape (iPlanet) web servers, you MAY need to set an + environment variable name that PHP will look for to know it is OK + to continue execution. Setting this variable MAY cause security + issues, so check what you are doing first. </p> <p> -More information can be found <a href="http://security.e-matters.de/advisories/012002.html">here</a> -relating to the form upload exploit that caused the release of 4.1.2 initially. + More information can be found <a href="http://security.e-matters.de/advisories/012002.html">here</a> + relating to the form upload exploit that caused the release of 4.1.2 initially. </p> -<?php commonFooter(); ?> \ No newline at end of file +<?php site_footer(); ?> Index: phpweb/release_4_2_0_fr.php diff -u phpweb/release_4_2_0_fr.php:1.5 phpweb/release_4_2_0_fr.php:1.6 --- phpweb/release_4_2_0_fr.php:1.5 Sun Mar 2 11:56:37 2003 +++ phpweb/release_4_2_0_fr.php Thu Aug 14 08:21:39 2003 @@ -1,77 +1,91 @@ <?php -header("Cache-Control: public, max-age=600"); -require_once 'prepend.inc'; -header("Content-language: fr"); -commonHeader("Hypertext Preprocessor"); -echo "\n<!--$MYSITE-->\n"; +// $Id: release_4_2_0_fr.php,v 1.6 2003/08/14 12:21:39 goba Exp $ +$_SERVER['BASE_PAGE'] = 'release_4_2_0_fr.php'; +include_once $_SERVER['DOCUMENT_ROOT'] . '/include/prepend.inc'; +site_header("Annonce de publication de PHP 4.2.0"); ?> -<h1> -Annonce de PHP 4.2.0 -</h1> +<h1>Annonce de publication de PHP 4.2.0</h1> -<p>Après avoir passé avec succès le processus qualité, PHP 4.2.0 est officiellement <a href="http://www.php.net/downloads.php">publié</a>!</p> +<p> + Après avoir passé avec succès le processus + qualité, PHP 4.2.0 est officiellement <a href="/downloads.php">publié</a>! +</p> <h2>Variables externes</h2> <p> -Le changement le plus important de PHP 4.2.0 concerne la gestion des - variables. Les <b>variables externes (issues de l'environnement d'exécution, -des requêtes HTTP, des cookies ou du serveur web) ne sont plus enregistrées -dans l'environnement d'exécution global par défaut.</b> La méthode recommandée -pour accéder aux variables externes est d'utiliser les nouveaux tableaux globaux, -introduits en PHP 4.1.0. Pour plus d'informations sur ces modifications : + Le changement le plus important de PHP 4.2.0 concerne la gestion des + variables. Les <strong>variables externes (issues de l'environnement d'exécution, + des requêtes HTTP, des cookies ou du serveur web) ne sont plus enregistrées + dans l'environnement d'exécution global par défaut.</strong> + La méthode recommandée pour accéder aux variables + externes est d'utiliser les nouveaux tableaux globaux, introduits en + PHP 4.1.0. Pour plus d'informations sur ces modifications: +</p> <ul> <li><a href="http://www.php.net/manual/en/language.variables.predefined.php">PHP Manual : Predefined variables</a></li> <li><a href="http://www.php.net/release_4_1_0.php">Annonce de PHP 4.1.0</a></li> <li><a href="http://www.zend.com/zend/art/art-oertli.php">Article de Thomas Oertli sur la programmation sécurisée en PHP</a></li> <li><a href="http://www.phpinfo.net/?p=articles&rub=globals">Article de Jean Pierre Dézelus sur les variables globales</a></li> </ul> -</p> <h2>Compatibilité</h2> <p> -L'ASF (Apache Software Foundation) a récemment publié sa première -version publique d'Apache 2. PHP 4.2.0 dispose du support - <b>EXPERIMENTAL</b> d'Apache 2. Vous pouvez compiler un module + L'ASF (Apache Software Foundation) a récemment publié sa première + version publique d'Apache 2. PHP 4.2.0 dispose du support + <strong>EXPERIMENTAL</strong> d'Apache 2. Vous pouvez compiler un module DSO pour Apache 2 avec l'option --with-apxs2. Nous recommandons - de <b>ne pas</b> utiliser cette combinaison en environnement de + de <strong>ne pas</strong> utiliser cette combinaison en environnement de production. </p> -<p>Il manque encore à PHP 4.2.0 des fonctionnalités clés -sur MacOSX et sur Darwin. PHP n'est donc pas officiellement -supporté par le PHP group sur ces plates-formes. Spécifiquement, -compiler PHP comme module Apache dynamiquement chargé n'est pas -encore supporté. PHP 4.3.0, dont la publication est prévue pour -Août 2002, sera la première version qui supportera officiellement -Mac OS X. Cette version, aussi bien pour les futures versions de +<p> + Il manque encore à PHP 4.2.0 des fonctionnalités clés + sur MacOSX et sur Darwin. PHP n'est donc pas officiellement + supporté par le PHP group sur ces plates-formes. Spécifiquement, + compiler PHP comme module Apache dynamiquement chargé n'est pas + encore supporté. PHP 4.3.0, dont la publication est prévue pour + Août 2002, sera la première version qui supportera officiellement + Mac OS X. Cette version, aussi bien pour les futures versions de Mac OS X et Apache, sera totalement synchronisé avec les autres - plates-formes PHP.</p> + plates-formes PHP. +</p> <h2>Améliorations</h2> -<p>PHP 4.2.0 inclut de nombreuses innovations : </p> + +<p>PHP 4.2.0 inclut de nombreuses innovations:</p> <ul> - <li><b>Les variables externes (issues de l'environnement d'exécution, -des requêtes HTTP, des cookies ou du serveur web) ne sont plus enregistrées -dans l'environnement d'exécution global par défaut. -</b></li> + <li> + <strong>Les variables externes (issues de l'environnement + d'exécution, des requêtes HTTP, des cookies ou du serveur web) + ne sont plus enregistrées dans l'environnement d'exécution + global par défaut. + </strnong> + </li> <li>Remise en état générale de l'extension socket</li> <li>Performances révolutionnaires des uploads de fichiers</li> - <li>Les extensions satellite (corba) et mailparse ont été placées sous PECL, - et ne sont plus fournies directement avec la distribution officielle de PHP.</li> + <li> + Les extensions satellite (corba) et mailparse ont été placées sous PECL, + et ne sont plus fournies directement avec la distribution officielle de PHP. + </li> <li>L'extension POSIX a été nettoyée</li> <li>L'extension iconv a été améliorée</li> - <li>Le support de la bufferisation d'affichage, introduite en PHP 4.1.0, - a été stabilisée.</li> - <li>Gain de performance notable et amélioration de la stabilité de l'extension domxml</li> + <li> + Le support de la bufferisation d'affichage, introduite en PHP 4.1.0, + a été stabilisée. + </li> + <li> + Gain de performance notable et amélioration de la + stabilité de l'extension domxml + </li> <li>Support des expressions régulières multi-octets</li> - <li><b>ENORMMENT</b> de corrections, et de nouvelles fonctions.</li> + <li><strong>ENORMMENT</strong> de corrections, et de nouvelles fonctions.</li> </ul> <p> -Pour une liste complète de changements en PHP 4.2.0, voyez le fichier -<a href="/ChangeLog-4.php">NEWS</a>, dans la distribution. + Pour une liste complète de changements en PHP 4.2.0, voyez le fichier + <a href="/ChangeLog-4.php#4.2.0">NEWS</a>, dans la distribution. </p> -<?php commonFooter(); ?> +<?php site_footer(); ?> Index: phpweb/release_4_2_0.php diff -u phpweb/release_4_2_0.php:1.12 phpweb/release_4_2_0.php:1.13 --- phpweb/release_4_2_0.php:1.12 Fri Apr 26 17:33:58 2002 +++ phpweb/release_4_2_0.php Thu Aug 14 08:21:39 2003 @@ -1,77 +1,82 @@ <?php -/* if you're reading this, it isn't because you've found a security hole. - this is an open source website. read and learn! */ - -header("Cache-Control: public, max-age=600"); - -require_once 'prepend.inc'; - -commonHeader("Hypertext Preprocessor"); -echo "\n<!--$MYSITE-->\n"; +// $Id: release_4_2_0.php,v 1.13 2003/08/14 12:21:39 goba Exp $ +$_SERVER['BASE_PAGE'] = 'release_4_2_0.php'; +include_once $_SERVER['DOCUMENT_ROOT'] . '/include/prepend.inc'; +site_header("PHP 4.2.0 Release Announcement"); ?> -<h1> -PHP 4.2.0 Release Announcement -</h1> +<h1>PHP 4.2.0 Release Announcement</h1> - -<p>After an orderly QA process, PHP 4.2.0 is <a href="/downloads.php">out</a>!<br> +<p>After an orderly QA process, PHP 4.2.0 is <a href="/downloads.php">out</a>!<br /> [ <a href="/release_4_2_0_fr.php">Version Française</a> ] </p> <h2>External variables</h2> -<p>The biggest change in PHP 4.2.0 concerns variable handling. <b>External +<p> + The biggest change in PHP 4.2.0 concerns variable handling. <strong>External variables (from the environment, the HTTP request, cookies or the web server) - are no longer registered in the global scope by default.</b> The preferred + are no longer registered in the global scope by default.</strong> The preferred method of accessing these external variables is by using the new Superglobal - arrays, introduced in PHP 4.1.0. More information about this change: + arrays, introduced in PHP 4.1.0. More information about this change:</p> + <ul> <li><a href="/manual/en/language.variables.predefined.php">PHP Manual: Predefined variables</a></li> <li><a href="/release_4_1_0.php">The PHP 4.1.0 release announcement</a></li> <li><a href="http://www.zend.com/zend/art/art-oertli.php">Thomas Oertli's article on secure programming in PHP</a></li> </ul> -</p> <h2>Compatibility</h2> -<p>The Apache Software Foundation recently released their first +<p> + The Apache Software Foundation recently released their first General Availability version of Apache 2. PHP 4.2.0 will have - <b>EXPERIMENTAL</b> support for this version. You can - build a DSO module for Apache 2 with --with-apxs2. We do <b>not</b> recommend - that you use this in a production environment. + <strong>EXPERIMENTAL</strong> support for this version. You can + build a DSO module for Apache 2 with --with-apxs2. We do + <strong>not</strong> recommend that you use this in a production + environment. </p> -<p>PHP 4.2.0 still lacks certain key features on Mac OS X and +<p> + PHP 4.2.0 still lacks certain key features on Mac OS X and Darwin, and isn't officially supported by the PHP Group on these platforms. Specifically, building PHP as a dynamically loaded Apache module isn't supported at this time. PHP 4.3.0, due to be released in August, 2002, will be the first PHP release to officially support Mac OS X. It, along with future Mac OS X and Apache releases, will enable full feature parity - with other PHP platforms. <b>Update:</b> + with other PHP platforms. <strong>Update:</strong> <a href="http://www.entropy.ch/software/macosx/php/">Instructions on - overcoming these limitations</a></p> + overcoming these limitations</a> +</p> <h2>Improvements</h2> + <p>PHP 4.2.0 includes several improvements:</p> + <ul> - <li><b>External variables (from the environment, the HTTP request, cookies or - the web server) are no longer registered as global variables</b></li> + <li> + <strong>External variables (from the environment, the HTTP request, cookies or + the web server) are no longer registered as global variables</strong> + </li> <li>Overhaul of the sockets extension</li> <li>Highly improved performance with file uploads</li> - <li>The satellite and mailparse extensions were moved to PECL and are no longer - bundled with the official PHP release</li> + <li> + The satellite and mailparse extensions were moved to PECL and are no longer + bundled with the official PHP release + </li> <li>The posix extension has been cleaned up</li> <li>iconv handling has been improved</li> - <li>Output buffering support, which was introduced in PHP 4.1.0 has - been stabilized</li> + <li> + Output buffering support, which was introduced in PHP 4.1.0 has + been stabilized + </li> <li>Improved performance and stability of the domxml extension</li> <li>New multibyte regular expression support</li> - <li><b>LOTS</b> of fixes and new functions</li> + <li><strong>LOTS</strong> of fixes and new functions</li> </ul> <p> -For a full list of changes in PHP 4.2.0, see the -<a href="/ChangeLog-4.php">NEWS</a> file. + For a full list of changes in PHP 4.2.0, + <a href="/ChangeLog-4.php#4.0.2">see the ChangeLog</a>. </p> -<?php commonFooter(); ?> +<?php site_footer(); ?>