Re: [eAccelerator-developers] No Support for eAccelerator?

[Bart V. <bar...@zo...>]

Ed Baer wrote:
> Hi,
>=20
> Thanks for your reply.
>=20
> Is it not possible to have the newest version of eAccelerator be able t=
o
> decode both 5.0.x and 5.1.x since the code is already written for both?=

> Why not look for a signature in the encoded script and call either one
> decoder or the other.  You already have the Zend and other information
> in the encoded data.
>=20
> I was having a security issue a while back and I added an encryption
> step to the Turke mmcache version of the code.  It put a signature in
> the first few bytes of the encoded script.  If it didn't find that
> signature during decode it just bypassed the decryption step and went
> straight to the decoding.
>=20
> This would eliminate the breakage of all the previously encoded scripts=
=2E
> Also, this would also allow everyone to step up to your newest version
> without a complete recompile of all the code already written and you
> would get a much faster adoption of the new version.
>=20
> I think everyone would like to move to PHP 5.1.x at this point since
> 5.0.3 is from late 2004.  They will just have to limit their syntax to
> PHP 4.3 for compiled scripts in order to keep stability until you have
> completed the 5.x encoder port.  Then the transition will be transparen=
t
> and painless and most people will already be on the new code base.
>=20
> BTW, I am using the encoder that came with of 0.9.2a with PHP 5.0.3 and=

> limiting the function calls and syntax to what is available in PHP 4.3
> and everything seems to work just fine.
>=20
> I am perfectly happy to wait for you to get the 0.9.5+ version of the
> encoder to support 5.x syntax.
>=20
> Just out of curiosity though, is there any schedule for getting the 5.x=

> version of the encoder working?
>=20
> Thanks again for your input.
>=20
> ewb
>=20

Hello,

I don't know if you have seen the current encoder code but it's really
really messy and very hard to maintain. I've started rewriting it but I
don't have much time at the moment.
I only need the caching so for me encoding really isn't a priority.
About the multiple decoders, thats quite hard to do and would require a
lot of extra code. At the moment we are < 1.0, this means that
eAccelerator isn't "stable" yet and still under development.

The compatibility between php versions isn't something we can do
something about. They change opcodes a lot lately.

gr,

Bart

--=20
Bart Vanbrabant <bar...@zo...>
PGP fingerprint: 093C BB84 17F6 3AA6 6D5E  FC4F 84E1 FED1 E426 64D1