[google-appengine] Re: pycrypto 2.6.1 errors

2016-12-25 Thread 'Adam (Cloud Platform Support)' via Google App Engine 
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 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 workaround.
>
> Best,
> Mak
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/abe04628-2e68-4ff1-b545-13eb01c13830%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: pycrypto 2.6.1 errors

2016-12-23 Thread Mark Cummins 

>
> @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 workaround.

Best,
Mak

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/c8bfa883-a325-4332-8278-1b8c9ee7e8f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: pycrypto 2.6.1 errors

2016-12-22 Thread Attila-Mihaly Balazs 
@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: 
https://github.com/ansible/ansible/issues/6941#issuecomment-89255641

There is also a suggestion on how to mute the warnings temporarily:

```
from Crypto.pct_warnings import PowmInsecureWarning
import warnings
warnings.simplefilter("ignore", PowmInsecureWarning)
```

Happy Holidays!
Attila

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/60324cb2-2017-476d-9379-bccd108f40b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: pycrypto 2.6.1 errors

2016-12-22 Thread Mark Cummins 
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 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 pycrypto update to 2.6.1.
>>
>> We've flipped over to the new library version, and we're now seeing 
>> errors like this:
>>
>>
>> 11:28:31.524/base/data/home/runtimes/python27/python27_lib/versions/third_party/pycrypto-2.6.1/Crypto/Util/number.py:57:
>>  
>> PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild using 
>> libgmp >= 5 to avoid timing attack vulnerability.
>> 11:28:31.524 _warn("Not using mpz_powm_sec. You should rebuild using 
>> libgmp >= 5 to avoid timing attack vulnerability.", PowmInsecureWarning)
>>
>>
>> It looks like this is a platform problem with the new 1.9.49 SDK? Or are 
>> we doing something to cause this?
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/691c8292-7bfe-4d82-8004-2835ccfd2528%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: pycrypto 2.6.1 errors

2016-12-20 Thread 'Nick (Cloud Platform Support)' via Google App Engine 
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 pycrypto update to 2.6.1.
>
> We've flipped over to the new library version, and we're now seeing errors 
> like this:
>
>
> 11:28:31.524/base/data/home/runtimes/python27/python27_lib/versions/third_party/pycrypto-2.6.1/Crypto/Util/number.py:57:
>  
> PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild using 
> libgmp >= 5 to avoid timing attack vulnerability.
> 11:28:31.524 _warn("Not using mpz_powm_sec. You should rebuild using 
> libgmp >= 5 to avoid timing attack vulnerability.", PowmInsecureWarning)
>
>
> It looks like this is a platform problem with the new 1.9.49 SDK? Or are 
> we doing something to cause this?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/89695daf-6078-4876-a5b5-0c1c55107be9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: pycrypto 2.6.1 errors

2016-12-15 Thread 'Nick (Cloud Platform Support)' via Google App Engine 
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 production, or 
development? What operating system are you running?

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 pycrypto update to 2.6.1.
>
> We've flipped over to the new library version, and we're now seeing errors 
> like this:
>
>
> 11:28:31.524/base/data/home/runtimes/python27/python27_lib/versions/third_party/pycrypto-2.6.1/Crypto/Util/number.py:57:
>  
> PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild using 
> libgmp >= 5 to avoid timing attack vulnerability.
> 11:28:31.524 _warn("Not using mpz_powm_sec. You should rebuild using 
> libgmp >= 5 to avoid timing attack vulnerability.", PowmInsecureWarning)
>
>
> It looks like this is a platform problem with the new 1.9.49 SDK? Or are 
> we doing something to cause this?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/92ef491f-88cf-4621-8724-d9849292cb7c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

2011-03-17 Thread Chris Lambacher 


On Mar 15, 3:14 pm, Ikai Lan (Google) ika...@google.com 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 of repeated SHA1 hashing with a salt.

There is a pure python pbkdf2 implementation: 
http://www.dlitz.net/software/python-pbkdf2/

A copy of that module is included in Beaker if you want to be able to
get it with easy_install/pip/buildout:
http://beaker.groovie.org/modules/pbkdf2.html#module-beaker.crypto.pbkdf2

-Chris

-- 
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.

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

2011-03-15 Thread Ovnicraft 
On Mon, Mar 14, 2011 at 5:42 PM, Dave Peck davep...@gmail.com 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 salt.

 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?

Regards,



 Thanks,
 Dave

 On Mar 10, 4:39 pm, Dave Peck davep...@gmail.com wrote:
  PyCrypto offers the blowfish cipher, but not thebcrypthash.
 
  What's the best way to store passwords on App Engine with PyCrypto?
 
  Thanks,
  Dave

 --
 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.




-- 
Cristian Salamea
@ovnicraft

-- 
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.

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

2011-03-15 Thread saidimu apale 
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.

It appears the GAE implementation of os.urandom is designed for
cryptographic use, though there is absolutely no documentation (apart from
the comment thread on the issue). Without knowing the details of the GAE
implementation, it is hard to tell if it will suit your needs.

saidimu

On Mon, Mar 14, 2011 at 6:59 PM, Dave Peck davep...@gmail.com 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 directly by the App Engine team.

 App Engine *does* provide PyCrypto on production, but it does *not*provide 
 the Crypto.Random submodule.

 Thus my question: might we ever expect to see it?

 Thanks,
 Dave

  --
 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.


-- 
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.

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

2011-03-15 Thread Ovnicraft 
On Mon, Mar 14, 2011 at 5:59 PM, Dave Peck davep...@gmail.com 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 directly by the App Engine team.


And try to use keyczar.


 App Engine *does* provide PyCrypto on production, but it does *not*provide 
 the Crypto.Random submodule.

 Thus my question: might we ever expect to see it?

 Thanks,
 Dave




-- 
Cristian Salamea
@ovnicraft

-- 
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.

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

2011-03-15 Thread Ikai Lan (Google) 
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.ycombinator.com/item?id=2177172

Ikai Lan
Developer Programs Engineer, Google App Engine
Blog: http://googleappengine.blogspot.com
Twitter: http://twitter.com/app_engine
Reddit: http://www.reddit.com/r/appengine



On Tue, Mar 15, 2011 at 11:59 AM, Ovnicraft ovnicr...@gmail.com wrote:



 On Mon, Mar 14, 2011 at 5:59 PM, Dave Peck davep...@gmail.com 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 directly by the App Engine team.


 And try to use keyczar.


 App Engine *does* provide PyCrypto on production, but it does *not*provide 
 the Crypto.Random submodule.

 Thus my question: might we ever expect to see it?

 Thanks,
 Dave




 --
 Cristian Salamea
 @ovnicraft

  --
 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.


-- 
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.

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

2011-03-14 Thread Dave Peck 
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 Crypto.Random
will ever be available?

Thanks,
Dave

On Mar 10, 4:39 pm, Dave Peck davep...@gmail.com wrote:
 PyCrypto offers the blowfish cipher, but not thebcrypthash.

 What's the best way to store passwords on App Engine with PyCrypto?

 Thanks,
 Dave

-- 
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.

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

2011-03-14 Thread Dave Peck 
 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 on production, but it does not provide the 
Crypto.Random submodule.

Thus my question: might we ever expect to see it?

Thanks,
Dave

-- 
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.

[google-appengine] Re: PyCrypto

2009-08-01 Thread Holger 

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 tryerror.


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

[google-appengine] Re: PyCrypto

2009-08-01 Thread Henrik Schack 

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 w...@arcor.de 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

 See:http://www.dlitz.net/software/pycrypto/

 That's what I learnd by google 'python crypto'. The rest is tryerror.
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

[google-appengine] Re: PyCrypto

2009-08-01 Thread Holger 

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 and there you
find crypt)

In the python folder Lib/test/ there is a file test_crypt.py. Maybe
this sample can help.

Which crypt code packet you want and need to use - see Python
documentation.

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

[google-appengine] Re: PyCrypto Access

2009-05-07 Thread Jarek Zgoda 

This seems to be problem with shell.appspot.com (it tries to persist
the DES object in session).

On 5 Maj, 23:53, Devel63 danstic...@gmail.com 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 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 straight out of the
 pycrypto examples.

 On May 5, 1:24 pm, Devel63 danstic...@gmail.com wrote:

  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.  To the
  contrary, antlr3, django v0.96, webob, and yaml ... everything else
  mentioned 
  onhttp://code.google.com/appengine/docs/python/tools/libraries.html
  ... gets installed with the SDK under the lib directory.

  I guess I can give it a go and see what happens, but it seems weird to
  me that Google would make a custom version, tell us it is not based on
  the latest release of the public version, and then not distribute it
  with the SDK as they have with every other incorporated library
  (unless there's some security reason not to do so).  So I guess we
  have to get it working locally, then upload and hope that it works
  with their modified and reduced functionality module, which we have no
  way of examining beforehand.

  On May 5, 12:57 pm, Wooble geoffsp...@gmail.com wrote:

   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 danstic...@gmail.com wrote:

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 compatible with more recent versions.

   http://code.google.com/appengine/docs/python/tools/libraries.html

On May 5, 7:54 am, Nick Johnson (Google) nick.john...@google.com
wrote:

 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 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
-~--~~~~--~~--~--~---

[google-appengine] Re: PyCrypto Access

2009-05-05 Thread Nick Johnson (Google) 

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 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
-~--~~~~--~~--~--~---

[google-appengine] Re: PyCrypto Access

2009-05-05 Thread Devel63 

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) nick.john...@google.com
wrote:
 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 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
-~--~~~~--~~--~--~---

[google-appengine] Re: PyCrypto Access

2009-05-05 Thread Nick Johnson (Google) 

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 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
-~--~~~~--~~--~--~---

[google-appengine] Re: PyCrypto Access

2009-05-05 Thread Devel63 

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 compatible with more recent versions.

http://code.google.com/appengine/docs/python/tools/libraries.html


On May 5, 7:54 am, Nick Johnson (Google) nick.john...@google.com
wrote:
 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 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
-~--~~~~--~~--~--~---

[google-appengine] Re: PyCrypto Access

2009-05-05 Thread David Wilson 

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 danstic...@gmail.com:

 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 compatible with more recent versions.

    http://code.google.com/appengine/docs/python/tools/libraries.html


 On May 5, 7:54 am, Nick Johnson (Google) nick.john...@google.com
 wrote:
 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
 




-- 
It is better to be wrong than to be vague.
  — Freeman Dyson

--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

[google-appengine] Re: PyCrypto Access

2009-05-05 Thread Wooble 

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 danstic...@gmail.com wrote:
 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 compatible with more recent versions.

    http://code.google.com/appengine/docs/python/tools/libraries.html

 On May 5, 7:54 am, Nick Johnson (Google) nick.john...@google.com
 wrote:

  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 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
-~--~~~~--~~--~--~---

[google-appengine] Re: PyCrypto Access

2009-05-05 Thread Devel63 

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.  To the
contrary, antlr3, django v0.96, webob, and yaml ... everything else
mentioned on http://code.google.com/appengine/docs/python/tools/libraries.html
... gets installed with the SDK under the lib directory.

I guess I can give it a go and see what happens, but it seems weird to
me that Google would make a custom version, tell us it is not based on
the latest release of the public version, and then not distribute it
with the SDK as they have with every other incorporated library
(unless there's some security reason not to do so).  So I guess we
have to get it working locally, then upload and hope that it works
with their modified and reduced functionality module, which we have no
way of examining beforehand.


On May 5, 12:57 pm, Wooble geoffsp...@gmail.com wrote:
 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 danstic...@gmail.com wrote:

  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 compatible with more recent versions.

     http://code.google.com/appengine/docs/python/tools/libraries.html

  On May 5, 7:54 am, Nick Johnson (Google) nick.john...@google.com
  wrote:

   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 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
-~--~~~~--~~--~--~---

[google-appengine] Re: PyCrypto Access

2009-05-05 Thread Devel63 

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 straight out of the
pycrypto examples.


On May 5, 1:24 pm, Devel63 danstic...@gmail.com wrote:
 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.  To the
 contrary, antlr3, django v0.96, webob, and yaml ... everything else
 mentioned onhttp://code.google.com/appengine/docs/python/tools/libraries.html
 ... gets installed with the SDK under the lib directory.

 I guess I can give it a go and see what happens, but it seems weird to
 me that Google would make a custom version, tell us it is not based on
 the latest release of the public version, and then not distribute it
 with the SDK as they have with every other incorporated library
 (unless there's some security reason not to do so).  So I guess we
 have to get it working locally, then upload and hope that it works
 with their modified and reduced functionality module, which we have no
 way of examining beforehand.

 On May 5, 12:57 pm, Wooble geoffsp...@gmail.com wrote:

  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 danstic...@gmail.com wrote:

   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 compatible with more recent versions.

      http://code.google.com/appengine/docs/python/tools/libraries.html

   On May 5, 7:54 am, Nick Johnson (Google) nick.john...@google.com
   wrote:

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 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
-~--~~~~--~~--~--~---

[google-appengine] Re: PyCrypto Access

2009-05-05 Thread Tim Hoffman 

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'
so you can't deploy it and they
will have cut it down to what they can allow (ie no file writes,
socket connections etc, and whatever
cyphers and hashes they will support in the infrastructure)

Rgds

T

On May 6, 4:24 am, Devel63 danstic...@gmail.com wrote:
 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.  To the
 contrary, antlr3, django v0.96, webob, and yaml ... everything else
 mentioned onhttp://code.google.com/appengine/docs/python/tools/libraries.html
 ... gets installed with the SDK under the lib directory.

 I guess I can give it a go and see what happens, but it seems weird to
 me that Google would make a custom version, tell us it is not based on
 the latest release of the public version, and then not distribute it
 with the SDK as they have with every other incorporated library
 (unless there's some security reason not to do so).  So I guess we
 have to get it working locally, then upload and hope that it works
 with their modified and reduced functionality module, which we have no
 way of examining beforehand.

 On May 5, 12:57 pm, Wooble geoffsp...@gmail.com wrote:

  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 danstic...@gmail.com wrote:

   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 compatible with more recent versions.

      http://code.google.com/appengine/docs/python/tools/libraries.html

   On May 5, 7:54 am, Nick Johnson (Google) nick.john...@google.com
   wrote:

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 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
-~--~~~~--~~--~--~---