EncryptedRandomAccessThing and other API's from my GSoC project

This is EncryptedRandomAccessThing which toad will be using in his db4o replacement along with around half of the API I have written this summer for GSoC. ERAT is dependent on the three API's included. I am still in the process of writing docs and unit tests for ERAT but the other three APIs are complete. These will be done this weekend. This requires BouncyCastle 1.51 (#271).
It makes me nervous that this is outside the critical section. I can imagine that this could lead to writes being incompletely applied. Is there a reason this is safe? I'd prefer moving it to when the lock is still held.