Re: Idea for an easy to use encryption library, as well as a formlibrary
| From: | Philippe Jausions | Date: | Fri, 26 May 2006 14:14:28 +0000 |
| Subject: | Re: Idea for an easy to use encryption library, as well as a formlibrary | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-42637@lists.php.net to get a copy of this message | ||
davisneilp@mindspring.com wrote:
>It's a wrapper that simplifies implementing encryption into your application.
>
>
hmmm. In that case it's a little bit of a limited interest. Either you
provide a wrapper for all the encryptions and not only AES, or you'd
have to add a PHP-only AES encryption.
-Philippe
>-----Original Message-----
>
>
>>From: Philippe Jausions <Philippe.Jausions@11abacus.com>
>>Sent: May 24, 2006 5:59 PM
>>To: davisneilp@mindspring.com
>>Cc: pear-dev@lists.php.net
>>Subject: Re: Idea for an easy to use encryption library, as well as a formlibrary
>>
>>neil davis wrote:
>>
>>
>>>Hello all,
>>>I have a couple of libraries I've built that I'd like to see not go to
>>>waste.
>>>
>>>Encryption:
>>>I have an encryption library that is currently functional for AES. It
>>>supports building initialization vectors, hashes using mt_rand and all
>>>other functionality needed for encrypting and decrypting data using
>>>Rijndael. I would like to add this to pear, and over time support more
>>>than AES.
>>>
>>>As a user, I found the existing PHP functions to be a little complicated
>>>to understand, even for someone who's done this before in another
>>>language. This library makes it simple, without needing to understand
>>>how encryption works. I wrote it so I wouldn't need to reinvent the
>>>wheel if I need to do this again a year from now for a different
>>>project.
>>>
>>>
>>>
>><snip>
>>
>>Is it a PHP-only implementation or a wrapper around MCrypt? I've just
>>recently worked on Crypt_Blowfish to add support for MCrypt. Obviously a
>>PHP-only code will be slower than C-compiled library, so it makes sense
>>to use MCrypt whenever possible.
>>
>>It would also be best to align your API to one of the existing Crypt
>>package.
>>
>>
>>>Both of these will need to be reformatted by me and inline comments
>>>added so it will take some time to put them into the PEAR mold, but I
>>>think they'd be worthy additions to the PEAR collection of open source
>>>libraries.
>>>
>>>My motivation is that the project was cancelled, but the libraries are
>>>very cool. I'd hate to see either of these collecting dust and would
>>>like to give them to PEAR and participate in maintaining them.
>>>
>>>
>>-Philippe
>>