I'll try to find some time to look at it. I need to re-familiarize myself
with the output buffering code at some point anyway...
At 07:57 20/09/2002, Yasuo Ohgaki wrote:
>Zeev Suraski wrote:
>>At 12:27 19/09/2002, Yasuo Ohgaki wrote:
>>
>>>Dan Hardiker wrote:
>>>
We are dealing with *idiot
[EMAIL PROTECTED] wrote:
> I *do* think that line numbers being linked like lxr.php.net is a good idea
> and is a really easy thing to code. +1's? However, turning it on based on
> linking to a numbered link isn't a great idea as links with # are much more
> common than people using ?HIGHLIGHT_F
Zeev Suraski wrote:
> At 12:27 19/09/2002, Yasuo Ohgaki wrote:
>
>> Dan Hardiker wrote:
>>
>>> We are dealing with *idiots* here. Their CODE doesnt work, they are
>>> *learning* PHP, they want help on their *non-functional* code, easily,
>>> simply and quickly.
>>> We can already say "put this in
On Thu, 19 Sep 2002, [EMAIL PROTECTED] wrote:
> That's what I thought also (as far as cvs access). I need to make a new
> patch really quick because a bugfix was applied in the zend_highlight.c
> file that wasn't apparent in the file that I was working with. This being
> the first patch I've ma
TECTED], [EMAIL PROTECTED]
Subject: RE: [PHP-DEV] Thread Reading
On Thu, 19 Sep 2002, [EMAIL PROTECTED] wrote:
> Applied a little bit ago to help with translating documentation from to
> Dutch, but I didn't have much luck (plus I'm not currently subscribed to
> the Dutch m
On Thu, 19 Sep 2002, [EMAIL PROTECTED] wrote:
> Applied a little bit ago to help with translating documentation from to
> Dutch, but I didn't have much luck (plus I'm not currently subscribed to
> the Dutch manual mailing list, blah blah blah). Should I apply for an
> account to commit this to t
hi,
> And sensitive cleartext data like SQL passwords can always be passed
> through environment variables. For instance, Apache has the 'Setenv'
> directive to set this, and the httpd.conf file can be made only readable by
> root.
Correct me if I'm wrong, but the documentation to mod_auth_ext
al Message:
-
From: James Cox [EMAIL PROTECTED]
Date: Thu, 19 Sep 2002 20:29:16 +0100
To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: RE: [PHP-DEV] Thread Reading
> At 20:10 19/09/2002, Adam Voigt wrote:
> >Newbie's or
> At 20:10 19/09/2002, Adam Voigt wrote:
> >Newbie's or people seeking help with bad security
> >standards, could give away the password to there SQL server, etc.
> >Maybe the phps parser or whatever it's called should automatically ***
> >out the password fields of all the db, ftp, etc. calls.
>
At 20:10 19/09/2002, Adam Voigt wrote:
>Newbie's or people seeking help with bad security
>standards, could give away the password to there SQL server, etc.
>Maybe the phps parser or whatever it's called should automatically ***
>out the password fields of all the db, ftp, etc. calls.
I don't thi
plain stupid. I hope everyone on php-dev@ agrees
that this isn't a "vulnerability"
Met vriendelijke groeten,
Devon H. O'Dell
sitetronics.com
Original Message:
-
From: Jedi/Sector One [EMAIL PROTECTED]
Date: Thu, 19 Sep 2002 20:02:22 +0200
To: [EMAIL PROTECT
On Thu, Sep 19, 2002 at 01:56:03PM -0400, [EMAIL PROTECTED] wrote:
> This is a security standard that is already inherent in the current phps
> version. It is also not the job of PHP to save people from themselves.
And sensitive cleartext data like SQL passwords can always be passed
through en
00
To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: Re: [PHP-DEV] Thread Reading
Newbie's or people seeking help with bad security
standards, could give away the password to there SQL server, etc.
Maybe the phps parser or whatever it's called should
There's nothing inherent about .phps that is incompatible with output
buffers. Fixing this should be simple enough.
At 12:52 19/09/2002, Yasuo Ohgaki wrote:
>Markus Fischer wrote:
>>On Thu, Sep 19, 2002 at 06:27:55PM +0900, Yasuo Ohgaki wrote :
>>>Let's discourage usage of phps in the manual wh
Newbie's or people seeking help with bad security
standards, could give away the password to there SQL server, etc.
Maybe the phps parser or whatever it's called should automatically ***
out the password fields of all the db, ftp, etc. calls.
Adam Voigt
[EMAIL PROTECTED]
On Thu, 2002-09-19 at 13
At 12:27 19/09/2002, Yasuo Ohgaki wrote:
>Dan Hardiker wrote:
>>We are dealing with *idiots* here. Their CODE doesnt work, they are
>>*learning* PHP, they want help on their *non-functional* code, easily,
>>simply and quickly.
>>We can already say "put this in a .php file then give us the URL to i
Dan Hardiker wrote:
>>hm, what's the use of having a table here?
>
>
> Because what if there is someone with a 10,000 line script? or just a 6
> line script? Then the indenting will look out of place or crooked.
>
> If we are outputing in HTML, why not *use* HTML ;) Tables allows the left
> han
> hm, what's the use of having a table here?
Because what if there is someone with a 10,000 line script? or just a 6
line script? Then the indenting will look out of place or crooked.
If we are outputing in HTML, why not *use* HTML ;) Tables allows the left
hand column to be flexable.
Is there
Devon O'Dell wrote:
> Simple fix :)
[...]
http://www.dapond.net/code/backtrace.phps?HIGHLIGHT_FORMAT=lineno
>>>This last url doesn't output anything.
>>>Maybe because the HTML is broken?
>>>
>>
>> missing
hm, what's the use of having a table here?
why not just one big environ
Simple fix :)
Devon
[EMAIL PROTECTED] wrote:
>On Thu, 19 Sep 2002, Jani Taskinen wrote:
>
>>On Thu, 19 Sep 2002, Dan Hardiker wrote:
>>
>>>For those of you who dont have time, or the capability to test it out for
>>>yourself, please take the following exampes:
>>>
>>> http://www.dapond.net/code
On Thu, 19 Sep 2002, Yasuo Ohgaki wrote:
> [EMAIL PROTECTED] wrote:
> > On Thu, 19 Sep 2002, Yasuo Ohgaki wrote:
> >
> >
> >>Let's discourage usage of phps in the manual while adding new feature.
> >
> >
> > Let's not do that. There was no single bugreport about it.
> >
>
> Could you reprod
On Thu, 19 Sep 2002, Jani Taskinen wrote:
> On Thu, 19 Sep 2002, Dan Hardiker wrote:
>
> >For those of you who dont have time, or the capability to test it out for
> >yourself, please take the following exampes:
> >
> > http://www.dapond.net/code/backtrace.php
> > http://www.dapond.net/code/ba
[EMAIL PROTECTED] wrote:
> On Thu, 19 Sep 2002, Yasuo Ohgaki wrote:
>
>
>>Let's discourage usage of phps in the manual while adding new feature.
>
>
> Let's not do that. There was no single bugreport about it.
>
Could you reproduce the problem now?
--
Yasuo Ohgaki
--
PHP Development Mai
On Thu, 19 Sep 2002, Dan Hardiker wrote:
>For those of you who dont have time, or the capability to test it out for
>yourself, please take the following exampes:
>
> http://www.dapond.net/code/backtrace.php
> http://www.dapond.net/code/backtrace.phps
> http://www.dapond.net/code/backtrace.phps
[EMAIL PROTECTED] wrote:
> On Thu, 19 Sep 2002, Yasuo Ohgaki wrote:
>
>
>>[EMAIL PROTECTED] wrote:
>>
>>>No, I'm not sleepdy. There aren't any line numbers or variables in your
>>>backtrace. This usually does happen when there is no debug info.
>>
>>Ah. I see.
>>I'm on the machine httpd w/o --e
On Thu, 19 Sep 2002, Yasuo Ohgaki wrote:
> [EMAIL PROTECTED] wrote:
> >
> > No, I'm not sleepdy. There aren't any line numbers or variables in your
> > backtrace. This usually does happen when there is no debug info.
>
> Ah. I see.
> I'm on the machine httpd w/o --enable-debug now, but
> isn't
[EMAIL PROTECTED] wrote:
> On Thu, 19 Sep 2002, Yasuo Ohgaki wrote:
>
>
>>I guess you are sleepy :)
>>Or my mail is messed up ?
>
>
> No, I'm not sleepdy. There aren't any line numbers or variables in your
> backtrace. This usually does happen when there is no debug info.
Ah. I see.
I'm on t
On Thu, 19 Sep 2002, Yasuo Ohgaki wrote:
> I guess you are sleepy :)
> Or my mail is messed up ?
No, I'm not sleepdy. There aren't any line numbers or variables in your
backtrace. This usually does happen when there is no debug info.
Derick
[EMAIL PROTECTED] wrote:
> On Thu, 19 Sep 2002, Yasuo Ohgaki wrote:
>
>
>>I don't recall bug ID, but here is the backtrace.
>>
>>The cause would be output buffer and zend_printf does not
>>work well together. Enabling any buffer segfualt php when
>>phps is used.
>
>
> this bt is pretty useless
Ic, so Yasou, please open a bug report with the appropriate
information so we have it in the DB, thx.
On Thu, Sep 19, 2002 at 06:52:49PM +0900, Yasuo Ohgaki wrote :
> Markus Fischer wrote:
> >On Thu, Sep 19, 2002 at 06:27:55PM +0900, Yasuo Ohgaki wrote :
> >
> >>Let's discourage usage o
On Thu, 19 Sep 2002, Yasuo Ohgaki wrote:
> I don't recall bug ID, but here is the backtrace.
>
> The cause would be output buffer and zend_printf does not
> work well together. Enabling any buffer segfualt php when
> phps is used.
this bt is pretty useless without any debug info in apache or PH
Markus Fischer wrote:
> On Thu, Sep 19, 2002 at 06:27:55PM +0900, Yasuo Ohgaki wrote :
>
>>Let's discourage usage of phps in the manual while adding new feature.
>
>
> Wait, stop. First hand over the related bug IDs, couldn't
> find it only be text searching which you were refering to
On Thu, 19 Sep 2002, Yasuo Ohgaki wrote:
> Let's discourage usage of phps in the manual while adding new feature.
Let's not do that. There was no single bugreport about it.
Derick
---
Derick Rethans
On Thu, Sep 19, 2002 at 06:27:55PM +0900, Yasuo Ohgaki wrote :
> Let's discourage usage of phps in the manual while adding new feature.
Wait, stop. First hand over the related bug IDs, couldn't
find it only be text searching which you were refering to in
an earlier post, before we at
Dan Hardiker wrote:
> We are dealing with *idiots* here. Their CODE doesnt work, they are
> *learning* PHP, they want help on their *non-functional* code, easily,
> simply and quickly.
>
> We can already say "put this in a .php file then give us the URL to it"
> and cut n paste them a short scrip
>> For those of you who dont have time, or the capability to test it out
>> for yourself, please take the following exampes:
>>
>> http://www.dapond.net/code/backtrace.php
>> http://www.dapond.net/code/backtrace.phps
>> http://www.dapond.net/code/backtrace.phps?HIGHLIGHT_FORMAT=default
>> ht
Me too.
--
Yasuo Ohgaki
James Cox wrote:
> I agree. Lets jsut get this in the tree..
>
> -- james
>
>
>>On Thu, Sep 19, 2002 at 02:28:35AM +0100, Dan Hardiker wrote :
>>
>>>This doesnt demonstrate the use of the show_source (or other aliased)
>>>function, but I assure you - it works similar
On Thu, 19 Sep 2002, Dan Hardiker wrote:
> I still await a good reason for this not to become part of the standard
> distribution, and any list of adverse side affects this poses.
Where is the patch? :) I think it's about time that it gets integrated/
looked upon.
Derick
-
Looks great!
Derick
On Thu, 19 Sep 2002, Dan Hardiker wrote:
> Hi all [specifically those monitoring the patches thread],
>
> Ive noticed that alot of you seem to be asking questions which were
> actually answered in the original post of the thread. Can I request that
> anyone who has an opin
I agree. Lets jsut get this in the tree..
-- james
>
> On Thu, Sep 19, 2002 at 02:28:35AM +0100, Dan Hardiker wrote :
> > This doesnt demonstrate the use of the show_source (or other aliased)
> > function, but I assure you - it works similarly with an optional
> > parameter, defaulting to cur
On Thu, Sep 19, 2002 at 02:28:35AM +0100, Dan Hardiker wrote :
> This doesnt demonstrate the use of the show_source (or other aliased)
> function, but I assure you - it works similarly with an optional
> parameter, defaulting to current behaviour.
I hope you don't forget that highlight_file(
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 18 September 2002 09:49 pm, Yasuo Ohgaki wrote:
> Dan Hardiker wrote:
> > Hi all [specifically those monitoring the patches thread],
> >
> > Ive noticed that alot of you seem to be asking questions which were
> > actually answered in the
Dan Hardiker wrote:
> Hi all [specifically those monitoring the patches thread],
>
> Ive noticed that alot of you seem to be asking questions which were
> actually answered in the original post of the thread. Can I request that
> anyone who has an opinion on this matter both read the thread, and
I totally agree to you - and i still can't catch up the point what the current
discussion is about.
Sascha
> The underlying effect is minimal, no noticable change. The effect of
> having the option there is mind blowing for IRC based support staff who
> are dealing with (for want of a better wo
Hi all [specifically those monitoring the patches thread],
Ive noticed that alot of you seem to be asking questions which were
actually answered in the original post of the thread. Can I request that
anyone who has an opinion on this matter both read the thread, and (where
possible) try out the p
45 matches
Mail list logo
