Thanks Barry.

I updated issue http://code.google.com/p/googleappengine/issues/detail?id=996
and encourage others to do so stressing the importance of a fast
implementation.

On Jun 12, 8:22 pm, Barry Hunter <barrybhun...@googlemail.com> wrote:
> On 12/06/2009, gae123 <pa...@gae123.com> wrote:
>
>
>
> >  Nick,
>
> >  if I understand correctly the pycrypto implementation is in Python and
> >  I have found this very slow in the past. Are there any plans for
> >  support for a native/C based encryption library?
>
> Check the issue tracker, and add a suggestion if it not there already.
> Not really meaning to answer for Google, but they rarely reveal plans.
> (except at the most basic level)
>
>
>
>
>
>
>
> >  Thanks
>
> >  On Jun 11, 2:11 am, "Nick Johnson (Google)" <nick.john...@google.com>
> >  wrote:
>
> > > Hi Karl,
>
> >  > I'm not aware of any pure-Python implementations of bcrypt. However,
> >  > pycrypto is supported on App Engine, which supports many of the same
> >  > operations and algorithms.
>
> >  > -Nick Johnson
>
> > > On Thu, Jun 11, 2009 at 10:09 AM, Karl <kp8...@gmail.com> wrote:
>
> >  > > Are there any implementations of bcrypt that work on google app
> >  > > engine?
>
> >  > > The py-bcrypt package (http://www.mindrot.org/projects/py-bcrypt/)
> >  > > uses a C backend, so it can't be deployed on GAE.
>
> >  > > Are there any pure Python implementations of bcrypt?
>
> >  > > Thanks,
>
> > > > Karl- Hide quoted text -
>
> >  > - Show quoted text -
>
> --
> Barry
>
> -www.nearby.org.uk-www.geograph.org.uk-- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to