Re: [RFC] Horde_Cipher -> Crypt_Cipher

Quoting Davey <davey@php.net>: > Having had a look at Horde_Cipher, and knowing it would be useful in my > XML_Encrypt package, I would like some thoughts on releasing the current > version of Horde_Cipher as Crypt_Cipher in PEAR. AFAICT it has no Horde > dependencies and follows PEAR CS et al; To be clear, if this package is wanted by the PEAR community, we'll rename it as required, and then upload it to the PEAR site like we've done with VFS and XML_SVG. It won't be forked into PEAR CVS as well. > Firstly (and foremost IMO) we have Crypt_RC4 already, what should we do > about the redundancy? Leave the old package, but move new development to the new one, imho. > Secondly, the current Crypt_* cipher stuff (RC4, CBC, XTEA) are single > stand-alone packages, I can see about modifying Horde_Crypt to a) use > the current Crypt_RC4 instead of theirs and b) and also add the others > to it? I think a top-level Crypt api is needed in PEAR; if the current Crypt packages have a unified API, then we can merge them (keeping the old standalone packages for BC, but again, moving new development to the new common API package). If not, same thing, but we just leave the old packages. Working out the naming I'll leave to someone else for now. :) > One last thing, if this is done, should the various encryption drivers > provided with Horde_Cipher also be released as standalone packages so > that they can be used on their own like the current Crypt_* packages > aswell as with the Crypt_Cipher package... No, we should have one general umbrella package, that maintains the common API. -chuck -- Charles Hagenbuch, <chuck@horde.org> They're just looking at a wall of meat.