Re: [PHP] Re: PHP Security Advisory: Vulnerability in PHP versions 4.2.0

2002-07-24 Thread Rick Widmer
At 10:22 AM 7/24/02 -0400, Scott Fletcher wrote: >It work very nicely The whole process take 30 to 45 minutes for just >one server. I wonder how does someone did 12 computers in 10 minutes. >Cool! For me the key to upgrading many servers is to compile once then copy the resulting files to

Re: [PHP] Re: PHP Security Advisory: Vulnerability in PHP versions 4.2.0

2002-07-24 Thread Jason Wong
On Wednesday 24 July 2002 22:22, Scott Fletcher wrote: > It work very nicely The whole process take 30 to 45 minutes for just > one server. You've got a slow computer and/or you type too slow ;-) > I wonder how does someone did 12 computers in 10 minutes. > Cool! For me it was a case of

Re: [PHP] Re: PHP Security Advisory: Vulnerability in PHP versions 4.2.0

2002-07-24 Thread Scott Fletcher
38DA@hsus3">news:4B08FD7DB3CBD4119F560002A508C453015B38DA@hsus3... > > From: Scott Fletcher [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, July 23, 2002 12:43 PM > > To: [EMAIL PROTECTED] > > Subject: Re: [PHP] Re: PHP Security Advisory: Vulnerability > > in PHP versions 4.2.0 > > > >

Re: [PHP] Re: PHP Security Advisory: Vulnerability in PHP versions 4.2.0

2002-07-24 Thread Scott Fletcher
PROTECTED]] > > Sent: Tuesday, July 23, 2002 12:43 PM > > To: [EMAIL PROTECTED] > > Subject: Re: [PHP] Re: PHP Security Advisory: Vulnerability > > in PHP versions 4.2.0 > > > > > > I don't know how to appy patches to the PHP software. I just fin

[PHP] Re: PHP Security Advisory: Vulnerability in PHP versions 4.2.0

2002-07-24 Thread Ian Ball
Hmmm, interesting I didn't know about this and didn't see it in the docs. So now I know for my next upgrade. Anyway, my upgrade is in, and through the mails it should be clear to those who thought how terribly difficult and time consuming it is/was to do the upgrades that it was in fact

RE: [PHP] Re: PHP Security Advisory: Vulnerability in PHP versions 4.2.0

2002-07-23 Thread Andrew Chase
If all you're doing is applying the patch (not adding/removing any extensions), you should be able to use ./config.nice which will use all of the configuration commands from your last compile (This is an extremely handy thing if your GD/Freetype setup was particularly ornery the first time aroun

[PHP] Re: PHP Security Advisory: Vulnerability in PHP versions 4.2.0

2002-07-23 Thread Ricky Dhatt
"Ian Ball" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > patch -p0 < php-4.2.1-to-4.2.2.patch > cd php-4.2.1 > ./configure --with-mysql --with-apxs=/usr/local/apache/bin/apxs --with-ldap > make > make install > /usr/local/apache/bin/apachectl restart Hmm...

RE: [PHP] Re: PHP Security Advisory: Vulnerability in PHP versions 4.2.0

2002-07-23 Thread Matt Schroebel
> From: Scott Fletcher [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, July 23, 2002 12:43 PM > To: [EMAIL PROTECTED] > Subject: Re: [PHP] Re: PHP Security Advisory: Vulnerability > in PHP versions 4.2.0 > > > I don't know how to appy patches to the PHP software.

Re: [PHP] Re: PHP Security Advisory: Vulnerability in PHP versions 4.2.0

2002-07-23 Thread Scott Fletcher
Amended to this recent posting. Already started a new posting from scratch. "Scott Fletcher" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > I don't know how to appy patches to the PHP software. I just finish > upgrading the website to work with PHP 4.2.1 fro

Re: [PHP] Re: PHP Security Advisory: Vulnerability in PHP versions 4.2.0

2002-07-23 Thread Scott Fletcher
I don't know how to appy patches to the PHP software. I just finish upgrading the website to work with PHP 4.2.1 from PHP 4.0.6. And now this So, just patched it then configure openssl, mycrypt, curl, modssl then do the usual stuff for PHP then apache, right?? "Adam Alkins" <[EMAIL PROTECT

Re: [PHP] Re: PHP Security Advisory: Vulnerability in PHP versions 4.2.0

2002-07-22 Thread Adam Alkins
Any real programmer should know that almost nothing is bug free, even if you test it beyond your imagination. Something is always going to elude you and be found by someone experimenting down the road. For the widespread use of PHP, I'm rather impressed by the small amount of vunerabilities disco

[PHP] Re: PHP Security Advisory: Vulnerability in PHP versions 4.2.0

2002-07-22 Thread Ian Ball
[delete some flaming] Hehe, and I thought I had to go to USENET to see a flamewar. This is great, a flamewar delivered directly to my mailbox, it doesn't get better... Let me put my $0.02 in. Security holes happen, no matter what software you use. PHP and open source in general, unl

[PHP] Re: PHP Security Advisory: Vulnerability in PHP versions 4.2.0 and 4.2.1

2002-07-22 Thread Peter
Yes. Please post something to php.announce! Nothing ever gets announced in there anymore. "Steve Meyers" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Can you post this to php.announce as well? > > Marko Karppinen wrote: > > > > >PHP Security Advisory: V

Re: [PHP] Re: PHP Security Advisory: Vulnerability in PHP versions 4.2.0 and 4.2.1

2002-07-22 Thread Rouvas Stathis
Hi all, Just wanting to notify everyone that the link for the PHP.4.2.2 download is broken. -Stathis. -- Rouvas Stathis [EMAIL PROTECTED] http://www.di.uoa.gr/~rouvas -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

[PHP] Re: PHP Security Advisory: Vulnerability in PHP versions 4.2.0 and 4.2.1

2002-07-22 Thread Steve Meyers
Can you post this to php.announce as well? Marko Karppinen wrote: > >PHP Security Advisory: Vulnerability in PHP versions 4.2.0 and 4.2.1 > > > Issued on: July 22, 2002 > Software: PHP versions 4.2.0 and 4.2.1 > Platforms: All > > >The PHP Group has learned of a serious security vu