[google-appengine] Re: PyCrypto

Depends. Depends on the module you want to use. Could be For example: from Crypto.Hash import MD5 Or: from Crypto.Cipher import DES See: http://www.dlitz.net/software/pycrypto/ That's what I learnd by google 'python crypto'. The rest is try&error. --~--~-~--~~~--

[google-appengine] Re: PyCrypto

Ahh OK thank you very much, so PyCrypto isn't part of the AppEngine SDK download right ? /Henrik Schack On Aug 1, 10:42 am, Holger wrote: > Depends. > > Depends on the module you want to use. > > Could be For example: > from Crypto.Hash import MD5 > > Or: > from Crypto.Cipher import DES > > Se

[google-appengine] Re: PyCrypto

Really don't know. If it is part, you are able to import it (import is needed anyway), If not, you first have to install their code and than import it into your script. And anyway it's a python item not an appengine one. (You remember, before installing appengine you had to install python 25 an

[google-appengine] Re: PyCrypto Access

Hi Dan, Just the same as you would in any other app using PyCrypto: Consult the relevant documentation. PyCrypto puts all the relevant modules under the 'Crypto' module. -Nick Johnson --~--~-~--~~~---~--~~ You received this message because you are subscribed to t

[google-appengine] Re: PyCrypto Access

The problem is that I don't see a file or a directory named 'Crypto' anywhere on my system (it's certainly not in google_appengine/lib with antlr3 and django) . Where is it supposed to be? On May 5, 5:04 am, "Nick Johnson (Google)" wrote: > Hi Dan, > > Just the same as you would in any other ap

[google-appengine] Re: PyCrypto Access

PyCrypto is a third-party library. If it is installed, it will be in your Python install's site-packages directory, not under the App Engine SDK. -Nick Johnson --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google

[google-appengine] Re: PyCrypto Access

What?? How does this reconcile with the 1.2.1 announcement: App Engine includes a custom version of the Python Cryptography Toolkit, also known as PyCrypto. The version included with App Engine is based on pycrypto 2.0.1. This is not the latest version, but should be largely compatib

[google-appengine] Re: PyCrypto Access

Seems there is native code there for various ciphers and hashes. Just include the Python parts of PyCrypto in your project. Try running: [ x for x in sys.modules.keys() if 'ypt' in x ] on http://shell.appspot.com David 2009/5/5 Devel63 : > > What??  How does this reconcile with the 1.2.1

[google-appengine] Re: PyCrypto Access

The libraries are installed on the App Engine production servers. They are not part of the SDK, so they're not on your machine unless you installed them, the same as the other third party libraries usable with App Engine. On May 5, 1:38 pm, Devel63 wrote: > What??  How does this reconcile with t

[google-appengine] Re: PyCrypto Access

OK, I hear what you all are saying: I need to install the libraries on my dev server, but not upload them to my workspace because they will already be accessible there. However, I don't know why people on this thread keep saying that this is the way it works with all the other 3rd party libraries

[google-appengine] Re: PyCrypto Access

Doesn't seem to work on http://shell.appspot.com I can import a module (e.g., from Crypto.Cipher import DES), but when I try to use it I get all sorts of errors about not being able to pickle it (e.g., obj=DES.new('abcdefgh', DES.MODE_ECB). I picked those 2 lines (and others) because they are st

[google-appengine] Re: PyCrypto Access

Hi The approach makes heaps of sense PIL, Imaging support is done the same way, you need PIL installed locally to support the limited image api, and google have a service that performs the same thing in their infrastructure. They won't let you run the full pycrypto library as it has lot of 'c'

[google-appengine] Re: PyCrypto Working?

Hi Dan, shell.appspot.com uses the Pickle module to persist objects between user requests. Evidently, PyCrypto objects are not picklable. This is not a problem using PyCrypto in your own code, unless you intended to pickle them. -Nick Johnson On Wed, May 6, 2009 at 3:25 AM, Devel63 wrote: > >

[google-appengine] Re: PyCrypto Access

This seems to be problem with shell.appspot.com (it tries to persist the DES object in session). On 5 Maj, 23:53, Devel63 wrote: > Doesn't seem to work onhttp://shell.appspot.com > > I can import a module (e.g., from Crypto.Cipher import DES), but when > I try to use it I get all sorts of errors

[google-appengine] Re: pycrypto 2.6.1 errors

Hey Mark, Usually, an issue like this should be reported to the Public Issue Tracker , but we can work on it here until something more concrete can develop to report. What command is producing this issue? Is this error message seen in produc

[google-appengine] Re: pycrypto 2.6.1 errors

Hey Mark, Any update on my last questions? Did you make a post to the Public Issue Tracker or would you like to keep corresponding here? Cheers, Nick Cloud Platform Community Support On Tuesday, December 6, 2016 at 6:41:40 AM UTC-5, Mark Cummins wrote: > > The new Python SDK (1.9.49) includes

[google-appengine] Re: pycrypto 2.6.1 errors

We see this issue in production. It happens whenever we import pycrypto. We couldn't find any solution, so we've reverted to the old version on the assumption that this is an SDK problem. On Tuesday, 20 December 2016 21:54:20 UTC, Nick (Cloud Platform Support) wrote: > > Hey Mark, > > Any updat

[google-appengine] Re: pycrypto 2.6.1 errors

@Mark: I'm a little bit confused since I don't think you can set the SDK version used by the app in production. Rather, it is always auto-upgraded to the latest. It seems that the Python build used by Google uses an old(er) version of the GMP library. See this Ansible issue for more details: h

[google-appengine] Re: pycrypto 2.6.1 errors

> > @Mark: I'm a little bit confused since I don't think you can set the SDK > version used by the app in production. Rather, it is always auto-upgraded > to the latest. > Ah, no, I mean that we reverted to the old PyCrypto version, rather than the SDK version. Thank you very much for the wor

[google-appengine] Re: pycrypto 2.6.1 errors

This has been acknowledged and an issue has been filed in the tracker: https://code.google.com/p/googleappengine/issues/detail?id=13468 On Friday, December 23, 2016 at 7:35:45 AM UTC-5, Mark Cummins wrote: > > @Mark: I'm a little bit confused since I don't think you can set the SDK >> version use

[google-appengine] Re: PyCrypto and user passwords.

Really? No suggestions? I settled on multiple iterations of SHA256. But I note that the version of PyCrypto on app engine doesn't include the Crypto.Random submodule, so it's impossible to even generate a cryptographically satisfactory salt. Can someone on the App Engine team comment on whether C

[google-appengine] Re: PyCrypto and user passwords.

On Mar 15, 3:14 pm, "Ikai Lan (Google)" wrote: > Wow, there are no pure Python bcrypt libraries. I was just talking to Nick > (he's sitting next to me today, normally he's in Sydney) and he mentions > that there should be a pure Python implementation of pbkdf2, which is just a > generalization o

Re: [google-appengine] Re: PyCrypto and user passwords.

> Can someone on the App Engine team comment on whether Crypto.Random > will ever be available? > Did you try to include your own PyCrypto version? No, because you can't. PyCrypto requires native code, and thus must be supported directly by the App Engine team. App Engine does provide PyCrypto

Re: [google-appengine] Re: PyCrypto and user passwords.

On Mon, Mar 14, 2011 at 5:42 PM, Dave Peck wrote: > Really? No suggestions? > > I settled on multiple iterations of SHA256. But I note that the > version of PyCrypto on app engine doesn't include the Crypto.Random > submodule, so it's impossible to even generate a cryptographically > satisfactory

Re: [google-appengine] Re: PyCrypto and user passwords.

You can generate secure random numbers on AppEngine via os.urandom(n) to get n-bytes suitable for cryptographic use. Try it on shell.appspot.com This issue http://code.google.com/p/googleappengine/issues/detail?id=1055 has more details, especially comments #1 and #4 from a Googler way back in 2009

Re: [google-appengine] Re: PyCrypto and user passwords.

On Mon, Mar 14, 2011 at 5:59 PM, Dave Peck wrote: > Can someone on the App Engine team comment on whether Crypto.Random >> will ever be available? >> > Did you try to include your own PyCrypto version? > > > No, because you can't. PyCrypto requires native code, and thus must be > supported direc

Re: [google-appengine] Re: PyCrypto and user passwords.

Wow, there are no pure Python bcrypt libraries. I was just talking to Nick (he's sitting next to me today, normally he's in Sydney) and he mentions that there should be a pure Python implementation of pbkdf2, which is just a generalization of repeated SHA1 hashing with a salt. http://news.ycombina