Open Bug 1657536 Opened 5 months ago Updated 3 months ago

Store the fact a record is a tombstone in the plaintext part of the payload

Categories

(Firefox :: Sync, enhancement)

enhancement

Tracking

()

ASSIGNED

People

(Reporter: markh, Assigned: markh)

Details

Attachments

(1 file)

We can already deduce it with a high degree of reliability simply by looking at the size of the record, so to help the server team avoid deducing, let's just have the deleted flag in the plain-text. We can also keep it in the encrypted payload, at least for the next few years.

Assignee: nobody → markh
Status: NEW → ASSIGNED

We'll need to confirm that both Python and Rust sync servers gracefully handle this value before landing this (their might "gracefully handle" it by ignoring it, which is find...but we don't want to them to e.g. return a "400 Bad Request" because of the unexpected plaintext field)

A quick manual test shows it works with sync-1-us-west1-g (which is spanner, right?) and with sync-719-us-west-2

There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:markh, could you have a look please?
For more information, please visit auto_nag documentation.

Flags: needinfo?(markh)

Did we decide that we don't really need this after all?

(In reply to Ryan Kelly [:rfkelly] from comment #5)

Did we decide that we don't really need this after all?

Doing this in app-services in a non-hacky way is tricker than I expected, so we agreed to deprioritize that - and I don't think it's worth landing this until we are ready to land it there.

Flags: needinfo?(markh)

Echo-ing what Mark said; it's something that be nice to have on the sync storage side, but re:priority if it's non trivial work on the client side, we're good to de-prioritize for now.

You need to log in before you can comment on or make changes to this bug.