# libmcrypt: abandonware?

- Thread: https://externals.io/message/79531
- Original archive: https://news-web.php.net/php.internals/79531
- Started by Scott Arciszewski on 2014-12-10T18:25:28+00:00
- Messages: 1
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #79531 — Scott Arciszewski — 2014-12-10T18:25:28+00:00

URL: https://externals.io/message/79531#79531

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Le 05/12/2014 17:17, Scott Arciszewski a écrit :
> > […]
>
> Having a dead upstream for crypto API is a critical issue :(
>
> FYI some downstream (ex RHEL) don't even provide this library.
> Already too much crypto libraries, and it will be a mess to provide a
> dead project in an Enterprise distribution.
>
> So php/mcrypt also not available.
>
> But most applications. which use it, usually have alternative, and
> make it optional (ex phpMyAdmin 4.3 now even use openssl as first choice).
>
> We probably have enough crypto API in PHP, and we probably should mark
> this one as deprecated / unmaintained in 5.x, and move it to PECL (7.x).
>
>
> Remi.
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAlSH6R0ACgkQYUppBSnxahiRdQCg6IKC9hfJavD9QE3dXEVc8o4t
> H+kAoIWLbVRwS5qfidJi8Yq/F/NQ7vlH
> =osvZ
> -----END PGP SIGNATURE-----

Well then, I'll focus on migrating all my code to use openssl instead of
mcrypt. :)

I think this would be for the best.