On Wed, Jul 23, 2014 at 6:28 PM, Scott Arciszewski <[email protected]> wrote:
> I've forwarded the message onto jedisct1. I'm not part of the dev team, > just a user. :) > > > On Fri, Jul 18, 2014 at 3:00 AM, Pierre Joye <[email protected]> wrote: > > > > > On Jul 17, 2014 11:32 PM, "Scott Arciszewski" <[email protected]> > > wrote: > > > > > > Hello, > > > > > > To expose an API that allows for sane implementations of elliptic curve > > > cryptography in PHP projects, I would like to propose/nominate the > > > inclusion of libsodium in PECL. > > > > > > https://github.com/jedisct1/libsodium-php This is a PHP extension > > written > > > by the maintainer of libsodium > > > https://github.com/jedisct1/libsodium > > > > > > The author (Frank Denis) can be contacted at [email protected], > > > [email protected], etc. > > > > I see no problem to have it in pecl. > > > > However the original author should do the request or are you part of the > > dev team? > > > > Cheers, > > Pierre > > > Think that would be better to use a different prefix for it's functions. I have already crypto extension on PECK. The currently released version uses Crypto namespace. I'm also constantly working on the branch 'next' (branch for the next release) where I implemented streams starting with crypto (at the moment just crypto.file://). I think that it would be a bit confusing for PECL users to have completely different extensions using the same prefixes... Cheers Jakub
