The easiest way to check is to look at embedded.mobileprovision ([[NSBundle mainBundle] pathForResource:@”embedded.mobileprovision” ofType:nil]): It’s a bit of a pain to parse since it’s a signed plist (PKCS#7 signed data, according to openssl asn1parse -inform der), but a bad hack is to just look for <plist and </plist>. Development contains UDIDs and <key>get-task-allow</key><true/> Ad Hoc … Read more
The common name attribute in a Distinguished Name is encoded as: X520CommonName ::= CHOICE { teletexString TeletexString (SIZE (1..ub-common-name)), printableString PrintableString (SIZE (1..ub-common-name)), universalString UniversalString (SIZE (1..ub-common-name)), utf8String UTF8String (SIZE (1..ub-common-name)), bmpString BMPString (SIZE (1..ub-common-name)) } where ub-common-name is 64. The last three encodings allow the use of all Unicode code points (using UTF-16 for … Read more
If you use ASN.1 with Unaligned PER, and define your data types using the appropriate constraints (e.g., specifying lower/upper bounds for integers, upper bounds for the length of lists, etc.), your encodings will be very compact. There will be no bits wasted for things like alignment or padding between the fields, and each field will … Read more
IETF PKIX (latest version RFC 5280) is a well accepted profile for certificates. From section 4.1.2.4, the following fields must be supported (I’ve added between parenthesis is the OpenSSL long and optional short name): country (countryName, C), organization (organizationName, O), organizational unit (organizationalUnitName, OU), distinguished name qualifier (dnQualifier), state or province name (stateOrProvinceName, ST), common … Read more
ASN.1 is an ISO/ISE standard. It has a very readable source language and a variety of back-ends, both binary and human-readable. Being an international standard (and an old one at that!) the source language is a bit kitchen-sinkish (in about the same way that the Atlantic Ocean is a bit wet) but it is extremely … Read more
You can do this conversion with the OpenSSL library. Windows binaries can be found here. Once you have the library installed, the command you need to issue is: openssl x509 -in mycert.crt -out mycert.pem -outform PEM
Your keys may already be in PEM format, but just named with .crt or .key. If the file’s content begins with —–BEGIN and you can read it in a text editor: The file uses base64, which is readable in ASCII, not binary format. The certificate is already in PEM format. Just change the extension to … Read more