Author Archives: lantean

Loading SecCertificateRef from PEM String

In order to load a PEM certificate, you’d probably wanna grab the PEM itself from your backend, right?.

You can do so, by means of this command:

openssl s_client -showcerts -host host.com -port 443

Once you’ve got the certificate, you should get rid of the Begin/End Certificate substrings.

Cocoa Snippet itself is quite easy:

[cc lang=”objc”]

NSData *rawCertificate = [[NSData alloc] initWithBase64Encoding:PlaintextCertificateString];
SecCertificateRef parsedCertificate = SecCertificateCreateWithData(NULL, (__bridge CFDataRef)rawCertificate);
[/cc]

That’s it. Don’t forget about checking expiration dates. Unfortunately, Apple’s API to do so is private, and i personally refuse to build OpenSSL into my app, just to check that.

Pushing a new CocoaPods Version with Trunk

CocoaPods is a useful dependency management tool for OSX and iOS. They’ve recently introduced some changes, to ease the process of publishing new versions of your Framework.

Just in case you’re lost, just like me, these are the commands required to push a new release:

[cc]
pod trunk register EMAIL@HERE.COM ‘Your Name’ –description=’MBP 15′
pod trunk me
pod trunk push FrameworkName.podspec.json
[/cc]

Note that after hitting trunk register, you’ll get an email to confirm your identity.

Codesign Check

Keychain access for iOS apps is tied up to the provisioning profile you use to sign the binary. So, what happens if you release a new build, signed using a different provisioning profile?.

Yes! your guess is accurate!. You loose access to anything you’ve stored in the keychain, resulting in (probably) deauthentication.

There is a command that allows you to verify the “Keychain Access Group” for a given executable. By means of this, you’ll be able to verify if your new release will have the same access than your previous build (assuming you also have that binary!).

Take notes…

codesign -d --entitlements - /path/AppName.OSX.1.0.2.xcarchive/Products/Applications/AppName.app/

Git toggled folders as submodules!?

Few days ago, i had to struggle with a strange scenario in which git began tracking a folder, as if it was a submodule.

Now, what’s strange with that?: i didn’t set any submodules!. My .gitmodule file was empty (in fact, i didn’t even have that file).

Thanks to this stackflow question, i ended up figuring out this solution:

git ls-files --stage | grep 160000
git rm --cached [Paths retrieved from the command above]

Hopefully, this will help another lost soul!