Re: [PEAR-QA] Crypt_RSA

Awesome :)



On Tue, Apr 13, 2010 at 1:09 AM, Jim Wigginton <[email protected]> wrote:

> On Mon, Apr 12, 2010 at 4:49 AM, Daniel O'Connor
> <[email protected]> wrote:
> > On Wed, Feb 24, 2010 at 3:40 PM, Daniel O'Connor <
> [email protected]>
> > wrote:
> >>
> >>
> >> On Wed, Feb 24, 2010 at 3:41 AM, John McKinzey <[email protected]
> >
> >> wrote:
> >>>
> >>> My thoughts: PEAR should adopt the Crypt_RSA class at
> >>> phpseclib.sourceforge.net as Crypt_RSA2.  If "[you] don't have time to
> >>> [add new features] and [you] don't know RSA well enough" then your
> >>> ability to fix all but the most superficial of bugs is suspect.
> >>> Besides, the phpseclib Crypt_RSA package fulfills several open feature
> >>> requests for the PEAR package that, by your admission, you'd be
> >>> unwilling and unable to do.
> >>
> >> Ah, perhaps; but it's LGPL'd; and the patches / changes which appear to
> >> have been applied to it have never been pushed back upstream afaict -
> ie:
> >> the maintainer hasn't bugged us with.. .bugs :)
> >>
> >> Seems odd, since he's a pear dev (http://pear.php.net/user/terrafrost)
> >>
> >> *nudge terrafrost, nudge*
> >>
> >> Anyway, there's nothing to stop both of them becoming devs on the
> package
> >> :)
> >
> > Let's try this email address.
> >
> > psst, Jim; Does your Crypt_RSA have any common heritage with the PEAR
> > version?
> >
> > Feel like making http://phpseclib.sourceforge.net/ installable via a
> pear
> > channel? (something like http://www.pirum-project.org/ makes it pretty
> > simple these days)?
> > If so, I'm more than happy to point users of PEAR's Crypt_RSA over to
> > phpseclib.
> >
> >
>
> Sorry for not replying to the last email - I got it but it, I guess,
> got lost in a deluge of other email.
>
> Anyway, my Crypt_RSA was developed from the ground up, completely
> independent of the one in PEAR.
>
> I do plan on creating a PEAR channel for the 0.2.1 release of
> phpseclib, which will hopefully happen later this month.  I'll send an
> email here when that's done?
>