New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 727874 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Make sure SharedModelTypeProcessor correctly handles reencryption

Project Member Reported by pav...@chromium.org, May 30 2017

Issue description

SharedModelTypeProcessor (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.
 

Comment 1 by s...@chromium.org, Jan 17 2018

Owner: pav...@chromium.org
Status: Untriaged (was: Available)
Assigning to pavely@ for re-triaging.

Comment 2 by pav...@chromium.org, Jan 17 2018

Labels: SyncHandoff2018
Owner: ----
Status: Available (was: Untriaged)
Labels: -Pri-2 Pri-3
pavely@: Is it accurate that the only result of this is issue is redundant traffic?

Assuming yes, adjusting priority.

Comment 4 by pav...@chromium.org, 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