Just FYI, I'm voting against this proposal, as the number of parameters is simply growing out of control, which involves: - more BC breaks if default parameters change - more security issues if the defaults are unsafe (or become unsafe, for whatever reason) - more cognitive load (it's arguably more complex)
In general, this simply pushes too many responsibilities on the interface. Support for AEAD can be moved to a separate function, which involves a minor BC break: collision with pre-existing functions, if anybody was crazy/stupid enough to implement crypto in userland, and even worse in the global namespace. Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/ On 20 January 2016 at 17:40, Jakub Zelenka <bu...@php.net> wrote: > Hi, > > The vote is now open: > > https://wiki.php.net/rfc/openssl_aead#voting > > Cheers > > Jakub >
