If you want to generate signing certificate for your android app with OpenSSL, you can use library in this way:

Create a key:

  $ openssl genrsa -out android_distribution.key 2048

Generate a request:

  $ openssl req -new -key android_distribution.key -out android_distribution.csr

Self-signing:

  $ openssl x509 -req -days 10950 -in android_distribution.csr \
  > -signkey android_distribution.key -out android_distribution.crt

Transform .crt в .p12:

  $ openssl pkcs12 -export -in android_distribution.crt \
  > -inkey android_distribution.key -out android_distribution.p12

Don't forget to store your data somewhere safe.

UPDATE:

If you need keystore for example for phonegap build you can canvert your certificate:

  $ keytool -importkeystore -srckeystore android_distribution.p12 \
  > -srcstoretype PKCS12 -destkeystore android_distribution.jks -deststoretype JKS

The end.

In this article I would like to talk about my library called GizmoDuck. I enjoy creating mobile apps and often I user Adobe AIR in conjunction with Starling and Feathers. Application architecture is created with Robotlegs. In order to have Robotlegs working with graphical frameworks one needs to have connector. Recently I used Robotlegs 1.5.2 and connector which can be found here. I'm happy with MVCS pattern.

Time goes and nowadays we have Robotlegs 2.2.0 release with nice MVCS bundle in it. Unfortunately I did not find any port for existed MVCS bundle and decided to write my own. So, let's try to mix Feathers and Robotlegs 2 in the project called GizmoDuck.

This short record covers iOS certificate types and typical situations where you can use them. Nothing is really new here but it's just good to have it nearby. Also you will find steps to generate certificates with the help of openssl.

I'm not sure if it is possible to mix development and production certificates and provisioning file. It doesn't make any sense.