Nick Alexander ffc393b56c Bug 1775132 - Part 2: Allow background tasks to have non-ephemeral persistent profiles. r=mossop ... This is a little tricky since some behaviour must be in the profile service while some is more naturally in the background tasks mechanism. Essentially, some background tasks will have a consistent profile location determined by their "profile prefix", which includes vendor, installation hash, and background task name. Right now, those tasks are determined by their task name, but in the future we could make this more flexible. A few technical notes: 1. I elected to not assume (or provide) a directory service provider in the relevant helper, mostly to ease future commits that might pull this functionality forward in the startup process. 2. These background task profiles are placed in "Background Tasks Profiles" on relevant platforms (non-Unix and macOS), sibling to "Profiles". 3. To avoid any possible vulnerability with predictable profile directories, these non-ephemeral background task profiles are salted. An entry is placed in the `BackgroundTasksProfiles` section of `profiles.ini` mapping the profile prefix to the relative salted path. Differential Revision: https://phabricator.services.mozilla.com/D149919		2022-07-13 20:12:12 +00:00
..
index.md	Bug 1775132 - Part 2: Allow background tasks to have non-ephemeral persistent profiles. r=mossop	2022-07-13 20:12:12 +00:00