Please consider dropping requirement on MCrypt.

[remicollet]

lilbmcrypt is a dead project, unmainted for ~7years.
Some Enterprise Distribution simply don't provide it (e.g. RHEL)

Relying on a dead cow for cryptography just sounds terrible.

Please consider switching to openssl encryption which is much more common and wel maintained.

[GrahamCampbell]

We are using both openssl and mcrypt. Taylor would probably accept a PR to 5.1 to remove the need for mcrypt, though I can't speak for him.

[GrahamCampbell]

5.1 will be our next and first LTS release btw, and will ship on Tuesday next week.

[GrahamCampbell]

It's also php 5.5.9+ only. :)

[remicollet]

It's also php 5.5.9+ only. :)

Which is fine ;) RHEL (with RHSCL 2.0) provides 5.5.21 and 5.6.5 ;)
But not mcrypt

[GrahamCampbell]

Which is fine

Great. I'd quite like to see us dropping mcrypt too. :)

[jbrooksuk]

Dropping mcrypt would be a great change! :)

[GrahamCampbell]

I'll talk to Taylor about this later today and see what he thinks. :)

[base-zero]

👍

[taylorotwell]

If it can be done in a backwards compatible way, sure.

[ibrasho]

If I remove mcrypt dependency completely but end up with compatible encoding, is that fine?

[taylorotwell]

As long as it can decrypt stuff that was encrypted using the old mcrypt way.

On Wed, Jun 3, 2015 at 1:16 PM, Ibrahim AshShohail <notifications@github.com

wrote:

If I remove mcrypt dependency completely but end up with compatible
encoding, is that fine?

—
Reply to this email directly or view it on GitHub
#9020 (comment).

[ibrasho]

Encrypter::setCipher() and Encrypter::setMode() will not be BC.

Is this acceptable?

[taylorotwell]

I'm fine with that.

[ibrasho]

Done #9041