On Tue, 5 Mar 2002, Joseph Tate wrote: > Well, J Smith has mentioned Crypto++. I haven't looked into it, but that > sounds like a good little module as a substitute for mcrypt. If he truly is > working on a php extension using it, then it's purely acedemic to add it to > your module.
IMO, if there will be an interface to crypto++ it should be merged into the current mcrypt one, forming together a new combined module. (Just like Sterling is trying to do for XSLT). Derick > > > -----Original Message----- > > From: Keyser Soze [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, March 05, 2002 1:19 PM > > To: Joseph Tate; Brad Fisher; [EMAIL PROTECTED] > > Cc: [EMAIL PROTECTED] > > Subject: Re: [PHP-DEV] New Module > > > > > > I agree, so I think this module could be packaged with a default mycrypt > > library to make this easier > > > > Any idea? > > > > Keyser Soz > > > > > > ----- Original Message ----- > > From: "Joseph Tate" <[EMAIL PROTECTED]> > > To: "Keyser Soze" <[EMAIL PROTECTED]>; "Brad Fisher" > > <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > > Cc: <[EMAIL PROTECTED]> > > Sent: Tuesday, March 05, 2002 3:15 PM > > Subject: RE: [PHP-DEV] New Module > > > > > > > What Brad is suggesting doesn't take away from your module, > > just makes it > > > easier to use from php land. No need to write your own crypt > > functions in > > > C, just write them in PHP and use them as callbacks. Of course leaving > > that > > > option for advanced users is a good idea. I personally don't > > think that I > > > would be writing custom crypt functions, so I would like a > > crypto++ plugin > > > to do that for me. > > > > > > Joseph > > > > > > > -----Original Message----- > > > > From: Keyser Soze [mailto:[EMAIL PROTECTED]] > > > > Sent: Tuesday, March 05, 2002 1:03 PM > > > > To: Brad Fisher; [EMAIL PROTECTED] > > > > Cc: [EMAIL PROTECTED] > > > > Subject: Re: [PHP-DEV] New Module > > > > > > > > > > > > but that's what my module is meant for > > > > > > > > Keyser Soze > > > > > > > > ----- Original Message ----- > > > > From: "Brad Fisher" <[EMAIL PROTECTED]> > > > > To: <[EMAIL PROTECTED]> > > > > Cc: <[EMAIL PROTECTED]> > > > > Sent: Tuesday, March 05, 2002 3:03 PM > > > > Subject: Re: [PHP-DEV] New Module > > > > > > > > > > > > > > > > > > J Smith wrote: > > > > > > > > > > > I hesitate to mention this because I don't want to get stuck > > > > in a corner > > > > > > here, but I've been working on and off on a PHP encryption > > > > extension for > > > > > > precisely the reasons you mention. I'm using Crypto++, a > > public ... > > > > > > > > > > This sounds to me like one of the better ways to do it. > > Just have an > > > > extension > > > > > that does two-way encryption, and supports several different > > algorithms. > > > > For > > > > > those people who whant to define their own algorithms, why not > > > > have a way > > > > to > > > > > register a new crypt/decrypt callback methods either > > developed in PHP > > or > > > > > loadable module? Something like: > > > > > > > > > > bool crypto_register_algorithm(string name, function &crypt, > > function > > > > > &decrypt) > > > > > > > > > > Then crypt and decrypt could have function headers similar > > to (perhaps > > > > this is > > > > > oversimplified): > > > > > > > > > > string crypt(string data, mixed key) > > > > > > > > > > I don't think the module would need to write configuration > > files, etc. > > > > That > > > > > could be handled with PHP by the developer, or by another PHP > > > > > extension/function which can write such files. > > > > > > > > > > Just babbling, > > > > > -Brad > > > > > > > > > > > > > > > > > > > > -- > > > > > PHP Development Mailing List <http://www.php.net/> > > > > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > > > > > > > > > > > > -- > > > > PHP Development Mailing List <http://www.php.net/> > > > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > > > > -- > > > PHP Development Mailing List <http://www.php.net/> > > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > > > > -- > > PHP Development Mailing List <http://www.php.net/> > > To unsubscribe, visit: http://www.php.net/unsub.php > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php > -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
