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
