Fix fs-verity API for secondary users
createFsveritySetupAuthToken previously takes a userId in order to handle the app uid, ended up did it incorrectly. Since the authentication in question is really to compare the calling uid with the file owner's uid, userId doesn't really matter. Drop it and fix the range check accordingly. Ignore-AOSP-First: cross-repo API change Bug: 319280249 Test: atest FsVerityTest Test: atest FsVerityTest --user-type secondary_user Test: atest installd_service_test Change-Id: I4090792afaf05c3dff5cb34731ef7030243196c2 Merged-In: I4090792afaf05c3dff5cb34731ef7030243196c2
Loading
Please register or sign in to comment