Re: [PHP-DEV] Open issues for 4.0.6

2001-05-19 Thread Andi Gutmans

At 11:01 PM 5/18/2001 +0200, [EMAIL PROTECTED] wrote:
On Fri, 18 May 2001, Andi Gutmans wrote:

  Okay but I don't think there is much left to do for 4.0.6 and it can
  hopefully be released within a week or so.
  Any idea who is tackling that mcrypt() problem? Does this happen to
  everyone using it?

I just committed a fix to the CVS, this solved the problem for me.
libmcrypt 2.4.10 still gives some strange results (encrypted strings like
8 \0's), but it works fine with libmcrypt 2.4.11 (I could not get 2.4.12
to compile here).

Do you think this is a bug with libmcrypt or in PHP? Should we have 
./configure detect the version and say that you need = 2.4.11?

Andi


-- 
PHP Development 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]




Re: [PHP-DEV] Open issues for 4.0.6

2001-05-19 Thread Andi Gutmans

Can you grab the latest CVS and check if this is fixed.
Derick commited a couple of fixes yesterday.
Andi

At 05:13 PM 5/18/2001 +0100, Chris Walker wrote:
Hello Andi,

Friday, May 18, 2001, 5:07:46 PM, you wrote:

AG I think there are two main open issues for 4.0.6.
AG The crash in mcrypt (if it is a general problem) and the rollback of 
domxml.

AG Am I correct? Is there anything else crucial which needs to be added?

AG Andi

I re-verified the mcrypt problem late last night by upgrading a redundant
linux server to 4.0.6 and the mcrypt functions immediately started to
fail - interestingly all platforms this has been tested on return
DNS/Server not found errors in MSIE  5.0 under Win32. I fully expect
it to do the same on other platforms/browser configurations but don't
have the time to go through them all.

The immediate workaround is of course to comment out / remove the
appropriate calls to the mcrypt functions but clearly for applications
where data integrity is important this isn't a long term fix.

I understand that Derek was going to have a look at this issue last
night, and would appreciate any information on progress as and when it
arises; we have 3 applications relying on this functionality to secure
user data and each of them is now using alternative methods which I am
keen to bin at the earliest opportunity.

--
Best regards,
  Chris
  Operations Director, Gameshrine Limited
  mailto:[EMAIL PROTECTED]


-- 
PHP Development 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]




Re: [PHP-DEV] Open issues for 4.0.6

2001-05-19 Thread derick

On Sat, 19 May 2001, Andi Gutmans wrote:

 I just committed a fix to the CVS, this solved the problem for me.
 libmcrypt 2.4.10 still gives some strange results (encrypted strings like
 8 \0's), but it works fine with libmcrypt 2.4.11 (I could not get 2.4.12
 to compile here).

 Do you think this is a bug with libmcrypt or in PHP? Should we have
 ./configure detect the version and say that you need = 2.4.11?

I know almost certain that this bug is in mcrypt, because reinstalling
(without recompiling PHP) libmcrypt 2.4.10 gives the wrong output again.

So it's wise to do a check for 2.4.11, but I wonder if we must make it =
2.4.11, or == 2.4.11, as I expect that compiling with 2.4.12 gives very
much trouble (because of an updated libtldl). I can check it as soon as
2.4.13 is out, but I could not get 2.4.12 compiled on my box within 5
minutes.

regards,

Derick Rethans

-
PHP: Scripting the Web - www.php.net - [EMAIL PROTECTED]
 SRM: Site Resource Manager - www.vl-srm.net
-


-- 
PHP Development 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]




Re: [PHP-DEV] Open issues for 4.0.6

2001-05-19 Thread Andi Gutmans

I don't know but I feel it's wrong to do an == check because people might 
be using this PHP version when 2.4.18 is out.

Andi

At 06:47 PM 5/19/2001 +0200, [EMAIL PROTECTED] wrote:
On Sat, 19 May 2001, Andi Gutmans wrote:

  I just committed a fix to the CVS, this solved the problem for me.
  libmcrypt 2.4.10 still gives some strange results (encrypted strings like
  8 \0's), but it works fine with libmcrypt 2.4.11 (I could not get 2.4.12
  to compile here).
 
  Do you think this is a bug with libmcrypt or in PHP? Should we have
  ./configure detect the version and say that you need = 2.4.11?

I know almost certain that this bug is in mcrypt, because reinstalling
(without recompiling PHP) libmcrypt 2.4.10 gives the wrong output again.

So it's wise to do a check for 2.4.11, but I wonder if we must make it =
2.4.11, or == 2.4.11, as I expect that compiling with 2.4.12 gives very
much trouble (because of an updated libtldl). I can check it as soon as
2.4.13 is out, but I could not get 2.4.12 compiled on my box within 5
minutes.

regards,

Derick Rethans

-
 PHP: Scripting the Web - www.php.net - [EMAIL PROTECTED]
  SRM: Site Resource Manager - www.vl-srm.net
-


-- 
PHP Development 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]




Re: [PHP-DEV] Open issues for 4.0.6

2001-05-19 Thread derick

On Sat, 19 May 2001, Andi Gutmans wrote:

 I don't know but I feel it's wrong to do an == check because people might
 be using this PHP version when 2.4.18 is out.

True, but I just tried 2.4.13, and it didn't compile straight out of the
box. I'm complaining to the author now about this. But it does work fine
(i.e., it actually encrypts the data, while 2.4.10 does not do that).

regards,

Derick

-
PHP: Scripting the Web - www.php.net - [EMAIL PROTECTED]
 SRM: Site Resource Manager - www.vl-srm.net
-


-- 
PHP Development 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]




Re: [PHP-DEV] Open issues for 4.0.6

2001-05-19 Thread Andi Gutmans

At 07:11 PM 5/19/2001 +0200, [EMAIL PROTECTED] wrote:
On Sat, 19 May 2001, Andi Gutmans wrote:

  I don't know but I feel it's wrong to do an == check because people might
  be using this PHP version when 2.4.18 is out.

True, but I just tried 2.4.13, and it didn't compile straight out of the
box. I'm complaining to the author now about this. But it does work fine
(i.e., it actually encrypts the data, while 2.4.10 does not do that).

Yeah but for the people it compiles there's a good chance it'll work. For 
people it doesn't compile for they will probably install 2.4.12 automatically.

Andi


-- 
PHP Development 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]




Re: [PHP-DEV] Open issues for 4.0.6

2001-05-19 Thread derick

On Sat, 19 May 2001, Andi Gutmans wrote:

 Yeah but for the people it compiles there's a good chance it'll work. For
 people it doesn't compile for they will probably install 2.4.12 automatically.

Indeed (BTW, .12 is not available anymore, only .11 and .13). Further,
I've no idea how to fix this in the configure scripts (the check for .13),
so please can somebody look at this?

Derick

-
PHP: Scripting the Web - www.php.net - [EMAIL PROTECTED]
 SRM: Site Resource Manager - www.vl-srm.net
-


-- 
PHP Development 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]




Re: [PHP-DEV] Open issues for 4.0.6

2001-05-19 Thread Hartmut Holzgraefe

Andi Gutmans wrote:
 i'd like to rename php_unregister_info_logos() (in ./main/php_logos.h)
 to php_unregister_info_logo() (singular) as it operates on *one*
 logo image, not a group of those
 
 hope this won't brake to much code out there as it is not documented
 yet, but as i'm going to do so soon i'd like to set this strait asap ...
 
 Is this function actually needed? It doesn't seem as if any code is using it.

it's not needed within php itself as the only standard extension that
registers info logos is ext/standard for the php and zend logos 
i haven't put any unregister calls into ext/standard MSHUTDOWN() as
it destroys the whole logo registration cash anyway

but the original idea behind making the phpinfo logo thing more 
gereral was to have an interface for third party extensions so that
theese can register their own info images (like vendor logos),
and theese should definetly use the unregister call in their
MSHUTDOWN() functions

not sure about anybody but Six using this in a serious extension though




-- 
Hartmut Holzgraefe  [EMAIL PROTECTED]  http://www.six.de  +49-711-99091-77

-- 
PHP Development 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]




[PHP-DEV] Open issues for 4.0.6

2001-05-18 Thread Andi Gutmans

I think there are two main open issues for 4.0.6.
The crash in mcrypt (if it is a general problem) and the rollback of domxml.

Am I correct? Is there anything else crucial which needs to be added?

Andi


-- 
PHP Development 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]




Re: [PHP-DEV] Open issues for 4.0.6

2001-05-18 Thread Chris Walker

Hello Andi,

Friday, May 18, 2001, 5:07:46 PM, you wrote:

AG I think there are two main open issues for 4.0.6.
AG The crash in mcrypt (if it is a general problem) and the rollback of domxml.

AG Am I correct? Is there anything else crucial which needs to be added?

AG Andi

I re-verified the mcrypt problem late last night by upgrading a redundant
linux server to 4.0.6 and the mcrypt functions immediately started to
fail - interestingly all platforms this has been tested on return
DNS/Server not found errors in MSIE  5.0 under Win32. I fully expect
it to do the same on other platforms/browser configurations but don't
have the time to go through them all.

The immediate workaround is of course to comment out / remove the
appropriate calls to the mcrypt functions but clearly for applications
where data integrity is important this isn't a long term fix.

I understand that Derek was going to have a look at this issue last
night, and would appreciate any information on progress as and when it
arises; we have 3 applications relying on this functionality to secure
user data and each of them is now using alternative methods which I am
keen to bin at the earliest opportunity.

-- 
Best regards,
 Chris
 Operations Director, Gameshrine Limited
 mailto:[EMAIL PROTECTED]



-- 
PHP Development 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]




Re: [PHP-DEV] Open issues for 4.0.6

2001-05-18 Thread Sterling Hughes

Andi Gutmans wrote:

 I think there are two main open issues for 4.0.6.
 The crash in mcrypt (if it is a general problem) and the rollback of 
 domxml.
 
 Am I correct? Is there anything else crucial which needs to be added?


Yup, and after Colin's message, I'm still deciding whether to rollback 
the DOM-XML commit in the branch.  Right now I'm going through the 
source and doing a bit of cleanup (removing confusing commented 
portions, adding some debugging features).  I'm basically waiting to the 
last minute to see if I can get enough cleaned up and working for the 
next release (crash bugs, functionality, documentation, etc.)

I probably won't be able to finish, and end up just reverting the commit 
in the branch, but its worth a try. ;)

-Sterling


-- 
PHP Development 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]




Re: [PHP-DEV] Open issues for 4.0.6

2001-05-18 Thread Andrei Zmievski

On Fri, 18 May 2001, Sterling Hughes wrote:
 Yup, and after Colin's message, I'm still deciding whether to rollback 
 the DOM-XML commit in the branch.  Right now I'm going through the 
 source and doing a bit of cleanup (removing confusing commented 
 portions, adding some debugging features).  I'm basically waiting to the 
 last minute to see if I can get enough cleaned up and working for the 
 next release (crash bugs, functionality, documentation, etc.)
 
 I probably won't be able to finish, and end up just reverting the commit 
 in the branch, but its worth a try. ;)

The extension is pretty broken right now. I think he tried to emulate
what I did in PHP-GTK and at the same time preserve backwards
compatibility to the old API and that's just not possible. Example,
domxml_children() crashes because it's an alias for $root-children and
for the former case this_ptr is NULL. In PHP-GTK all functions are
methods, but it wouldn't help here.

-Andrei
* UNIX, isn't that some archaic form of DOS? - our job applicant *

-- 
PHP Development 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]




Re: [PHP-DEV] Open issues for 4.0.6

2001-05-18 Thread Hartmut Holzgraefe

Andi Gutmans wrote:
 
 I think there are two main open issues for 4.0.6.
 The crash in mcrypt (if it is a general problem) and the rollback of domxml.
 
 Am I correct? Is there anything else crucial which needs to be added?

i'd like to remove my SAP extension from the 4.0.6RC branch as it has
no production functionality as of yet ...

-- 
Hartmut Holzgraefe  [EMAIL PROTECTED]  http://www.six.de  +49-711-99091-77

-- 
PHP Development 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]




Re: [PHP-DEV] Open issues for 4.0.6

2001-05-18 Thread Hartmut Holzgraefe

Andi Gutmans wrote:
 
 I think there are two main open issues for 4.0.6.
 The crash in mcrypt (if it is a general problem) and the rollback of domxml.
 
 Am I correct? Is there anything else crucial which needs to be added?

one more ...

i'd like to rename php_unregister_info_logos() (in ./main/php_logos.h)
to php_unregister_info_logo() (singular) as it operates on *one*
logo image, not a group of those

hope this won't brake to much code out there as it is not documented
yet, but as i'm going to do so soon i'd like to set this strait asap ...

-- 
Hartmut Holzgraefe  [EMAIL PROTECTED]  http://www.six.de  +49-711-99091-77

-- 
PHP Development 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]




Re: [PHP-DEV] Open issues for 4.0.6

2001-05-18 Thread Andi Gutmans

At 09:46 PM 5/18/2001 +0200, Hartmut Holzgraefe wrote:
Andi Gutmans wrote:
 
  I think there are two main open issues for 4.0.6.
  The crash in mcrypt (if it is a general problem) and the rollback of 
 domxml.
 
  Am I correct? Is there anything else crucial which needs to be added?

one more ...

i'd like to rename php_unregister_info_logos() (in ./main/php_logos.h)
to php_unregister_info_logo() (singular) as it operates on *one*
logo image, not a group of those

hope this won't brake to much code out there as it is not documented
yet, but as i'm going to do so soon i'd like to set this strait asap ...

Is this function actually needed? It doesn't seem as if any code is using it.

Andi


-- 
PHP Development 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]




Re: [PHP-DEV] Open issues for 4.0.6

2001-05-18 Thread Andi Gutmans

At 12:07 AM 5/18/2001 -0400, Sterling Hughes wrote:
Andi Gutmans wrote:

I think there are two main open issues for 4.0.6.
The crash in mcrypt (if it is a general problem) and the rollback of domxml.
Am I correct? Is there anything else crucial which needs to be added?


Yup, and after Colin's message, I'm still deciding whether to rollback the 
DOM-XML commit in the branch.  Right now I'm going through the source and 
doing a bit of cleanup (removing confusing commented portions, adding some 
debugging features).  I'm basically waiting to the last minute to see if I 
can get enough cleaned up and working for the next release (crash bugs, 
functionality, documentation, etc.)

I probably won't be able to finish, and end up just reverting the commit 
in the branch, but its worth a try. ;)

Okay but I don't think there is much left to do for 4.0.6 and it can 
hopefully be released within a week or so.
Any idea who is tackling that mcrypt() problem? Does this happen to 
everyone using it?

Andi


-- 
PHP Development 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]




Re: [PHP-DEV] Open issues for 4.0.6

2001-05-18 Thread Andi Gutmans

At 06:53 PM 5/18/2001 +0200, Hartmut Holzgraefe wrote:
Andi Gutmans wrote:
 
  I think there are two main open issues for 4.0.6.
  The crash in mcrypt (if it is a general problem) and the rollback of 
 domxml.
 
  Am I correct? Is there anything else crucial which needs to be added?

i'd like to remove my SAP extension from the 4.0.6RC branch as it has
no production functionality as of yet ...

That's kind of a problem. There's no way I know of where we could remove it 
just from the 4.0.6 branch (CVS is a bit limited in this respect. It's much 
less powerful than Clearcase and other commercial version control systems).
We could completely remove it from PHP and re-add it after 4.0.6 is out of 
the door.
What do you guys think?

Andi


-- 
PHP Development 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]




Re: [PHP-DEV] Open issues for 4.0.6

2001-05-18 Thread derick

On Fri, 18 May 2001, Andi Gutmans wrote:

 Okay but I don't think there is much left to do for 4.0.6 and it can
 hopefully be released within a week or so.
 Any idea who is tackling that mcrypt() problem? Does this happen to
 everyone using it?

I just committed a fix to the CVS, this solved the problem for me.
libmcrypt 2.4.10 still gives some strange results (encrypted strings like
8 \0's), but it works fine with libmcrypt 2.4.11 (I could not get 2.4.12
to compile here).

regards,

Derick Rethans

-
PHP: Scripting the Web - www.php.net - [EMAIL PROTECTED]
 SRM: Site Resource Manager - www.vl-srm.net
-


-- 
PHP Development 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]