diff options
| author | Mark Rathjen <mrathjen@google.com> | 2017-01-19 04:10:37 +0000 |
|---|---|---|
| committer | Mark Rathjen <mrathjen@google.com> | 2017-01-19 04:10:37 +0000 |
| commit | d891f01d96cbaa3b1329c3d476084f3fedb30a89 (patch) | |
| tree | 59e6d86d0cb33b56576fd6bdb60d45cdb6207e00 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | be43257005d086ff7d93c15dae22ac40bc0d545e (diff) | |
Roll forward SSAID Migration to be Per App/User Unique Values.
SSAID is currently shared across all applications for each
user on the device, giving developers the ability to track
users across multiple applications. Using SSAID for tracking
is an abuse of the original intention of the SSAID and has
inherent privacy concerns.
This change will make the SSAID unique per application, per
user on a device. To not affect applications installed prior
to this change they will retain the legacy SSAID value until
uninstalled and reinstalled again.
Across subsequent installations the application will receive
the same SSAID as long as the package name and signature remain
consistent.
Tested manually the following cases:
- App retains the legacy sssaid after OTA.
- App gets a new ssaid upon post-OTA installation.
- App retrieves same ssaid across post-OTA unistall/reinstalls.
- Different Apps receive different ssaids.
- Factory reset removes ssaid data and generates a different
ssaid after App install.
- System retains legacy ssaid.
Bug: 34395671
Test: CTS tests passed, Manual testing passed
This reverts commit be43257005d086ff7d93c15dae22ac40bc0d545e.
Change-Id: Ibf20e7949304c30d65bb8aa24cdbbe6e104b1002
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions