When Kristian implemented database unencryption, I believe that he just piggybacked on top of the existing re-encryption logic. This means that unencryption records an EncryptContainerUndoOperation in the transaction log just as re-encryption does. Does anyone see a compelling reason to create a new UnencryptContainerUndoOperation for unencryption in order to distinguish it from re-encryption?

Thanks,
-Rick

Reply via email to