Re: [PHP-DEV] aes_decrypt() aes_encrypt() (was Re: crypto_something)

2015-02-27 Thread Tom Worster
On 2/27/15, 4:29 PM, "Leigh" wrote: >On 27 February 2015 at 21:14, Tom Worster wrote: > >> I don't see why we couldn't sponsor an effort to encourage adoption >> of this or some such interoperability protocol. Go to FIG, see if the >> Rails, Node and Django people are interested, and so fourth..

Re: [PHP-DEV] aes_decrypt() aes_encrypt() (was Re: crypto_something)

2015-02-27 Thread Leigh
On 27 February 2015 at 21:14, Tom Worster wrote: > 1. You say it "doesn't leave any room for interoperability" but I'm > not sure I agree. I invite you again to look at the Cryptography lib > for Python. There are countless applications/services that will do things "their own way", and the odds o

[PHP-DEV] aes_decrypt() aes_encrypt() (was Re: crypto_something)

2015-02-27 Thread Tom Worster
On 2/26/15 11:12 AM, Leigh wrote:> On 26 February 2015 at 15:37, Tom Worster wrote: > I've spoken with Anthony and a couple of others about something in the > same vein as the new csprng functions. I think core needs a pair of > functions that handles the needs of the 99%. Those functions are. >