New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update README with usage strategy #14

Open

ronaldtse opened this issue Jun 9, 2017 · 1 comment

Milestone

Contributor

ronaldtse commented Jun 9, 2017

Explain strategy first, add concrete details as tool functionality gets implemented.

The “strategy” doesn’t change over time and is roughly like this:

In the project, create fields for new encrypted values using regular Rails migration(s).
Run stand-alone Transcryptor against the prepared database(s). This step should fail safe.
Once everything settles, create migration(s) to remove old encrypted fields/data.

Contributor Author

ronaldtse commented Jun 9, 2017

The point is there are two use cases of transcryptor and we should separate them.

Infrequent batch use: migrating from one encryption scheme to another one, maybe only once. There's no need to include transcryptor in the bundle.
Automated re-encryption: Clean and understandable model for recurring re-encryptions #12

ribose-jeffreylau added this to the 1.0 milestone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment