Age | Commit message (Collapse) | Author |
|
NO_IFTTT=Does not modify RoleParser logic
RelNote: N/A
Bug: 376728836
Flag: EXEMPT refactor
Test: build
Change-Id: I603adc9e8e584bbadda49903bca6c3aba30cad89
|
|
7a14ab0dbd
Original change: https://android-review.googlesource.com/c/platform/packages/modules/Permission/+/2999660
Change-Id: I6961a7362ca1fcf494e081363781a0e41b4f2793
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
system image which is declared in Android.bp should include the module.
so define phony module 'aosp_mainline_module' in
package_modules/common/build for aggregation.
Bug: 321000103
Test: m nothing
Change-Id: Iad84decf54f255a312231e9edd4745a118815b72
|
|
Original change: https://android-review.googlesource.com/c/platform/packages/modules/Permission/+/2939780
Change-Id: Ia9c34645719248e42236d8e7420943e59527ad81
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
|
|
This CL is created as a best effort to migrate test targets
to the new android ownership model. If you find incorrect or unnecessary
attribution in this CL, please create a separate CL to fix that.
For more details please refer to the link below,
<add g3 doc link>
Bug: 304529413
Test: N/A
Change-Id: Icbe839de65c4449f764bd579a9f8c43f9fac770d
Merged-In: Icbe839de65c4449f764bd579a9f8c43f9fac770d
|
|
This CL is created as a best effort to migrate test targets
to the new android ownership model. If you find incorrect or unnecessary
attribution in this CL, please create a separate CL to fix that.
For more details please refer to the link below,
<add g3 doc link>
Bug: 304529413
Test: N/A
(cherry picked from aosp/2939780)
Change-Id: Icbe839de65c4449f764bd579a9f8c43f9fac770d
|
|
This is a system service that provides the core API for ECM
(Enhanced Confirmation Mode).
Fix: 310655061
Test: manual
Change-Id: I831391e4437b51b3312b5273a2360bd029a3d8ee
|
|
Some RoleManager API methods are not multi-user-aware; for example, the
methods named "...FromController", among others. These methods lead to
Binder.getCallingUid().
And, many of those methods are called from the role-controller business
logic. But, that business logic will will be moving from a per-user app
into SystemServer. So, we need to make these methods multi-user-aware
to support the Role Business Logic Move project.
To do so, modify these methods to receive the user from the context,
and mark the APIs as @UserHandleAware.
For compatibility reasons, use CompatChanges, which will only enable
this change for callers with targetSdk V+. Since this is the first time
we've used CompatChanges in the Permission APEX, this involves updating
Android.bp files.
Test: atest CtsRoleTestCases
Bug: 303742236
Change-Id: I8efae9ffe083f8e33ea1bd221bc1ed05c1100a13
|
|
Test: m com.android.permission com.google.android.permission and verify
manually that apex_payload.img contains correct privapp_allowlist
Bug: 242509786
Change-Id: I9096cf02e4d0f74f62f4a2d11a34cafd51770ad0
|
|
Previously we used the same jarjar rules for both in the hope that if
we ever need to pass objects between them we won't run into class name
issues. However this created an issue when a static lib dependency is
needed in both framework-permission-s and service-permission, because
if we add it to service-permission it will conflict with the copy in
framework-permission-s, but if we don't service-permission will be
missing it on R.
So we should simply decouple the two and jarjar their classes into
different packages, which will help us solve this problem.
Bug: 253568736
Bug: 196909329
Test: atest StrictJavaPackagesTest
Change-Id: I107ac7be4033ccd5b6fb18f73745ded3a5e79202
|
|
SystemApi
We add this feature flag as SystemApi as it will be used across packages
(PermissionController, Settings and Platform code)
Bug: 261652173
Test: Will be used to guard the Safety Label Change Notifications
feature and so will be tested then.
Change-Id: Ia65d7c468a757de13feda32fa1a79299b39eaa63
|
|
Test: build
Change-Id: I0f425fb0e62bbb8b9feba3077d838690e6c98376
|
|
Original change: https://android-review.googlesource.com/c/platform/packages/modules/Permission/+/2151268
Change-Id: I7a86bc90a850c76fe729101eb56d6e338384c2bb
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Previously, both the sdk and apex had to specify the same *fragments
property to ensure that building a system image from a prebuilt
version of the module (both APEX and sdk snapshots) would work.
This change avoids the duplication by adding the apex to the sdk which
allows the sdk to automatically export any APIs and related information
provided by the APEX. At the moment that just includes information from
*fragments properties but may expand in future.
Bug: 232401814
Test: # Build snapshots with a fixed build number
BUILD_NUMBER=fixed packages/modules/common/build/mainline_modules_sdks.sh
# Remove api diff files as they contain file stamps of generated files so
# differ every time they are generated.
find out/dist/mainline-sdks -name \*txt | xargs rm
# Save the snapshots away.
mv out/dist/mainline-sdks before-changes
# Apply this change.
# Repeat the first two steps above and then run the following to verify
# that this change had no effect on the generated snapshot contents.
meld before-changes out/dist/mainline-sdks
Change-Id: Ic61c043e49f7de9560659359b67ed6ed0317ee08
|
|
|
|
Bundle the priv-app permission allowlist for the
apk inside the PermissionController apex.
Test: boots
Bug: 190375768
Change-Id: I034abf53d5dfaa5e4623247d62bca3f036416e35
|
|
Ran the following to compute the set of split_packages and
package_prefixes properties.
m analyze_bcpf && analyze_bcpf --bcpf com.android.permission-bootclasspath-fragment
Bug: 194063708
Test: m out/soong/hiddenapi/hiddenapi-flags.csv
Change-Id: I148891630da53d81ccdc6d3246a0b81e1e0fadc9
Merged-In: I148891630da53d81ccdc6d3246a0b81e1e0fadc9
|
|
Ran the following to compute the set of split_packages and
package_prefixes properties.
m analyze_bcpf && analyze_bcpf --bcpf com.android.permission-bootclasspath-fragment
Bug: 194063708
Test: m out/soong/hiddenapi/hiddenapi-flags.csv
Change-Id: I148891630da53d81ccdc6d3246a0b81e1e0fadc9
|
|
am: 022f2d1d4a am: bda7e190ca
Original change: https://android-review.googlesource.com/c/platform/packages/modules/Permission/+/2007755
Change-Id: I1ca6e51566a86727229e2d272d3203bb2b6cc9c2
|
|
In /packages/modules/common/sdk/ModuleDefaults.bp file, some
apex_defaults are added to provide common parameters corresponding to
Q, R, S, and T releases.
(Refer to CL link for above mentioned change -
https://android-review.googlesource.com/c/platform/packages/modules/common/+/2005890?forceReload=true)
This CL is using the apex_default corresponding to R release for the
com.google.android.permission module.
Bug: 172589606
Test: USE_RBE=true m
Since there are no runtime changes, successful code build is enough for
testing.
Change-Id: I2f37a1813c576d8751f5eb32006b486884708ac5
|
|
Bug: 216251607
Test: m
Change-Id: Ib403780221201bc8f75b529ed8f1f8439604a0f3
|
|
Revert "Xml Config CTS tests."
Revert submission 16439579-SafetyCenterXML
Reason for revert: DroidMonitor: Potential culprit for Bug b/216154014 - verifying through Forrest before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.
Reverted Changes:
I3376c0afc:Add validation and unit tests to the safety center...
I5652f67b9:Add first revision of fields to the safety center ...
I3ccdf1122:Xml Config CTS tests.
I95f2ee11a:Add basic GMS version of the Safety Center XML con...
Ied67b6598:Add basic Safety Center resources
Change-Id: I5bd1f1fbcade1e499130838d223e24b287e85455
|
|
Start reading the safety center config XML in the Safety Center service
Bug: 208428415
Test: atest SafetyCenterResourcesLibTests
Test: atest CtsSafetyCenterTestCases
Change-Id: Ied67b65986a93293f4ed2296c2a2cbdd93ff3e5d
|
|
Note: This needs to be exported from the APEX (ag/15938066) when a new
prebuilt is dropped.
The systemserver_fragment is needed for dexpreopting when the permission
APEX is built from a prebuilt.
Bug: 194150908
Test: m nothing
Merged-In: Iae4fc725d486178d58fba76b3dc014c523317cb9
Change-Id: Iae4fc725d486178d58fba76b3dc014c523317cb9
(cherry picked from commit 529c5b5dc2a0b89bb01ca73aa8ef03ba414bbf0a)
|
|
Note: This needs to be exported from the APEX (ag/15938066) when a new
prebuilt is dropped.
The systemserver_fragment is needed for dexpreopting when the permission
APEX is built from a prebuilt.
Bug: 194150908
Test: m nothing
Change-Id: Iae4fc725d486178d58fba76b3dc014c523317cb9
|
|
|
|
Bug: 169780183
Test: presubmit
Change-Id: Ia396ab3e3ff42dadc5b20939628e1a493c2a9d1c
|
|
Previously, the hidden API encoding of the permission boot dex jars,
i.e. those dex jars that permission contributes to the bootclasspath
were done as part of the monolithic hidden API processing. This change
causes the encoding to be done by the permission's
bootclasspath_fragment.
This change involves the following:
* Addition of the fragments property to the permission's
bootclasspath_fragment module to list all the other
bootclasspath_fragment modules on which this depends.
* Addition of the additional_stubs property to add stubs for APIs that
are not provided by another bootclasspath_fragment.
The build automatically checks that the hidden API flags which are
computed by permission and encoded into its boot dex jars match those
that are generated by the monolithic processing so this is guaranteed
to be safe.
Bug: 179354495
Test: m com.android.permission
- ensure that the generated APEX is byte-for-byte identical
before and after these changes.
m out/soong/hiddenapi/hiddenapi-flags.csv
- make sure that they are not changed by this.
Change-Id: Idcbdd331d5b5e897338bba46485cb56dab20dd4b
|
|
This subsumes the java_sdk_library in the sdk. Also add the
service-framework java_sdk_library as it was missing.
Bug: 188427719
Test: build_mainline_modules.sh
Change-Id: I27846baf3292c477b339e9bb2b2795542daf34c0
|
|
Allows SdkExtensions to inspect its version to decide what the extension
sdk version is on-device.
Bug: 188787081
Test: m com.android.permission and inspect
Change-Id: Icf8b31a77fca75dd6900e9f605a08153fa6e018f
|
|
Note that the contents of the fragment are added as dependencies to an
apex, so there is no need to duplicate them in java_libs.
Bug: 180105615
Test: atest CtsClasspathsTestCases
Change-Id: I268e0fe441ef4935ba27d41205f6467632458eb3
|
|
Note that the contents of the bootclasspath_fragment are added as
dependencies to an apex, so there is no need to duplicate them in
java_libs.
Bug: 180105615
Test: atest CtsClasspathsTestCases
Change-Id: I2c4cfe587ad4b3d459c3610bbf3928fb2f8ccea7
|
|
For consistency with other modules.
Bug: 177884752
Test: m permission-module-sdk
Change-Id: I1c6350bc88e7a3db95bdefb2dd8a899e4a7d40e8
|
|
|
|
Bug: 177884752
Test: m
Change-Id: I3e0dbc85cbab7d1b209c65fa8804a62bd6814a4d
|
|
am: 7924b77485 am: 13f86dd226
Original change: https://android-review.googlesource.com/c/platform/packages/modules/Permission/+/1576226
MUST ONLY BE SUBMITTED BY AUTOMERGER
Change-Id: I971bc92333730c2121be2e540660fe9419004ef8
|
|
Added SPDX-license-identifier-Apache-2.0 to:
Android.bp
framework/Android.bp
service/Android.bp
testing/Android.bp
tests/Android.bp
Bug: 68860345
Bug: 151177513
Bug: 151953481
Test: m all
Exempt-From-Owner-Approval: janitorial work
Change-Id: I16cc0e9742f196de9afbecc1bf0788c2f12bc4d0
|
|
These changes have to be in this CL together because:
- Code in service-permission depends on IRoleManager in
framework-permission, so the APIs in framework-permission and the code
in service-permission need to be moved together.
- The changes to service-permission build rules doesn't make sense
without the code moved in, so they have to be together as well.
Other details:
- framework-annotations: Several annotations are added into
framework-annoatations. Since the discussion with API council seems to
allow user IDs in system server in-process APIs, @UserIdInt and
@AppIdInt is added. @MainThread and @AnyThread is added since
@WorkerThread is already added. @CallSuper is added since @CheckResult
is also already added and they are similar in terms of category of
functionality.
- framework-permission-s-shared-srcs: 3 classes (and 2 AIDL files)
from framework is copied as shared source files and jarjared for
framework-permission, and an additional 3 is added for
service-permission as service-permission-shared-srcs. Similar to
framework-wifi and service-wifi, the 3 classes in framework-permission
is also available to service-permission by the stub library
framework-permission-pre-jarjar, and the other 3 classes used only for
service-permission is included separately to minimize our impact on
classes loaded into boot classpath. framework-permission and
service-permission shares the same jarjar rules to make sure the
classes remain available, and for the same reason framework-permission
cannot be shrank during any optimization.
- framework-permission-s-shared: A java_library target for
framework-permission-shared-srcs is created to make sure that the
public classes won't be counted as APIs, as it would be if directly
included as srcs for framework-permission
java_sdk_library. service-permission-shared is the same thing for
service-permission.
- framework-permission-s: A new java_sdk_library target created to be
loaded into bootclasspath by Android S+.
- Dumpsys Protobuf: The dumpsys protobuf
file (rolemanagerservice.proto) is moved into the module, and both the
platform (incident.proto) and the module uses protoc-gen-javastream to
generate the Java classes from it. This should be fine since it's a
"source level inclusion", and we jarjar the generated classes in our
module to avoid conflict with platform copies.
Bug: 158736025
Test: manual
Test: device boots, default apps can be changed successfully.
Change-Id: I1914774f631e51d0c587a7e527a1c9bc05ee1595
|
|
This will host the moved framework classes for role.
The class RoleFrameworkPlaceholder is added because the build won't
pass if there isn't any java source.
Bug: 158736025
Test: build
Change-Id: Icabab2cc956d6c7c07a6217256d23a8402960307
|
|
Just a cosmetic cleanup since "R" resolves to 30 as well.
Test: m
Bug: 171330443
Change-Id: I83dcc7be1ff18e6429955a0fee2596d8b0e19a25
|
|
APEXes introduced in R need to set min_sdk_version to ensure that they
are built against correct version(30 or R) of stubs (libc/liblog/...).
Bug: 152655956
Test: /vendor/google/build/build_mainline_modules.sh
Change-Id: I4a893c34b09334eea124266287301e479b9e8a59
|
|
Mark updatable APEXes as updatable: true so that they are opted-out from
optimizations that make sense only for non-updatable modules; such as
symlinking to the libs in the system partition.
Bug: 149805758
Test: m and check that there is no symlink from the APEX to the system
partition.
Change-Id: Idb55300a60a261c7bb6359439ed220ff51fcf06c
|
|
Along with two empty classes to make build happy.
Bug: 136503238
Test: presubmit
Change-Id: Ib706a7ac4d09374ce220961f9439f712a38f7c0c
|
|
Bug: 136503238
Test: m mts && mts-tradefed run mts-permission
Change-Id: I281150603798156ef5f25fbce4b7eee1a4cae82a
|
|
Bug: 136503238
Test: atest --rebuild-module-info permission_e2e_tests
Change-Id: I05cc0f19679bc0d03785233a38bb1a8b31cd3652
|
|
We need an APEX module for permission to reliably roll back runtime
permission state, specifically, platform runtime-permissions.xml will
be moved into the data directory of this APEX and be rolled back when
PermissionController is rolled back.
Bug: 136503238
Test: build
Change-Id: I93166f8dc4783bd09afa6be19a302fb0c2decd0d
|