-
Notifications
You must be signed in to change notification settings - Fork 87
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.
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
Support encryption key in configuration #920
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, just a few suggestions and would like to see more tests.
Pull Request Test Coverage Report for Build 3111528733
💛 - Coveralls |
Pull Request Test Coverage Report for Build 3218450209
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One final question from me, otherwise it looks good.
I am writing to request clarification on the encryption key when passed, when added to realm later will it encrypt the existing realm? |
also the example from docs shows encrypting local realm // Generate encryption key
--
final key = List<int>.generate(64, (i) => Random().nextInt(256));
final encryptedConfig = Configuration.local([Car.schema],
// Include the encryption key in the configuration
encryptionKey: key);
final encryptedRealm = Realm(encryptedConfig); does it work on flexible sync as well @desistefanova |
Yes, it works with flexible sync and no - you cannot change the encryption of a file after it was created. You can use |
Support encryption key used to encrypt the entire [Realm].
Its length is forced to be 64bytes.
If null encryption is not enabled.
Fixes #88