Make sure SharedModelTypeProcessor correctly handles reencryption |
|||
Issue descriptionSharedModelTypeProcessor (SMTP) maintains one encryption key per model type, it is stored in ModelTypeState. When encryption key is changed by remote client SMTP reencrypts all the entities it maintains (SharedModelTypeProcessor::RecommitAllForEncryption). Typically though by the time the client gets to reencryption all the entities are already encrypted with new key. This process will repeat once per client resulting in redundant commit traffic to the server. Processor needs to remember with which key each entity was encrypted. Encryption key name should be stored in EntityMetadata.
,
Jan 17 2018
,
Apr 9 2018
pavely@: Is it accurate that the only result of this is issue is redundant traffic? Assuming yes, adjusting priority.
,
Apr 13 2018
Yes, the impact of this issue is redundant commit traffic during reencryption. Fixing this issue would involve maintaining key name (or reference to it) in each entity's metadata. |
|||
►
Sign in to add a comment |
|||
Comment 1 by s...@chromium.org
, Jan 17 2018Status: Untriaged (was: Available)