Fwd: Re: [dev] Horde_Cipher et al;

FYI ----- Forwarded message from mike@graftonhall.co.nz ----- Date: Sun, 27 Jul 2003 10:00:30 +1200 From: Mike Cochrane <mike@graftonhall.co.nz> Reply-To: Mike Cochrane <mike@graftonhall.co.nz> Subject: Re: [dev] Horde_Cipher et al; To: dev@lists.horde.org > ----- Message from davey@php.net --------- > > > >The code is fine. What's needed is to identify any Horde dependencies and to > get > >them submitted to PEAR. > > > >I'd be very reluctant to submit them as seperate libraries, instead of as > the > >whole Cipher/Crypt packages. > > > The reason for this is that there is existing Crypt_* packages, and > putting this into PEAR as-is would break that sort of, in that the > existing packages are stand-alone and these are not. :Like I said, I > like the idea of having it all in one, but it just doesn't fit into PEAR > like that. I will bring this up on the pear-dev ML and see what they > think should be done. > I would not support it if the Horde_Cipher class was split into seperate packages. The classes were never designed to work that way. Without the blockmode classes the cipher classes are useless and vice-vera. You need both to be able to do anything usefull. Horde_Cipher currently depends on Crypt_Rc4 for RC4 encryption. Horde_Cipher would obsolete Crypt_Crypt (never released) and Crypt_CBC. - Mike :-) -- Horde developers mailing list Frequently Asked Questions: http://horde.org/faq/ To unsubscribe, mail: dev-unsubscribe@lists.horde.org ----- End forwarded message ----- -chuck -- Charles Hagenbuch, <chuck@horde.org> They're just looking at a wall of meat.