[PHP-DEV] phpinfo() output

Currently API Versions: PHP: 20020307 PHP Extension: 20020429 Zend Extension: 20020903 is rendered instead of API Versions: PHP: 20020307 PHP Extension: 20020429 Zend Extension: 20020903 -- Sebastian Bergmann http://sebastian-bergmann.d

Re: [PHP-DEV] patch to restrict database access for ext/pgsql

On Fri, Sep 27, 2002 at 10:50:08AM +0900, Yasuo Ohgaki wrote: > Ilia A. wrote: > >list think of this patch. I merely try to explain why I believe this > >particular patch is not appropriate for standard PHP distribution. > > It will be yet another safe_mode like feature. i.e. > it isn't secure a

Re: [PHP-DEV] patch to restrict database access for ext/pgsql

On Thu, Sep 26, 2002 at 09:00:17PM -0400, Ilia A. wrote: > It is not a job of the programming language to implement system, database > security. This is simply not done. If you want to secure your PostgreSQL more > so that you can with the current tools, the people you should be talking to > ar

Re: [PHP-DEV] patch to restrict database access for ext/pgsql

Ilia A. wrote: > list think of this patch. I merely try to explain why I believe this > particular patch is not appropriate for standard PHP distribution. It will be yet another safe_mode like feature. i.e. it isn't secure as it sounds. Users with a little knowledge can access backend with socke

Re: [PHP-DEV] patch to restrict database access for ext/pgsql

On Thu, Sep 26, 2002 at 09:31:44PM -0400, Ilia A. wrote: > > PHP is full of tweaks and hacks specifically to augment and make easier the > > job of the people using it. > > The only simular hack I can imagine you are referring to is safe_mode, which > is a very ugly thing that was only implement

Re: [PHP-DEV] patch to restrict database access for ext/pgsql

On September 26, 2002 08:48 pm, Jim Mercer wrote: > On Thu, Sep 26, 2002 at 09:00:17PM -0400, Ilia A. wrote: > > It is not a job of the programming language to implement system, database > > security. This is simply not done. If you want to secure your PostgreSQL > > more so that you can with the

Re: [PHP-DEV] patch to restrict database access for ext/pgsql

On Thu, Sep 26, 2002 at 08:01:29PM -0400, Dan Kalowsky wrote: > On Thursday, September 26, 2002, at 06:36 PM, Jon Parise wrote: > >Isn't it generally better (where "better" means more secure, > >efficient, and easily maintained) to handle database access control > >using PostgreSQL's native access

Re: [PHP-DEV] patch to restrict database access for ext/pgsql

On Thursday, September 26, 2002, at 06:36 PM, Jon Parise wrote: > Isn't it generally better (where "better" means more secure, > efficient, and easily maintained) to handle database access control > using PostgreSQL's native access mappings? > Yep. Thus why it was created :) >-

RE: [PHP-DEV] patch to restrict database access for ext/pgsql

From: Jon Parise > Isn't it generally better (where "better" means more secure, > efficient, and easily maintained) to handle database access > control using PostgreSQL's native access mappings? I would think so, and IMHO, that's where pgsql access control belongs, with pgsql. Regards Mike Ro

Re: [PHP-DEV] patch to restrict database access for ext/pgsql

On Thu, Sep 26, 2002 at 02:15:52PM -0400, Jim Mercer wrote: > this patch adds the config variable pgsql.allowed_dblist [snip] > although it can be accomplished by other means, setting the variable to a > value of ":" effectively locks the code out of pgsql. Isn't it generally better (where "

[PHP-DEV] Re: [PHP-CVS] cvs: php4 /ext/session session.c

Guys, _Please_ include bug fixes in NEWS entries (or separately commit them) so we've complete log. Browsing back the ChangeLog and finding missing treasures ain't that funny. ;) thanks, - Markus On Thu, Sep 26, 2002 at 06:12:27PM -, Ilia Alshanetsky w

[PHP-DEV] Re: open_basedir bug

It looks like this is the culprit: http://cvs.php.net/diff.php/php4/main/fopen_wrappers.c?r1=1.142&r2=1.142.2.1&ty=h But I don't know enough about this particular situation to decide what the best solution is. Rasmus: any ideas? (and does this affect HEAD?) --Wez. On 09/26/02, "Andrei Zmievsk

Re: [PHP-DEV] Latest cvs: error in mbstring

Did you ./buildconf and then re-run configure? --Wez. On 09/26/02, "Martin Jansen" <[EMAIL PROTECTED]> wrote: > The following error occurs when building latest CVS: > > ext/mbstring/mbstring.lo: In function `zif_mb_convert_case': > /home/martin/cvs/php/php4/ext/mbstring/mbstring.c:2499:

[PHP-DEV] Re: remote_addr

Anderson O Muniz wrote: > Hello, > > I need help I never programmed in php. :/ Then you're in the wrong place. This group is for the development of the PHP sourcecode itself, not a support forum. > What i am doing wrong? Everything, try php.general or read the manual from the beginning --

[PHP-DEV] Re: [PHP-CVS] cvs: php4 /ext/standard config.m4 css.c css.h info.c /main php_ini.c /sapi/aolserver aolserver.c /sapi/apache php_apache.c

Michael Mauch <[EMAIL PROTECTED]> wrote: > Colin Viebrock <[EMAIL PROTECTED]> wrote: >> [EMAIL PROTECTED] wrote: >>> "render nicely" is something else than "total unreadable" to me. Did you >>> have a look at it with Netscape Navigator 4? Please fix something for >>> it, as it's pretty horrible

[PHP-DEV] Latest cvs: error in mbstring

The following error occurs when building latest CVS: ext/mbstring/mbstring.lo: In function `zif_mb_convert_case': /home/martin/cvs/php/php4/ext/mbstring/mbstring.c:2499: undefined reference to `php_unicode_convert_case' collect2: ld returned 1 exit status make: *** [sapi/cli/p

Re: [PHP-DEV] 4.3.0

[EMAIL PROTECTED] wrote: >>> >>> Good News! >>> >> I so love that show. > Which show is that? Futurama. -- Sebastian Bergmann http://sebastian-bergmann.de/ http://phpOpenTracker.de/ Did I help you? Consider a gift: http://wishlist.sebastian-bergmann.de/ -- PHP Dev

Re: [PHP-DEV] 4.3.0

On Thu, 26 Sep 2002, Andrei Zmievski wrote: > On Thu, 26 Sep 2002, Sebastian Bergmann wrote: > > Andrei Zmievski wrote: > > > Once the critical bugs are fixed, I intend to branch the tree in > > > preparation for 4.3.0 cycle. > > > > > > Good News! > > > > I so love that show. Which

Re: [PHP-DEV] 4.3.0

On Thu, 26 Sep 2002, Sebastian Bergmann wrote: > Andrei Zmievski wrote: > > Once the critical bugs are fixed, I intend to branch the tree in > > preparation for 4.3.0 cycle. > > > Good News! > I so love that show. -Andrei http://www.gravitonic.com

Re: [PHP-DEV] 4.3.0

Andrei Zmievski wrote: > Once the critical bugs are fixed, I intend to branch the tree in > preparation for 4.3.0 cycle. Good News! -- Sebastian Bergmann http://sebastian-bergmann.de/ http://phpOpenTracker.de/ Did I help you? Consider a gift: http://wishlist.seb

Re: [PHP-DEV] 4.3.0

Andrei Zmievski wrote: >All, > >Once the critical bugs are fixed, I intend to branch the tree in >preparation for 4.3.0 cycle. The remaining critical bugs are: > > [15025] Copy of array is affected by reference > [19292] random error: open_basedir restriction in effect. File is in >

[PHP-DEV] 4.3.0

All, Once the critical bugs are fixed, I intend to branch the tree in preparation for 4.3.0 cycle. The remaining critical bugs are: [15025] Copy of array is affected by reference [19292] random error: open_basedir restriction in effect. File is in wrong di

[PHP-DEV] remote_addr

Hello, I need help I never programmed in php. :/ I have a firewall with proxy. Now a put a webcam behind the firewall. If put the external_ip i see the cam, if i put the internal_ip i see the cam. Now i made a web page with code below Nova pagina 1 test">tes

[PHP-DEV] patch to restrict database access for ext/pgsql

this patch adds the config variable pgsql.allowed_dblist by default it has no value, meaning all databases are accessible it can contain a colon delimited list of databases that are accessible. if the database accessed is not in the list, and the list is not null, then an error is returned as

[PHP-DEV] Re: open_basedir bug

Wez, have you had a chance to look at #19292? -Andrei http://www.gravitonic.com/ * My wishlist: http://www.amazon.com/exec/obidos/wishlist/2Q2DIPY7BZLSH/ * -- PHP Development Mailing List To unsubscribe, visit: http://www.php.net/unsub

[PHP-DEV] Re: [PHP-CVS] Re: cvs: php4 /ext/standard css.c info.c /main php_ini.c /sapi/aolserveraolserver.c /sapi/apache php_apache.c

Colin Viebrock wrote: > Jani/Derrick/et al ... is this okay with you now? ZTS build is broken, fix coming up right away. -- Sebastian Bergmann http://sebastian-bergmann.de/ http://phpOpenTracker.de/ Did I help you? Consider a gift: http://wishlist.sebastian-bergmann.de/

[PHP-DEV] php_request_shutdown_for_exec and a bunch of bugs

Anyone have any ideas or insight on these bug reports: #15529 ap_cleanup_for_exec not used when creating #16548 exec or system a daemon will catch the port for this session #15642 system() with background execution hangs due to bogus filehandles open It appears that the problem is due to this

Re: [PHP-DEV] feedback on PHP's WDDX

Hi, can you please file a bugreport on bugs.php.net and assign it to me (cvs id is jan). I'll look into this.> Jan -- Q: Thank Jan? A: http://geschenke.an.dasmoped.net/ Got an old and spare laptop? Please send me a mail. Key7BCC EB86 8313 DDA9 25DF Fingerprint

[PHP-DEV] Re: [PHP-CVS] cvs: php4 /ext/standard config.m4 css.c css.h info.c /main php_ini.c /sapi/aolserver aolserver.c /sapi/apache php_apache.c

Colin Viebrock <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: >> "render nicely" is something else than "total unreadable" to me. Did you >> have a look at it with Netscape Navigator 4? Please fix something for >> it, as it's pretty horrible now. > > Can you send me a screen grab? I did

Re: [PHP-DEV] autoconf version

On Thu, Sep 26, 2002 at 11:03:18AM -0400, Colin Viebrock wrote: > I'm just wondering if that's a mistake. Does 2.53 contain buggy cache > code and is downgrading my version of autoconf really the appropriate > solution? Or was the cache issue solved in a later version, and the > buildconf messag

RE: [PHP-DEV] [PATCH] include statement in php.ini file

I thought about reading only *.ini files when directories were specified, and the main reason I didn't implement that is simply because I thought the PHP include functionality should behave like Apache's Include directive. Apache's include doesn't worry about ~ files and .ORIG or .OLD or .bak file

Re: [PHP-DEV] autoconf version

On Thu, Sep 26, 2002 at 11:44:37AM -0400, Dan Kalowsky wrote: > I've been getting this on my OSX machine for awhile. Thats because > autoconf 2.53 is the default for the dev tools. Seems to be working > just fine. > > Not entirely sure whats "buggy" about it, but I don't keep up on the > wh

Re: [PHP-DEV] autoconf version

I've been getting this on my OSX machine for awhile. Thats because autoconf 2.53 is the default for the dev tools. Seems to be working just fine. Not entirely sure whats "buggy" about it, but I don't keep up on the whole autoconf world either. On Thursday, September 26, 2002, at 11:03 AM, C

Re: [PHP-DEV] autoconf version

On Thu, 26 Sep 2002, Colin Viebrock wrote: > I run buildconf and get: > > ... > buildconf: autoconf version 2.53 (ok) > buildconf: Your version of autoconf likely contains buggy cache code. >Running cvsclean for you. >To avoid this, install autoconf-2.13 and automake-1.5.

[PHP-DEV] autoconf version

I run buildconf and get: ... buildconf: autoconf version 2.53 (ok) buildconf: Your version of autoconf likely contains buggy cache code. Running cvsclean for you. To avoid this, install autoconf-2.13 and automake-1.5. ... I'm just wondering if that's a mistake. Does 2.53 c

Re: [PHP-DEV] Reimplementing .phps

This would work fine, IMHO (although I was told that it wasn't worth it by somebody). I'll implement it in this way and create another patch... maybe it'll be usable :) Devon Zeev Suraski wrote: > In order to fix the backwards dependencies issues, as well as simplify > the implementation of

RE: [PHP-DEV] [PATCH] include statement in php.ini file

I suppose using a PHP keyword like include may lead to a desire for other PHP keywords, perhaps something like: additional_ini = /some/dir additional_ini = /some/file.ini Not sure why you want to limit it to one. Also, they can be nested, so in /some/dir/foo.ini you might have: additional_ini

[PHP-DEV] test - ignore

-- --- Derick Rethans http://derickrethans.nl/ JDI Media Solutions http://www.jdimedia.nl/ -

[PHP-DEV] feedback on PHP's WDDX

Hi, I am using PHP's WDDX and find it very useful, but that's only if I use it to exchange data between PHP program. Once I have to exchange the data with other languange I begin to face problem after problem, mostly because of the way PHP's WDDX interpret the variable type. The solution for thi

Re: [PHP-DEV] [PATCH] 64 bit PHP (long vs int problems) (fault)

> Hi, > > I has explain that problem in 1 week ago, and what they said to me is "Your > not on the good list" > c.f: We are on PHP-_DEV_ isn't it ? > > and, well i'v the sames problem of you plus we can use a long integer in > PHP. Sorry, we can not use. > > Best Regards, > Vergoz Michael > > --

Re: [PHP-DEV] [PATCH] 64 bit PHP (long vs int problems)

Hi, I has explain that problem in 1 week ago, and what they said to me is "Your not on the good list" c.f: We are on PHP-_DEV_ isn't it ? and, well i'v the sames problem of you plus we can use a long integer in PHP. Best Regards, Vergoz Michael - Original Message - From: "Jason Greene"

[PHP-DEV] Re: CLI and HTTP header, GLOB_NOSORT

I got a little time, so I removed dup of GLOB_NOSORT definition. Header problem remains. -- Yasuo Ohgaki Yasuo Ohgaki wrote: > Something wrong in current CVS. > > > [yohgaki@dev HEAD]$ php > HTTP/1.0 0 X > Content-type: text/html; charset=EUC-JP > > PHP Notice: Constant GLOB_NOSORT already de

[PHP-DEV] CLI and HTTP header, GLOB_NOSORT

Something wrong in current CVS. [yohgaki@dev HEAD]$ php HTTP/1.0 0 X Content-type: text/html; charset=EUC-JP PHP Notice: Constant GLOB_NOSORT already defined in Unknown on line 0 Unknown(0) : Notice - Constant GLOB_NOSORT already defined [yohgaki@dev HEAD]$ php -v HTTP/1.0 0 X Content-type: tex