Closed Bug 906028 Opened 11 years ago Closed 11 years ago

Use encryption key(s) from Firefox Accounts in Sync 1.1

Categories

(Firefox :: Sync, defect)

Product:
Firefox
Component:
Sync
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: lhilaiel, Unassigned)

References

Details

(Whiteboard: [qa+])

A meta bug to hang this work off as we break it down. There's some research required to figure out if we can have different per-type keys with a reasonable amount of work - so that we would actually get recoverability. If we can't, the best approach might be, for the purposes of this milestone, to keep the status quo(ish) - treat everything as class B.
Blocks: 905997
Depends on: 904612
Whiteboard: [qa+]
Yes, we should use kB as the "sync key" in the Sync 1.1 client side implementation. That should result in the minimum amount of work to integrate with Sync 1.1 and I have rough understanding of how to make that happen.
Depends on: 909967
Depends on: 910479
Depends on: 907420
No longer depends on: 910479
No longer depends on: 904612
Depends on: 949699
No longer depends on: 949699
Blocks: 951486
No longer blocks: 905997
No longer depends on: 907420
Summary: [meta] Use encryption key(s) from Firefox Accounts in Sync 1.1 → Use encryption key(s) from Firefox Accounts in Sync 1.1
FWIW, a basic version of this is "kinda done" in elm right now.
This is on central now.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Component: Firefox Sync: UI → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.