First part of a user guide for GCE in jclouds

Changed the wording.

To use it with a password I think one will can use a third-party library to handle P12 files - AFAIK jclouds itself doesn't support it out of the box, but there should be a lot of available libraries.

Note that if you store the password on the server for use by automated programs, it only provides security through obscurity - all the data to get the private key is still available to someone who compromises the system.

So I guess the answer what people would do in a production environment depends very much on the threat model. I'd expect some people wouldn't care if keys are leaked after the system got compromised (because they would rebuild the whole deployment in such a case) and will store everything without passwords while others would accept only tamper-proof hardware crypto card. By "you might not do in a production environment" I didn't mean this is a crazy thing to do, but it's not something that will work for everyone and I actually don't have the experience if this would work for the majority of people. Maybe it could be formulated better?