Stop mutating, evolve

RNCryptor Async

I have completed the major work for RNCryptor asynchronous operations on the async branch. This changes the API and the file format. I’ll be documenting this more formally within a few weeks, but here are the high points:

There are now separate RNCryptor and RNDecryptor objects (as well as RNOpenSSLEncryptor and RNOpenSSLDecryptor).

Aync usage looks like this:

RNEncryptor *encryptor = [[RNEncryptor alloc] initWithSettings:kRNCryptorAES256Settings
                                                       handler:^(RNCryptor *cryptor, NSData *data) {

You add data using addData:. handler may or may not be called once for every call to addData:. When you are done, you must call finish, at which point, handler will be called one last time. You can check this condition using cryptor.isFinished.

There is still synchronous access such as:

NSData *encryptedData = [RNEncryptor encryptData:data

I have dropped all the URL, file and stream APIs. Please let me know if you have a general use case where you would like them. I don’t mind creating some convenience methods, but the convenience methods in the original interface were becoming too numerous and that complicates testing. Input on this is welcome. I found that many people were either doing very small things where synchronous NSData is good, or they were using NSURLConnection, where you need all the callbacks (to handle redirects, authentication, etc.), so I’ve supported those two cases the most.

By default, handler is called on the GCD queue that the cryptor was created on. You can modify this by setting responseQueue.

Input on the API is welcome. I’m leaving it on the async branch until people have time to play with a little bit and I have time to document it fully.