On 07/01/2016 16:11, Scott Arciszewski wrote:
I'm personally not going to bother pushing for a pluggable crypto API if the only option is to use OpenSSL and all its legacy cruft.
I think what people are suggesting is not that libsodium shouldn't be supported under-the-hood, just that the fact you're using it shouldn't be exposed to userland. A PDO-like encryption interface (which as I understand it is not what you proposed in your other thread) would allow us to add libsodium in such a way that a relatively painless migration path can be created if it goes the way of mcrypt. So the pluggable API removes the need for any of the sodium_* / Sodium::* / \Sodium\* functions.
Regards, -- Rowan Collins [IMSoP] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
