Attempt to feature-detect application-bound encryption for Chrome-based browser migrators
Categories
(Firefox :: Migration, task, P2)
Tracking
()
People
(Reporter: mconley, Unassigned)
Details
Chrome uses application-bound encryption which prevents us from importing passwords or payment methods directly. We currently hard-code behaviour into our migration tool to walk users through importing passwords from an exported CSV file, and also hide the payment method imports on Chrome.
Ideally, we could feature-detect Chrome-based browsers doing application-bound encryption at runtime, in case other Chrome-based browsers start suddenly using the same technique.
|
||
Comment 1•5 months ago
|
||
Tentatively setting to S2 given some of the other discussion also around enterprise use and the (apparent) gradual rollout for various other browsers, but I could believe this should be S3 instead. Mike, wdyt?
|
Reporter | |
Comment 2•5 months ago
|
||
I think this is S3 given our current definitions in https://wiki.mozilla.org/BMO/UserGuide/BugFields#bug_severity, at least from a user's perspective, and given our current (admittedly whack-a-mole) mitigations.
Description
•