Open Bug 1316366 Opened 8 years ago Updated 2 years ago

include information from update-settings.ini in update ping?

Categories

(Toolkit :: Application Update, defect, P3)

defect

Tracking

()

People

(Reporter: bhearsum, Unassigned)

References

Details

(Whiteboard: [fce-active-legacy])

While talking about bug 1316365, and why users may be in that state, catlee got wondering what mar channel IDs these users would accept, and we realized that we have no way of knowing. While we send the app.update.channel in the update ping, we don't send ACCEPTED_MAR_CHANNEL_IDS. We can typically infer the value based on the version+channel information, but not so much in frankenfox cases like bug 1316365.

Should we start sending ACCEPTED_MAR_CHANNEL_IDS and maybe other update-settings.ini information in the update ping?
Whiteboard: [fce-active]
The only info in update-settings.ini is ACCEPTED_MAR_CHANNEL_IDS.

I think it would be more valuable to lock down these settings where ever possible especially since according to bug 1312562 comment #6 it appears that the need for this arose from manually changing the values and there should be no other way for this to have happened beyond balrog serving the update to them.
Whiteboard: [fce-active] → [fce-active-legacy]
Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.