True, but I thought it best to leave in the capability to read old legacy encrypted files in case for some reason the migration process (and re-encryption) fails, or is opted out of.

Currently when the user logs in and encryption is enabled, if a legacy key is found in the user data files, it will be stored in the session, and legacy decryption methods are available and unit tested to use that key, though I think currently they aren't implemented in the crypto stream or proxy classes (they could be quite easily, I think).

Obviously user data is paramount, and I wanted to leave some options in case things go wrong. I'm not sure what Frank's view is on this; we can always remove legacy decryption support if necessary.