Some time ago, I pitched the idea of implementing certificate/pubkey pinning in our apps. Altho the idea was well received, I wanted to come with better data to understand the implications of this implementation.
When a client talk to a server, it use TLS to cipher and authentify the connection with the server. The authentification (making sure you are talking to the server you intend to speak to), is done by the server presenting a certificate to the client.
To summary, a certificate contains:
Consider this code (description bellow):
Sounds simple right ?
However, the results can be a little bit unexpected:
What’s going on here ?
If you can read a title, you probably know what’s going on:
“I don’t know what it does. It predicts branches”
“It’s a good thing”
Steve jobs, 2003
Thank you Steve !
I’m not sure if this was enough, so I’ll try to explain a bit…
`UIImagePickerController` is great, and comes with some advantages (reduced code size, no permissions needed), but comes with some serious flaw, such as limited integrations, no customisations, and no multi assets picking.
While there a (a lot) of Assets Picker libraries that offer very good alternatives, we wanted to go a bit further:
- Let you (optionally) write your own view controllers using our MVVM architecture
- Customisable header cell
- Streamlined, background download of cloud assets
- Dynamically reloading the collections when the user update them
Simply create the view controller and setup the…