Closed Bug 1740226 Opened 3 years ago Closed 2 years ago

Enable monitoring login attempts to mark a site high-value

Categories

(Core :: DOM: Content Processes, task, P3)

Unspecified
Android
task

Tracking

()

RESOLVED FIXED
100 Branch
Tracking Status
firefox-esr91 --- wontfix
firefox97 --- wontfix
firefox98 --- wontfix
firefox99 --- wontfix
firefox100 --- fixed

People

(Reporter: dimi, Assigned: farre)

References

Details

(Whiteboard: [fission:android:m3])

Attachments

(1 file)

In Bug 1729640, we introduced fission.highValue.login.monitor pref to add high-value permission when a login attempt is detected. Note that turning on the pref doesn't necessarily mean we start to isolate high-value sites. Instead, the pref should be turned on prior to enabling isolating high-value sites feature so when the feature is on, we will have the permission stored in the permission manager.

Hi Chris, I guess this is something you should be aware of and decide the timeline to enable it.

Flags: needinfo?(cpeterson)

the pref should be turned on prior to enabling isolating high-value sites feature so when the feature is on, we will have the permission stored in the permission manager.

Is this a new Android app permission (that will cause the Android app updater to ask the user to accept this permission) or just new metadata in Firefox's own site permissions manager?

Severity: -- → N/A
Fission Milestone: --- → Future
Flags: needinfo?(cpeterson) → needinfo?(dlee)
Priority: -- → P3
Whiteboard: [fission:android:m3]

farre told me this feature is doesn't require a new Android app permission. It adds a new permission to identify high-value sites in the Firefox permission manager. Since the new permission is set by a callback at site login time, the sooner we enable this login monitoring, the more high-value sites will be flagged in the permission manager. So we should enable this for Android (only) soon.

Flags: needinfo?(dlee)
OS: Unspecified → Android
Depends on: 1741610
Fission Milestone: Future → ---
Assignee: nobody → afarre

Setting status-firefox99=wontfix because it's too late to land in Nightly 99. The Nightly 99 code freeze starts tomorrow and merges to Beta next week.

There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:farre, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit auto_nag documentation.

Flags: needinfo?(agi)
Flags: needinfo?(afarre)
Pushed by afarre@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/420c2ea69d18
Enable monitoring login attempts to mark a site high-value. r=agi
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
Flags: needinfo?(agi)
Flags: needinfo?(afarre)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: