[PHP] PHP 5.3.7 Released!
The PHP development team would like to announce the immediate availability of PHP 5.3.7. This release focuses on improving the stability of the PHP 5.3.x branch with over 90 bug fixes, some of which are security related. Security Enhancements and Fixes in PHP 5.3.7: * Updated crypt_blowfish to 1.2. (CVE-2011-2483) * Fixed crash in error_log(). Reported by Mateusz Kocielski * Fixed buffer overflow on overlog salt in crypt(). * Fixed bug #54939 (File path injection vulnerability in RFC1867 File upload filename). Reported by Krzysztof Kotowicz. (CVE-2011-2202) * Fixed stack buffer overflow in socket_connect(). (CVE-2011-1938) * Fixed bug #54238 (use-after-free in substr_replace()). (CVE-2011-1148) Key enhancements in PHP 5.3.7 include: * Upgraded bundled Sqlite3 to version 3.7.7.1 * Upgraded bundled PCRE to version 8.12 * Fixed bug #54910 (Crash when calling call_user_func with unknown function name) * Fixed bug #54585 (track_errors causes segfault) * Fixed bug #54262 (Crash when assigning value to a dimension in a non-array) * Fixed a crash inside dtor for error handling * Fixed bug #55339 (Segfault with allow_call_time_pass_reference = Off) * Fixed bug #54935 php_win_err can lead to crash * Fixed bug #54332 (Crash in zend_mm_check_ptr // Heap corruption) * Fixed bug #54305 (Crash in gc_remove_zval_from_buffer) * Fixed bug #54580 (get_browser() segmentation fault when browscap ini directive is set through php_admin_value) * Fixed bug #54529 (SAPI crashes on apache_config.c:197) * Fixed bug #54283 (new DatePeriod(NULL) causes crash). * Fixed bug #54269 (Short exception message buffer causes crash) * Fixed Bug #54221 (mysqli::get_warnings segfault when used in multi queries) * Fixed bug #54395 (Phar::mount() crashes when calling with wrong parameters) * Fixed bug #54384 (Dual iterators, GlobIterator, SplFileObject and SplTempFileObject crash when user-space classes don't call the parent constructor) * Fixed bug #54292 (Wrong parameter causes crash in SplFileObject::__construct()) * Fixed bug #54291 (Crash iterating DirectoryIterator for dir name starting with \0) * Fixed bug #54281 (Crash in non-initialized RecursiveIteratorIterator) * Fixed bug #54623 (Segfault when writing to a persistent socket after closing a copy of the socket) * Fixed bug #54681 (addGlob() crashes on invalid flags) * Over 80 other bug fixes. Windows users: please mind that we do no longer provide builds created with Visual Studio C++ 6. It is impossible to maintain a high quality and safe build of PHP for Windows using this unmaintained compiler. For Apache SAPIs (php5_apache2_2.dll), be sure that you use a Visual Studio C++ 9 version of Apache. We recommend the Apache builds as provided by ApacheLounge. For any other SAPI (CLI, FastCGI via mod_fcgi, FastCGI with IIS or other FastCGI capable server), everything works as before. Third party extension providers must rebuild their extensions to make them compatible and loadable with the Visual Studio C++9 builds that we now provide./p All PHP users should note that the PHP 5.2 series is NOT supported anymore. All users are strongly encouraged to upgrade to PHP 5.3.7. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] PHP 5.3.7RC5 Released for Testing
The fifth and final release candidate of 5.3.7 was just released for testing and can be downloaded here: https://downloads.php.net/ilia/php-5.3.7RC5.tar.bz2 (md5sum: 2604b92812e213287fa0fbc5d61223db) https://downloads.php.net/ilia/php-5.3.7RC5.tar.gz (md5sum: 2d3315be5ef7ab90ca359978f36c2001) The Windows binaries are available at: http://windows.php.net/qa/ This RC is in place to validate the changes resulting from various code adjustments made to address issues identified by static analysis. If no issues arise the final release will be made next week. To make sure we can finally get 5.3.7 out of the door, I would like to ask that all developers refrain from making commits into the 5.3 branch, until the final release is made (especially those on working on Coverity identified issues). PHP 5.3.7 is focused on improving the stability and security. To ensure that the release is solid, please test this RC against your code base and report any problems that you encounter. To find out what was changed since the last release please refer to the NEWS file found within the archive or on http://svn.php.net/viewvc/php/php-src/tags/php_5_3_7RC5/NEWS?revision=HEADview=markup Windows users please mind that we don't provide VS6 builds anymore since PHP 5.3.6. Ilia Alshanetsky -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] PHP 5.3.7RC4 Released for Testing
The fourth and hopefully final release candidate of 5.3.7 was just released for testing and can be downloaded here: https://downloads.php.net/ilia/php-5.3.7RC4.tar.bz2 (md5sum: 143ae4c3c5df93e2a9efae532cb51790) https://downloads.php.net/ilia/php-5.3.7RC4.tar.gz (md5sum: 8543604a0f171424c73ccaff5061f7ba) The Windows binaries are available at: http://windows.php.net/qa/ There were a few important fixes made since RC3 and this new RC is designed to validate that these fixes have not introduced any regressions. The intent is that this is the final release candidate before the final release, which if all goes well will follow in 2 weeks. PHP 5.3.7 is focused on improving the stability and security. To ensure that the release is solid, please test this RC against your code base and report any problems that you encounter. To find out what was changed since the last release please refer to the NEWS file found within the archive or on http://svn.php.net/viewvc/php/php-src/tags/php_5_3_7RC4/NEWS?revision=HEADview=markup Windows users please mind that we don't provide VS6 builds anymore since PHP 5.3.6. Ilia Alshanetsky -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] PHP 5.3.7RC3 Released for Testing
The third and hopefully final release candidate of 5.3.7 was just released for testing and can be downloaded here: https://downloads.php.net/ilia/php-5.3.7RC3.tar.bz2 (md5sum: 0ad46340ca3d4319ab10eac4a3978ae0) https://downloads.php.net/ilia/php-5.3.7RC3.tar.gz (md5sum: eab0329078f74f6c8fe5abcf6943b262) The Windows binaries are available at: http://windows.php.net/qa/ Given the volume of fixes since RC2 it was deemed necessary to make another to ensure that there are no regressions. The intent is that this is the final release candidate before the final release, which if all goes well will follow in 2 weeks. PHP 5.3.7 is focused on improving the stability and security. To ensure that the release is solid, please test this RC against your code base and report any problems that you encounter. To find out what was changed since the last release please refer to the NEWS file found within the archive or on http://svn.php.net/viewvc/php/php-src/tags/php_5_3_7RC3/NEWS?revision=HEADview=markup Windows users please mind that we don't provide VS6 builds anymore since PHP 5.3.6. Ilia Alshanetsky -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] PHP 5.3.7RC2 Released for Testing
The second release candidate of 5.3.7 was just released for testing and can be downloaded here: https://downloads.php.net/ilia/php-5.3.7RC2.tar.bz2 (md5sum: 1f4fba48807d5d6236b24ca1f1b63e69) https://downloads.php.net/ilia/php-5.3.7RC2.tar.gz (md5sum: d57c2d49d4e9c8a90d31068d88605ef2) The Windows binaries are available at: http://windows.php.net/qa/ Given the small number of changes since the last RC, it is likely a final version will be released in 2 weeks. If it is not, a third release candidate will be available in 2 weeks. PHP 5.3.7 is focused on improving the stability and security. To ensure that the release is solid, please test this RC against your code base and report any problems that you encounter. To find out what was changed since the last release please refer to the NEWS file found within the archive or on http://svn.php.net/viewvc/php/php-src/tags/php_5_3_7RC2/NEWS?revision=HEADview=markup Windows users please mind that we don't provide VS6 builds anymore since PHP 5.3.6. When using the openssl extension please mind a known regression which might lead to a performance degression. This regression will be fixed with RC2 and the final release. Ilia Alshanetsky -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] PHP 5.2.16 Released!
The PHP development team would like to announce the immediate availability of PHP 5.2.16. This release marks the end of support for PHP 5.2. All users of PHP 5.2 are encouraged to upgrade to PHP 5.3. This release focuses on addressing a regression in open_basedir implementation introduced in 5.2.15 in addition to fixing a crash inside PDO::pgsql on data retrieval when the server is down. All users who have upgraded to 5.2.15 and are utilizing open_basedir are strongly encouraged to upgrade to 5.2.16 or 5.3.4. For a full list of changes in PHP 5.2.16, see the ChangeLog on http://php.net/ChangeLog-5.php#5.2.16. For source downloads please visit our downloads page on http://php.net/downloads.php, Windows binaries can be found on http://windows.php.net/download/. Ilia Alshanetsky 5.2 Release Master -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] PHP 5.2.15 Released!
The PHP development team would like to announce the immediate availability of PHP 5.2.15. This release marks the end of support for PHP 5.2. All users of PHP 5.2 are encouraged to upgrade to PHP 5.3. This release focuses on improving the security and stability of the PHP 5.2.x branch with a small number, of predominatly security fixes. Security Enhancements and Fixes in PHP 5.2.15: Fixed extract() to do not overwrite $GLOBALS and $this when using EXTR_OVERWRITE. Fixed crash in zip extract method (possible CWE-170). Fixed a possible double free in imap extension. Fixed possible flaw in open_basedir (CVE-2010-3436). Fixed NULL pointer dereference in ZipArchive::getArchiveComment. (CVE-2010-3709). Fixed bug #52929 (Segfault in filter_var with FILTER_VALIDATE_EMAIL with large amount of data). Key enhancements in PHP 5.2.15 include: Fixed bug #47643 (array_diff() takes over 3000 times longer than php 5.2.4). Fixed bug #44248 (RFC2616 transgression while HTTPS request through proxy with SoapClient object). For a full list of changes in PHP 5.2.15, see the ChangeLog on http://php.net/ChangeLog-5.php#5.2.15. For source downloads please visit our downloads page on http://php.net/downloads.php, Windows binaries can be found on http://windows.php.net/download/. Ilia Alshanetsky 5.2 Release Master -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] PHP 5.2.15RC2 5.3.4RC2 Released for Testing
The second release candidates of 5.2.15 and 5.3.4 were just released for testing and can be downloaded here: http://downloads.php.net/ilia/php-5.2.15RC2.tar.bz2 (md5sum: 423e70e49f8defd63c6a08d824357f36) http://downloads.php.net/johannes/php-5.3.4RC2.tar.bz2 (md5sum: 36f7854304f9ecaa28d56f0eb163) The windows binaries will be available shortly at: http://windows.php.net/qa/ Since the first release candidate, we have not seen a large number of changes and and there are no show-stopper bugs for either version. At this point we both feel that the next logical step is the final release, which we would like to schedule a week from now. Given that this is the case, we would like to ask all developers to refrain making commits to the 5.3 and 5.2 branches, unless these constitue critical bug fixes, in which case please let Johannes and myself know about these fixes ahead of time. This way we can avoid last minute regressions, especially so for the 5.2.15 release, which is the final one in that series. Ilia Alshanetsky Johannes Schlüter PHP 5.2 Release Master PHP 5.3 Release Master -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] PHP 5.2.8 Released
The PHP development team would like to announce the immediate availability of PHP 5.2.8. This release addresses a regression introduced by 5.2.7 in regard to the magic_quotes functionality, that was broken by an incorrect fix to the filter extension. All users who have upgraded to 5.2.7 are encouraged to upgrade to this release, alternatively you can apply a work-around for the bug by changing filter.default_flags=0 in php.ini. For users upgrading from PHP 5.0 and PHP 5.1, an upgrade guide is available here (http://www.php.net/migration52), detailing the changes between those releases and PHP 5.2.8. For a full list of changes in PHP 5.2.8, see the ChangeLog (http://www.php.net/ChangeLog-5.php#5.2.8). Ilia Alshanetsky 5.2 Release Master -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] PHP 5.2.7 Released
The PHP development team would like to announce the immediate availability of PHP 5.2.7. This release focuses on improving the stability of the PHP 5.2.x branch with over 170 bug fixes, several of which are security related. All users of PHP are encouraged to upgrade to this release. Security Enhancements and Fixes in PHP 5.2.7: * Upgraded PCRE to version 7.8 (Fixes CVE-2008-2371) * Fixed missing initialization of BG(page_uid) and BG(page_gid), reported by Maksymilian Arciemowicz. * Fixed a crash inside gd with invalid fonts (Fixes CVE-2008-3658). * Fixed a possible overflow inside memnstr (Fixes CVE-2008-3659). * Fixed incorrect php_value order for Apache configuration, reported by Maksymilian Arciemowicz. * Fixed safe_mode related security issues detailed in CVE-2008-2665 and CVE-2008-2666. * Crash with URI/file..php (filename contains 2 dots) (Fixes CVE-2008-3660) * IMAP toolkit crash: rfc822.c legacy routine buffer overflow. (Fixes CVE-2008-2829) Some of the key enhancements in PHP 5.2.7 include: * Fixed several memory leaks inside the readline and sqlite extensions * A number of corrections relating to date parsing inside the date extension * Fixed bugs relating to data retrieval in the PDO extension * A series of crashes in various areas of code were resolved * Several corrections were made to the strip_tags() function in terms of and ?XML handling * A number of bugs were fixed in extract() function when EXTR_REFS flag is being used * Added the ability to log PHP errors to the SAPI (Ex. Apache log) logging facility * Over 170 bug fixes. For users upgrading from PHP 5.0 and PHP 5.1, an upgrade guide is available here (http://www.php.net/migration52), detailing the changes between those releases and PHP 5.2.7. For a full list of changes in PHP 5.2.7, see the ChangeLog (http://www.php.net/ChangeLog-5.php#5.2.7). Ilia Alshanetsky 5.2 Release Master -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] ldappasswd equivalent on PHP
Dear Sirs, I installed smbk5pwd, that module catches password change request and synchronises both samba and kerberos passwords. How can I do the same by php/ldap functions (not by calling external binary ldappasswd) ? Cheers, Ilia Chipitsine -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] PHP 4.3.9 Released
Here is the proposed 4.3.9 release announcement. PHP Development Team is proud to announce the immediate release of PHP 4.3.9. This is a maintenance release that in addition to over 50 non-critical bug fixes, addresses a problem with GPC input processing. This release also re-introduces ability to write GIF images via the bundled GD extension. All Users of PHP are encouraged to upgrade to this release as soon as possible. Aside from the above mentioned issues this release includes the following important fixes: * Implemented periodic PCRE compiled regexp cache cleanup, to avoid memory exhaustion * Fixed strip_tags() to correctly handle '\0' characters. * Rewritten UNIX and Windows install help files. * Fixed a file-descriptor leak with phpinfo() and other 'special' URLs. * Fixed possible crash inside php_shutdown_config(). * Fixed isset crashes on arrays. * Fixed imagecreatefromstring() crashes with external GD library. * Fixed fgetcsv() parsing of strings ending with escaped enclosures. * Fixed overflow in array_slice(), array_splice(), substr(), substr_replace(), strspn(), strcspn(). * Fixed '\0' in Authenticate header passed via safe_mode. * Allow bundled GD to compile against freetype 2.1.2. All in all this release fixes over 50 bugs that have been discovered and resolved since the 4.3.8 release. PHP Development Team -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Hokki =)
Looking forward for a response :P pass: 74434 -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] PHP 4.3.7 Released
PHP Development Team is proud to announce the release of PHP 4.3.7. This is a maintenance release that in addition to several non-critical bug fixes, addresses an input validation vulnerability in escapeshellcmd() and escapeshellarg() functions on the Windows platform. Users of PHP on Windows are encouraged to upgrade to this release as soon as possible. Aside from the above mentioned issues this release includes the following important fixes: Synchronized bundled GD library with GD 2.0.23. Fixed a bug that prevented compilation of GD extensions against FreeType 2.1.0-2.1.2. Fixed thread safety issue with informix connection id. Fixed incorrect resolving of relative paths by glob() in windows. Fixed mapping of Greek letters to html entities. Fixed a bug that caused an on shutdown crash when using PHP with Apache 2.0.49. Fixed a number of crashes inside pgsql, cpdf and gd extensions. All in all this release fixes over 30 bugs that have been discovered and resolved since the 4.3.6 release. Enjoy, PHP Development Team. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] PHP 4.3.5 Released
PHP Development Team is proud to announce the release of PHP 4.3.5. This is primarily a bug fix release, without any new features or additions.PHP 4.3.5 is by far the most stable release of PHP to date and it is recommended that all users upgrade to this release whenever possible. The major fixes include: - Fixed INI leak between Apache virtual hosts. - Fixed crashes inside fgetcsv() and make the function binary safe. - Fixed compilation with early versions of GCC 3.0. - Fixed a bug that prevented feof() from working correctly with sockets. - Improved the matching algorithm inside the get_browser() function. - Fixed resolving of open_basedir on Win32 systems. - Fixed incorrect errors for non-existent directories when safe_mode is enabled. - Bundled OpenSSL dlls on Win32 upgraded to 0.9.7c - Updated bundled PostgreSQL library to version 7.4 in Windows distribution. - Bundled PCRE library upgraded to 4.5 - Synchronized bundled GD library with GD 2.0.17 - A number of fixes for 64bit systems. Aside from the above mentioned fixes, this release resolves over 140 various bugs and implementational problems. Enjoy, PHP Development Team. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] PHP 4.3.5RC4 Released for Testing
The much overdue 4.3.5RC4 is finally out and hopefully will shortly (within a week) be followed by the final release. In the meantime please download this release, which is avaliable from http://qa.php.net/ and try it with against your code as well as make test. While I do not anticipate any major problems to be discovered this will ensure that 4.3.5 will be 100% production ready. If you do come across any critical issues or are of aware of some, please report them. For those of you who will run the PHP's test suite via make test, please do not be alarmed by the following test failures: Bug #25547 (error_handler and array index with function call) [tests/lang/bug25547.phpt] Bug #24594 (Filling an area using tiles). [ext/gd/tests/bug27582_2.phpt] Download URLs: http://downloads.php.net/ilia/php-4.3.5RC4.tar.bz2 http://downloads.php.net/ilia/php-4.3.5RC4.tar.gz http://downloads.php.net/ilia/php-4.3.5RC4-Win32.zip -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] PHP 4.3.4 Released
PHP 4.3.4 has been released. The focus of this release was the resolution of bugs and at the time of release some 70 bugs were resolved. All users are encouraged to upgrade to 4.3.4. PHP 4.3.4 contains, among others, following important fixes: * Fixed disk_total_space() and disk_free_space() under FreeBSD. * Fixed FastCGI being unable to bind to a specific IP. * Fixed several bugs in mail() implementation on win32. * Fixed crashes in a number of functions. * Fixed compile failure on MacOSX 10.3 Panther. Enjoy, PHP Development Team. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] PHP 4.3.3 released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After a lengthy QA process, PHP 4.3.3 is finally out! This maintenance release solves a fair number of bugs found in prior PHP versions and addresses several security issues. All users are *strongly* advised to upgrade to 4.3.3 as soon as possible. PHP 4.3.3 contains, among others, following important fixes, additions and improvements: * Improved the engine to use POSIX/socket IO where feasible. * Fixed several potentially hazardous integer and buffer overflows. * Fixed corruption of multibyte character including 0x5c as second byte in multipart/form-data. * Fixed each() to be binary safe for keys. * Major improvements to the NSAPI SAPI * Improvements to the IMAP extension * Improvements to the InterBase extension * Added DBA handler 'inifile' to support ini files. * Added long options into CLI CGI (e.g. --version). * Added a new parameter to preg_match*() that can be used to specify the starting offset in the subject string to match from. * Upgraded the bundled Expat library to version 1.95.6 * Upgraded the bundled PCRE library to version 4.3 * Upgraded the bundled GD library to version GD 2.0.15 * Over 100 various bug fixes! For a full list of changes in PHP 4.3.2, see the NEWS file. (http://www.php.net/ChangeLog-4.php#4.3.3). md5sums: 1171d96104e2ff2cff9e19789a4a1536php-4.3.3.tar.bz2 fe3fede4115354155fc6185522f7c6b2php-4.3.3.tar.gz c3497c394b3f5829136eb2ff614da241php-4.3.3-Win32.zip 140b98d796e81402776a133f273f0b38php-4.3.3-installer.exe Have fun, Ilia Alshanetsky [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE/ShTMLKekh381/CERAn5VAJ9SlW4lGGwGMXGpvs2blhS8R6Sl5ACcCkPV wWiX4ZLugm1K8xVIj2e0sKo= =xxIX -END PGP SIGNATURE- -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] PHP 4.3.3RC4 Released
RC3 did not prove as stable as I hoped it would be, so here we are 20+ bug fixes later with RC4. It is my sincere hope that RC4 will be the last RC before we can proceed with the final. Please test this release as much as possible, ideally you won't find any new bugs. Once again I would like to ask that all developers refrain from making commits to the 4_3 tree until 4.3.3 final is released, unless a patch addresses a critical issue. Critical issues are defined as the following: 1) Security Fixes 2) Fixes for bugs introduced in 4.3.3X releases 3) Fixes for bugs that break backwards compatibility with older versions. Ilia -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] PHP 4.3.3RC3 Released
PHP 4.3.3RC3 was just released, hopefully this will be the final release candidate prior to the final release. Please test this release as much possible so that any new/critical bugs maybe uncovered and resolved before the final. If you do find such bugs (hopefully you won't) be sure to label them as RC3 bugs. I would like to ask that all developers refrain from making commits to the 4_3 tree until 4.3.3 final is released, unless a patch addresses a critical issue. Critical issues are defined as the following: 1) Security Fixes 2) Fixes for bugs introduced in 4.3.3X releases 3) Fixes for bugs that break backwards compatibility with older versions. Ilia -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] strange thing about recode
Dear Sirs, anybody knows why recode(windows-1251..utf-8, F534A6C3-9174-11D5-903B-00D009784400) works very strange with PHP = 4.2.3 ? Cheers, Ilia Chipitsine -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Announcement: FUDforum 2.3.1 Released
FUDforum is a web based bulletin board software designed in PHP, utilizing a MySQL or PostgreSQL backend for data storage. The 2.3.1 release is the second stable release in the 2.3 branch, which introduces a number of new features as well as speed improvements. Below are some of the highlights of this release: * Mailing List NNTP support, allowing FUDforum to be used as a mailing list and newsgroup archive. This functionality also allows the admin to permit users to post message from the forum to the Mailing Lists and Newsgroups. * Additional translations were added, bringing up the number of i18n locales to 9, English, French, German, Spanish, Russian, Turkish, Polish, Chinese (traditional), Swedish * HTML cleanup, making the output HTML be fully HTML 4.01 compliant * The upgrade script can now upgrade PostgreSQL based forums as well as MySQL based forums. And the upgrade install scripts use zlib compression for the archive storage. * Other features, bug fixes and optimizations were added, these can be found in the changelog as they are to numerous to list here. Detailed ChangeLog: http://fud.prohost.org/CHANGELOG Download Page: http://fud.prohost.org/download.php Ilia Alshanetsky FUDforum Core Developer [EMAIL PROTECTED] -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] SESSION Security
If a person 'somehow' gains read access to the directory where the sessions are stored on your server, then yes it is possible for them to get the session id. Ilia On August 14, 2002 06:41 pm, Sascha Braun wrote: Is it possible that someone from outside can read the session stored on my webserver for getting unencrypted password and usernames? Schura -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] SESSION Security
On August 14, 2002 07:03 pm, Sascha Braun wrote: So, if somebody gets an ftp account somehow, he will be able to get session vars via a system() command? If their FTP client allows them to go into the directory where session ids are stored, then that user will be able to see current session ids. On most servers FTP clients are setup to only allow user access to their own home directory. Ilia - Original Message - From: Ilia A. [EMAIL PROTECTED] To: Sascha Braun [EMAIL PROTECTED]; PHP Mailingliste [EMAIL PROTECTED] Sent: Thursday, August 15, 2002 1:27 AM Subject: Re: [PHP] SESSION Security If a person 'somehow' gains read access to the directory where the sessions are stored on your server, then yes it is possible for them to get the session id. Ilia On August 14, 2002 06:41 pm, Sascha Braun wrote: Is it possible that someone from outside can read the session stored on my webserver for getting unencrypted password and usernames? Schura -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] SESSION Security
On August 14, 2002 07:12 pm, Sascha Braun wrote: So, the system() command allows a user only to start services in his own home direktory? Uhm... I am a little confused, how does system() command relate to FTP access? Ilia - Original Message - From: Ilia A. [EMAIL PROTECTED] To: Sascha Braun [EMAIL PROTECTED]; PHP Mailingliste [EMAIL PROTECTED] Sent: Thursday, August 15, 2002 1:36 AM Subject: Re: [PHP] SESSION Security On August 14, 2002 07:03 pm, Sascha Braun wrote: So, if somebody gets an ftp account somehow, he will be able to get session vars via a system() command? If their FTP client allows them to go into the directory where session ids are stored, then that user will be able to see current session ids. On most servers FTP clients are setup to only allow user access to their own home directory. Ilia - Original Message - From: Ilia A. [EMAIL PROTECTED] To: Sascha Braun [EMAIL PROTECTED]; PHP Mailingliste [EMAIL PROTECTED] Sent: Thursday, August 15, 2002 1:27 AM Subject: Re: [PHP] SESSION Security If a person 'somehow' gains read access to the directory where the sessions are stored on your server, then yes it is possible for them to get the session id. Ilia On August 14, 2002 06:41 pm, Sascha Braun wrote: Is it possible that someone from outside can read the session stored on my webserver for getting unencrypted password and usernames? Schura -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] sucking news out of the usenet
Andy,
I've recently written an newsgroup (NNTP) gateway between FUDforum and
newsgroup, which allows read/write data sharing between the two. The solution
for tracking down the reply to is done via 2 headers X-Reply-To or
In-Reply-To or most commonly References headers. There are a number of mail
clients that break the convention and send no such data, in which case you
need to do match replies based on subject. The latter occurs only very rarely
and in most cases you have a header with a unique ID against which you can
match messages.
--
Ilia Alshanetsky
[EMAIL PROTECTED]
http://fud.prohost.org/forum/
On August 8, 2002 04:10 pm, andy wrote:
Hi guys,
I am trying to build a usenet gateway which is collecting usenet posts and
puts them into a phpbb forum. Same other way around. So I did read an
excelent article on that published by Armel Fauveau at:
http://www.phpbuilder.com/columns/armel20010427.php3?page=1 (this is where
the code underneath is from. So getting the articles works.
My problem is how to glue all the articles together which are relies. I am
sure there is a way to find out which reply belongs to a post. I would like
to feed the phpbb database with it.
This is an example of an article including the header:
Newsgroups: php.general Path: news.php.net Xref: news.php.net
php.general:111709 Return-Path: Mailing-List: contact
[EMAIL PROTECTED]; run by ezmlm Delivered-To: mailing list
[EMAIL PROTECTED] Received: (qmail 81897 invoked by uid 1007); 8
Aug 2002 18:28:33 - Message-ID:
[EMAIL PROTECTED] To: [EMAIL PROTECTED]
Reply-To: sebastian Date: Thu, 8 Aug 2002 20:27:21 +0200 Lines: 11
X-Priority: 3 X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2600. X-MimeOLE: Produced
By Microsoft MimeOLE V6.00.2600. X-Posted-By: 141.44.162.176 Subject:
streaming mp3-audio??? From: [EMAIL PROTECTED] (Sebastian) hi @ all!
i´m looking for an algorithm or class to stream mp3-audiofiles, such as
easy as it can be. i found nothing on php.net and downloaded some
phpscripts from hotscripts and sourceforge but they were all very cryptical
and bad documentated. please help me, many thanks sebastian .
Lots of text.. puhh! I hope this is somehow possible. Maybe one of you guys
has a good idea on that. You can just cut and past the code underneath and
try it out by yourself.
Thanx for any help on that.
Andy
-
http://www.OZforum.info
Australia Information Forum
?php
# http://www.phpbuilder.com/columns/armel20010427.php3?page=3
$cfgServer= news.php.net;
$cfgPort= 119;
$cfgTimeOut= 10;
// open a socket
if(!$cfgTimeOut)
// without timeout
$usenet_handle = fsockopen($cfgServer, $cfgPort);
else
// with timeout
$usenet_handle = fsockopen($cfgServer, $cfgPort, $errno, $errstr,
$cfgTimeOut);
if(!$usenet_handle) {
echo Connexion failed\n;
exit();
}
else {
echo Connected\n;
$tmp = fgets($usenet_handle, 1024);
}
###
# page 2
//$cfgUser= xx;
//$cfgPasswd= yy;
$cfgNewsGroup= php.general;
// identification required on private server
if($cfgUser) {
fputs($usenet_handle, AUTHINFO USER .$cfgUser.\n);
$tmp = fgets($usenet_handle, 1024);
fputs($usenet_handle, AUTHINFO PASS .$cfgPasswd.\n);
$tmp = fgets($usenet_handle, 1024);
// check error
if($tmp != 281 Ok\r\n) {
echo 502 Authentication error\n;
exit();
}
}
// select newsgroup
fputs($usenet_handle, GROUP .$cfgNewsGroup.\n);
$tmp = fgets($usenet_handle, 1024);
if($tmp == 480 Authentication required for command\r\n) {
echo $tmp\n;
exit();
}
$info = split( , $tmp);
$first = $info[2];
$last = $info[3];
print First : $first\nbr;
print Last : $last\nbr;
###
# page 3
$cfgLimit= 10;
// upload last articles
$boucle=$last-$cfgLimit;
while ($boucle = $last) {
set_time_limit(0);
fputs($usenet_handle, ARTICLE $boucle\n);
#fputs($usenet_handle, BODY $boucle\n);
$article=;
$tmp = fgets($usenet_handle, 4096);
if(substr($tmp,0,3) != 220 AND substr($tmp,0,3) != 222) {
echo +--+\nbr;
echo Error on article $boucle\nbr;
echo +--+\nbr;
}
else {
while($tmp!=.\r\n) {
$tmp = fgets($usenet_handle, 4096);
$article = $article.$tmp;
}
echo +--+\nbr;
echo Article $boucle\nbr;
echo +--+\nbr;
echo $article\nbr;
}
$boucle++;
}
// close connexion
fclose($usenet_handle);
?
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Re: My SQL speed.
On August 3, 2002 12:54 am, Jason Stechschulte wrote: On Sat, Aug 03, 2002 at 01:49:10AM -0300, Manuel Lemos wrote: Google has 1 billion pages and qurys in a few milliseconds... Real search engines do not use SQL databases. What do search engines use? Is there something out there that explains how they work? Generally search egines use various hash algorithms to store their data, such as B-trees, Hash Tables, etc... Even that, is not enough when dealing with an extremely large dataset, in which case expensive hardware is used to provide the necessary IO capacity to allow for fast look ups. If you are trully interested in how search engines do this, there are plenty of articles describing Google's setup in terms of hardware. As far as fetching data from large MySQL databases it is not impossible or slow as some people claim. I have a 4 million record database in MySQL that is routinely accessed and most queries on that table are completed in 0.01-0.03 seconds, speed mostly depending on the number of rows retrieved. Keep in mind that your system and database configuration will play a very large role in regard to performance once you go beyond a certain amount of data. -- Ilia Alshanetsky [EMAIL PROTECTED] http://fud.prohost.org/forum/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] PHP Security Advisory: Vulnerability in PHP versions 4.2.0 and4.2.1
On July 22, 2002 10:12 am, 1LT John W. Holmes wrote: [snip] PHP Security Advisory: Vulnerability in PHP versions 4.2.0 and 4.2.1 [/snip] Looks like everyone will be using the new super globals, now... :) Well, I guess I'm still assuming that in a perfect world, people will upgrade because of security issues... ---John Holmes... As the Advisory suggests, the security fault affects only the 2 latest versions of PHP, all the people running older PHPs are not affected, so unless you've had the very latest stuff running this won't affect you and there will be no need to upgrade. If anything this will only convince people looking for 'stable' PHP to wait even longer before upgrading their releases because of potential bugs such as this one creeping up in 'new' releases. Ilia -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] Announcement: FUDforum 2.2.2 Released
A major upgrade of the 2.2X FUDforum with many bug fixes and a number of new features. The official announcement can be found here: http://fud.prohost.org/forum/index.php?t=msgth=724 Detailed ChangeLog: http://fud.prohost.org/CHANGELOG Download Page: http://fud.prohost.org/download.php Ilia Alshanetsky FUDforum Core Developer [EMAIL PROTECTED] -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Announcement: FUDforum 2.2.2 Released
Oops... This is what I get for making a release before finishing the upgrade of the support forum, heh.. Thanks for letting me know about the problem, it has been resolved. Ilia On July 12, 2002 09:07 am, Jeff Lewis wrote: Tried going to the official announcement and got this: query failed: %( SELECT fud_forum.id, fud_forum.name, fud_cat.name AS cat_name, fud_cat.id AS cat_id, fud_msg.post_stamp AS msg_post_stamp FROM fud_cat INNER JOIN fud_forum ON fud_cat.id=fud_forum.cat_id LEFT JOIN fud_msg ON fud_forum.last_post_id=fud_msg.id WHERE fud_forum.id IN (,,,) ORDER BY fud_cat.view_order, fud_forum.view_order )% because %( You have an error in your SQL syntax near ',,) ORDER BY fud_cat.view_order, fud_forum.view_order ' at line 14 )% - Original Message - From: Ilia A. [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, July 12, 2002 9:23 AM Subject: [PHP] Announcement: FUDforum 2.2.2 Released A major upgrade of the 2.2X FUDforum with many bug fixes and a number of new features. The official announcement can be found here: http://fud.prohost.org/forum/index.php?t=msgth=724 Detailed ChangeLog: http://fud.prohost.org/CHANGELOG Download Page: http://fud.prohost.org/download.php Ilia Alshanetsky FUDforum Core Developer [EMAIL PROTECTED] -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Survey: MySQL vs PostgreSQL for PHP
On July 5, 2002 07:54 pm, Pete James wrote: Ilia A. wrote: The biggest annoyance I've come across is the fact that while using PostgreSQL with PHP is that when you fetch a row you must specify the number of the result, while in MySQL, that is handled internally by PHP for you. This means that your PHP scripts must track the row numbers themselves. This is not so... see pg_fetch_array. Since PHP 4.1.0, you no longer need the row number. It may work without, but according to the manual on php.net pg_fetch_array pg_fetch_object pg_fetch_row REQUIRE a row number. If that is no longer the case as you claim, perphaps someone needs to inform the developers and have them update the documentation. Now we come to the actual database speed itself. In this regard in most applications MySQL is MUCH faster probably because it has to do allot less work then PostgreSQL does. For example, lets analyze the most common action performed in a database system, a SELECT. When you do a select in MySQL, MySQL internally locks the table for the duration of the select. PostgreSQL on the other hand does a row level lock, internally, for every row you select. Is this really what you want? Doesn't this mean that PostgreSQL would be more efficient for larger user volumes? Locking an entire table isn't usually a good thing. Not necessarily, locking entire table has its pluses and minuses. The BIG minues is that while the entire table is locked you cannot do anything until the lock is released. On the other hand, it is MUCH faster to lock the entire table then the inidividual rows. PostgreSQL would be more effecient on a system that does lots of locking, but on a system without or few locks MySQL will beat it hands down. Ilia FUDforum Core Developer [EMAIL PROTECTED] -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Survey: MySQL vs PostgreSQL for PHP
I've recently had the 'pleasure' of porting a large MySQL application to support PostgreSQL, through that experience I've gained some insight into the differences between the two as well as how they are supported by PHP. First allow me to point out that MySQL support in PHP is a lot more mature then PostgreSQL support. This can be seen through several factors, such as larger number of functions, which do more as well as the fact that only recently (php 4.2.0) did PostgreSQL interface functions got renamed to a more standard convention that MySQL functions already used since 3.0 days. For example, while using MySQL you can easily get properties of a field by simply using the mysql_field_type() function, pg_* has nothing similar. The only alternative is to run a query on the PostgreSQL internal tables, which contain the properties of a column. The biggest annoyance I've come across is the fact that while using PostgreSQL with PHP is that when you fetch a row you must specify the number of the result, while in MySQL, that is handled internally by PHP for you. This means that your PHP scripts must track the row numbers themselves. PostgreSQL also has a number of things that it lacks when compared to MySQL. For example, it does not support unsigned integers, which forces you to use int8 to store timestamps, which will eventually reach 4.2 billion. In case you are wondering what is the big deal, int4 or int8, besides 4 more bytes of memory, well on x86 processors, which are 32 bit, 32 bit numbers are handled faster then their 64 bit counterparts. Now a days the performance drop as the result is quite small, but in the end everything adds up. PostgreSQL also does not support ENUM type, although you can port your ENUMs to PostgreSQL by using CONSTANTS. Now we come to the actual database speed itself. In this regard in most applications MySQL is MUCH faster probably because it has to do allot less work then PostgreSQL does. For example, lets analyze the most common action performed in a database system, a SELECT. When you do a select in MySQL, MySQL internally locks the table for the duration of the select. PostgreSQL on the other hand does a row level lock, internally, for every row you select. PostgreSQL also does not optimize count(),max() and min() queries, which in MySQL are instant regardless of the table size since they are cached internally. PostgreSQL on the other hand needs to go every single row in the table. However, I should note that PostgreSQL developers I spoke to, told me that they plan to add this kind of functionality in the next release of PostgreSQL, whenever that happens. PostgreSQL also syncs any inserted or updated to disk right away to ensure that you don't loose any data should the computer crash on the other hand MySQL keeps memory buffers and will often not sync to disk right away to avoid disk IO. PostgreSQL offers greater data security, which would be important in a shopping cart, however it looses much speed in this approach compared to MySQL's approach which is ideal for programs where fast inserts are critical, like a web counter for example. PostgreSQL does have a number of advantages that should not be overlooked and are certainly very important. Such as views, that allow you to create 'virtual tables' who's data is a combination of a complex join, which simplifies your selects to select * from table1_table2_view; PostgreSQL supports triggers and stored procedures which can be coded in perl, python, plsql and C. These triggers and functions can clean up not to mention speed up you code by moving various database code from PHP to PostgreSQL. PostgreSQL also supports various table locking implementations, which include row level locking. The benefit of using it is what while a certain row in a table is locked other users who do not require this row can still read from a table. In MySQL once a table is locked to write, no other user can read from the very same table until the lock is released. This in particular makes PostgreSQL much more scalable then MySQL. Unlike MySQL, PostgreSQL supports transactions with rollbacks, which allow you to actually make a bunch of queries and then with a single commit apply them to the database. The cool thing is that you can actually undo bad query by canceling the transaction. Bottom line is that both MySQL and PostgreSQL have their 'markets'. IMHO in most cases MySQL is a simpler, faster and easier solution to use. However, if you require 100% data integrity and are dealing with sensitive data and in those case probably can spend a little more or hardware PostgreSQL should be your tool of choice. Ilia FUDforum Core Developer [EMAIL PROTECTED] On July 5, 2002 04:59 pm, Lazor, Ed wrote: How many here feel PostgreSQL has surpassed MySQL as the better backend for PHP? This would be based on performance (speed, scalability, etc.) and features. -Ed
[PHP] FUDforum 2.0 Stable Released
FUDforum 2.0 is a web forum released under the GPL license, written in PHP4 utilizing a MySQL database backend. The forum is completely customizable via a templating system, which is compiled for optimal performance. The templating system also has integrated i18n support, which allows the forum to be used in other languages, at this time there are 5 different languages to, which translations are available in the standard distribution and more will be available soon. The spell checker integrated into the forum, which utilizes pspell library also has multi-lingual support, thus permitting even the non English speakers to spell check their messages. FUDforum 2.0 also includes a powerful user group management system, that allows fine grained control over the users of the forum, for the administrator as well as the group manager(s) assigned by the administrator. In addition to these features, the forum contains all the other features you may have come to expect from a web forum, such as the ability to attach files to messages, include polls, private messaging system, FUDcode, which allows the user to style their text without the need for HTML, thread forum subscriptions with both e-mail ICQ notification, buddy and ignore lists, a full text search and many more. Despite all these features, FUDforum is extremely fast and scales extremely well, by using MySQL indexes and table views implemented in PHP to retrieve the data in the most expedient manner possible. The result, is that most forum pages take ~0.01-0.02 seconds to generate on most computers, even while the forum is under a heavy load. The forum, by default is setup with very secure file permissions, that are designed in such a way that given a reasonably well setup web server, your forum's data will be safe against hackers. You can download FUDforum from http://fud.prohost.org/download.php and if you have any questions, there is a support forum at http://fud.prohost.org/forum/, where you can get answers to your questions and concerns about the forum. Ilia Alshanetsky [EMAIL PROTECTED] FUDforum Core Developer -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] FUDforum 2.0 Stable Released
Jeff, You are absolutely correct that there are many forum software choices out there however, not are identical or even similar. First there is the design language choice, there are many forums that are written in PHP, but there are no less forums written in PERL, ASP and ColdFusion because not all servers support PHP. Then there is the distinction between open closed sources forums like FUDforum phpBB which are open source and Vbulletin PHPthreads which are closed source. Personally, I have decided to write my own forum because after looking at the 2 prevailing open source forums Phorum phpBB2 I was not impressed by their code to put it lightly. Thus, I decided to make a clean break and write something, which in my option is better. In the end, having more choice is hardly a bad thing, no? Ilia On June 10, 2002 01:51 pm, Jeff Lewis wrote: Is it just me or the forum area totally overflowing with choices? I often wonder why people don't pool talents and work on really great products, instead people break off and make their own system - quite unusual... Jeff - Original Message - From: Ilia A. [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, June 10, 2002 1:54 PM Subject: [PHP] FUDforum 2.0 Stable Released FUDforum 2.0 is a web forum released under the GPL license, written in PHP4 utilizing a MySQL database backend. The forum is completely customizable via a templating system, which is compiled for optimal performance. The templating system also has integrated i18n support, which allows the forum to be used in other languages, at this time there are 5 different languages to, which translations are available in the standard distribution and more will be available soon. The spell checker integrated into the forum, which utilizes pspell library also has multi-lingual support, thus permitting even the non English speakers to spell check their messages. FUDforum 2.0 also includes a powerful user group management system, that allows fine grained control over the users of the forum, for the administrator as well as the group manager(s) assigned by the administrator. In addition to these features, the forum contains all the other features you may have come to expect from a web forum, such as the ability to attach files to messages, include polls, private messaging system, FUDcode, which allows the user to style their text without the need for HTML, thread forum subscriptions with both e-mail ICQ notification, buddy and ignore lists, a full text search and many more. Despite all these features, FUDforum is extremely fast and scales extremely well, by using MySQL indexes and table views implemented in PHP to retrieve the data in the most expedient manner possible. The result, is that most forum pages take ~0.01-0.02 seconds to generate on most computers, even while the forum is under a heavy load. The forum, by default is setup with very secure file permissions, that are designed in such a way that given a reasonably well setup web server, your forum's data will be safe against hackers. You can download FUDforum from http://fud.prohost.org/download.php and if you have any questions, there is a support forum at http://fud.prohost.org/forum/, where you can get answers to your questions and concerns about the forum. Ilia Alshanetsky [EMAIL PROTECTED] FUDforum Core Developer -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Speed comparison of PHP vs. PERL (not conclusive)
Does this mean that running a comparison benchmarks between PHP and any other
language would in many cases show PHP to be slower simply because it's
looping code is slow? Unless, timing is done on a speed of PHP being able to
spew out webpages via the webserver with a webserver benchmark tool such as
apachebench?
Wouldn't that cause any benchmarks trying to guage the speed of PHP virtually
meaningless because of the 'loop' overhead, which is clearly great enough to
make PHP way slower in comparison to Perl for example?
Ilia
On May 31, 2002 05:38 pm, Rasmus Lerdorf wrote:
Not very surprising. Perl's looping code has always ben faster than
PHP's. Highly iterative loops is really not what PHP is geared for. You
are not going to write a Mandelbrot algorithm in PHP. You write it in C
and drop in a super-quick extension into PHP and call mandelbrot().
-Rasmus
On Fri, 31 May 2002, Daniel Grace wrote:
This all started in a little debate between me and a friend of mine who I
think is as much a PERL zealot as I am a PHP zealot (I was briefly
pondering the idea of a Win32 API extension for PHP), and the results
were rather surprising -- to me, at least..
It all started when I asked him what PERL had that PHP didn't in terms of
language (not taking community, modules, etc. into an account). We both
believed that the two would be very similiar in speed -- he thought PERL
would be a little faster but not enough to be noticeable. For the first
test, I went with a program that computed prime numbers between 2 and
1, using no form of caching or anything like that. I gave him the PHP
source with the task of writing something in PERL as close to the
original PHP source as possible. The results:
(note: I didn't know if PERL had PHP's continue(2), hence why I used the
slightly less efficient method here:)
prime.php:
#!/usr/bin/php -q
?php
echo 2\n;
for($check = 3 ; $check 1 ; $check += 2) {
$prime = 1;
$half = (int) $check / 2;
for($against = 2 ; $against = $half ; ++$against) {
if(!($check % $against)) {
$prime = 0;
break;
}
}
if($prime) echo $check\n;
}
prime.pl:
#!/usr/bin/perl
# print 2\n;
my $num;
for ($num = 3; $num 1; $num+=2)
{
my $prime = 1;
for $check ( 2 .. int($num/2) )
{
if ($num % $check == 0)
{
$prime = 0;
last;
}
}
#print $num\n if $prime;
}
The test machine is an AMD Duron 700 MHz using an a-bit KT7A motherboard
with 256 MB of PC100 SDRAM. uname -a reports Linux ulysses.venura.net
2.4.17-ulysses1 #1 Sat Dec 29 14:44:46 PST 2001 i686 unknown, PHP 4.2.1
was configured with --enable-inline-optimization --prefix=[somepath],
PERL 5.6.1 was configured with -O3 (among other options) (PHP compiles
with -g -O2 with no 'easy' (at-configure-time) way to change that, to my
knowledge).
Both programs were ran once normally to verify they actually generated
prime numbers, and then the bash time command was used to time them,
piping their output to /dev/null to prevent that from being a factor. I
re-ran the tests a few times with results consistently similiar to those
listed here:
The results:
[dewin@ulysses profiling]$ time ./prime.php /dev/null
real0m14.465s
user0m8.610s
sys 0m0.070s
[dewin@ulysses profiling]$ time ./prime.pl /dev/null
real0m5.302s
user0m3.180s
sys 0m0.000s
A second system, with PHP compiled the same way and a PERL 5.6.1 binary
distributed by Red Hat, 1.2 ghz with 442 MB of RAM:
[root@mrr-016 law]# time ./prime.pl /dev/null
real 0m2.078s
user 0m2.040s
sys 0m0.010s
[root@mrr-016 law]# time ./prime.php /dev/null
real 0m5.512s
user 0m5.430s
sys 0m0.010s
Comments? I was expecting the numbers to be very similiar -- rather
shocked that the PERL ended up being about 2.5x as fast as PHP was.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Speed comparison of PHP vs. PERL (not conclusive)
I agree that in most cases it makes more sence at seing the webpages per
second benchmark rather then a timing of some artibtrary benchmarks that for
example seeing how long it take to pick prime numbers. Since in the end it
matters how quickly you can get the data to the user, in case of perl
programs there would be the overhead of spawning a cgi program, (unless
mod_perl is used) which would negate much of the speed improvment gained by
Perl.
All that said, loops are very very common in PHP, and are used with virtually
in any script that uses a database wether it be SQL or flatfile to loop
through the result set.
Since this appears to be a known performance issue, perphaps it is something
the PHP Development team could consider improving for PHP 5.0
Ilia
On May 31, 2002 06:00 pm, Rasmus Lerdorf wrote:
Sure, you could put it that way. When benchmarking something you really
should benchmark stuff that you actually care about. Benchmark PHP
spewing out a web page after making a couple of SQL queries, for example.
That's typical usage, so that is what you should benchmark. Very few PHP
scripts are going to loop a couple of hundred thousand times to do
something.
-Rasmus
On Fri, 31 May 2002, Ilia A. wrote:
Does this mean that running a comparison benchmarks between PHP and any
other language would in many cases show PHP to be slower simply because
it's looping code is slow? Unless, timing is done on a speed of PHP being
able to spew out webpages via the webserver with a webserver benchmark
tool such as apachebench?
Wouldn't that cause any benchmarks trying to guage the speed of PHP
virtually meaningless because of the 'loop' overhead, which is clearly
great enough to make PHP way slower in comparison to Perl for example?
Ilia
On May 31, 2002 05:38 pm, Rasmus Lerdorf wrote:
Not very surprising. Perl's looping code has always ben faster than
PHP's. Highly iterative loops is really not what PHP is geared for.
You are not going to write a Mandelbrot algorithm in PHP. You write it
in C and drop in a super-quick extension into PHP and call
mandelbrot().
-Rasmus
On Fri, 31 May 2002, Daniel Grace wrote:
This all started in a little debate between me and a friend of mine
who I think is as much a PERL zealot as I am a PHP zealot (I was
briefly pondering the idea of a Win32 API extension for PHP), and the
results were rather surprising -- to me, at least..
It all started when I asked him what PERL had that PHP didn't in
terms of language (not taking community, modules, etc. into an
account). We both believed that the two would be very similiar in
speed -- he thought PERL would be a little faster but not enough to
be noticeable. For the first test, I went with a program that
computed prime numbers between 2 and 1, using no form of caching
or anything like that. I gave him the PHP source with the task of
writing something in PERL as close to the original PHP source as
possible. The results:
(note: I didn't know if PERL had PHP's continue(2), hence why I used
the slightly less efficient method here:)
prime.php:
#!/usr/bin/php -q
?php
echo 2\n;
for($check = 3 ; $check 1 ; $check += 2) {
$prime = 1;
$half = (int) $check / 2;
for($against = 2 ; $against = $half ; ++$against) {
if(!($check % $against)) {
$prime = 0;
break;
}
}
if($prime) echo $check\n;
}
prime.pl:
#!/usr/bin/perl
# print 2\n;
my $num;
for ($num = 3; $num 1; $num+=2)
{
my $prime = 1;
for $check ( 2 .. int($num/2) )
{
if ($num % $check == 0)
{
$prime = 0;
last;
}
}
#print $num\n if $prime;
}
The test machine is an AMD Duron 700 MHz using an a-bit KT7A
motherboard with 256 MB of PC100 SDRAM. uname -a reports Linux
ulysses.venura.net 2.4.17-ulysses1 #1 Sat Dec 29 14:44:46 PST 2001
i686 unknown, PHP 4.2.1 was configured with
--enable-inline-optimization --prefix=[somepath], PERL 5.6.1 was
configured with -O3 (among other options) (PHP compiles with -g -O2
with no 'easy' (at-configure-time) way to change that, to my
knowledge).
Both programs were ran once normally to verify they actually
generated prime numbers, and then the bash time command was used to
time them, piping their output to /dev/null to prevent that from
being a factor. I re-ran the tests a few times with results
consistently similiar to those listed here:
The results:
[dewin@ulysses profiling]$ time ./prime.php /dev/null
real0m14.465s
user
Re: [PHP] PHP compared to JSP
Caching is not going against PHP as long as whenever the file is changed of the 1st access it would be cached, rather then caching php scripts based on some arbitrary timer. Ideally the caching script would on the 1st access of the script convert the script to binary code which can then be executed right away without needing to pass through an interpreter. Just like you would run a compiled C program. I suspect such caching solution would greatly boost the speed of any PHP page. Unfortunately, as far as I know no current PHP caching solution does this. Ilia On May 4, 2002 12:18 pm, Pag wrote: Does PHP compile : NO Does the user loading same page for 2nd time gets better response : YES it can if caching is provided On a side not..isnt caching a bit like going against why PHP was built in the first place? I mean, information may get a bit out of date if we get a page on the cache instead of getting it fresh from the server. Pag -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] i18n translation of PHP based forum
Hello, I am one of the core developers of FUDforum, which is PHP based forum released under the GPL licence. The upcomming release of FUDforum 2.0 will contain i18n support and I am looking for people who would be willing to help translate the forum to other languages. If you want to help with the translations, please contact me at [EMAIL PROTECTED] Thanks. Ilia FUDforum Developer http://fud.prohost.org/forum/ [EMAIL PROTECTED] -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Phpfx, what is it?
You can also try FUDforum (http://fud.prohost.org/forum/) Ilia On March 20, 2002 07:11 pm, Chuck \PUP\ Payne wrote: Hi, I was sourgeforge.net looking at the PHP stuff, I saw something call phpfx, but it not clear what it is or what it does. Has anyone mess with it? Also I am looking for a php program that was written so that you can do a BBS, I wanted to use Ultimate Bulletin Board, but they no longer support the freeware verision, you have to pay almost $500 for it. The verision I have the date is not Y2K, so the dates come out 19100. So I need to replace the BBS, it was written with perl and I like to have something well you guys know. One last question for now. Is there a site that explain how to do list in php with colors, I want to add color to my lists, when I do thinks now there are so boring, with just white. Thanks a head of time...By the way | Chuck Payne | | Magi Design and Support | | www.magidesign.com | | [EMAIL PROTECTED] | BeOS, Macintosh 68K, Classic, and OS X, Linux Support. Web Design you can afford. Never be bullied into silence. Never allow yourself to be made a victim. Accept no one's definition of your life; define yourself.- Harvey Fierstein -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP] FUDforum - PHP Web Forum (GPL)
The work on FUDforum has finally been completed, so I thought to let the PHP users and developers know about it since they may be interested in this project. It has finally reached the stage where I feel it is mostly bug free and is ready for its debut. You can download FUDforum tar ball from http://fud.prohost.org/download.php, and should be pretty easy to install using the provided installation script. I've also made a demo forum, which you play with, both as user and as admin here, http://fud.prohost.org/dfrm/ Here is just a quick list of features that I can recall of the top of my head: Core features. * Ability to use FUDcode, HTML or Plain Text inside posts, configurable by the admin * Administrator definable ranks for the users bases on number of posts as well as assign an unlimited number of custom tags to individual users * Built in spell checker (using the pspell library) * Private Messaging system, with post tracking buddy lists * Ignore list, allows forum members to ignore posts made by other users. * CSS control panel, allowing the admin to easily customize the forum's look feel * Optional Threaded View (by default standard flat view is used, like UBB,VBulletin, phpBB, etc...) * Customizable Find and Replace system, which fully supports both perl regexp (preg) and php regexp (ereg) and even str_replace for extremely fast simple replaces The usual features you may have come to expect from forum software * Posting/Replying and editing of topics and messages * Sticky/Announcement messages which stay on top of the forum until they reach their expire date * Custom Avatars upload with administrator approval and automatic scaling (if ImageMagick's mogrify utility is installed) * Emoticon (smilies) Support, with an easy to use admin control panel, which allows the admin to add/remove and edit smilies * Post notification system, which can send notifications via Email ICQ * Unlimited number of forum moderators * Hidden, Private, Moderated and Password protected forums * Moderation queue, in moderated forums all unapproved messages can be viewed by the moderator and approved or deleted on the spot. * Email confirmation of registered users (can't post until the email address is confirmed) * Specialized HTML like FUDcode that allows styling of messages, the advantage of FUDcode over HTML is that FUDcode will never break layout. * Banning of users by their username and/or IP or IP Mask, Email address filter or Login name filter (full regexp support) * Multiple file uploads per post (configurable by the administrator for each forum) * File extension control, allowing/disallowing certain file extensions * Fully customizable header footer which can support PHP code * Language filter (full regexp), which allows the admin to replace certain offensive words * Full support for Children's Online Privacy Protection Act (COPPA) * Automatic lost password retrieval * Search Engine * MD5 passwords (128 Bit encryption) * Thread locking by Administrators Moderators * Easy to use installation PHP or Shell script * Unread Posts Tracking, you can automatically see which posts you have not yet read * Extensive message filtering, by date, read/unread, forum, thread, reply status * Message reporting, allows visitors to report inappropriate messages to the Administrator * Robust MySQL back-end, with a virtually unlimited number of messages (up to 2^32 messages) * Cookie based tracking system backed by Sessions in the event the user cannot use cookies. * Polls if allowed, users can create on or more polls on their messages * Forum Thread subscription system with an easy to use control panel. Allows users to subscribe unsubscribe from forums threads. * I-SPY system, if enabled it allows forum members to see what the other users on the forum are doing. There are more, but I won't bore you more so then necessary, I am sure you'll find'em out if you decide to try this thing out. -- Ilia Alshanetsky [EMAIL PROTECTED] FUDforum - http://fud.prohost.org/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
