Android P包管理机制之PackageManagerService授予权限流程解析

本文主要是介绍Android P包管理机制之PackageManagerService授予权限流程解析,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

PackageManagerService中默认给系统app授予相关需要的权限。

PackageManagerService中的systemReady是在SystemServer中执行的。

\frameworks\base\services\java\com\android\server\SystemServer.java

/**
* Starts a miscellaneous grab bag of stuff that has yet to be refactored
* and organized.
*/
private void startOtherServices() {//省略一部分代码//...traceBeginAndSlog("MakePackageManagerServiceReady");mPackageManagerService.systemReady();traceEnd();//省略一部分代码//...
}

\frameworks\base\services\core\java\com\android\server\pm\PackageManagerService.java

@Override
public void systemReady() {int[] grantPermissionsUserIds = EMPTY_INT_ARRAY;synchronized (mPackages) {// Verify that all of the preferred activity components actually// exist.  It is possible for applications to be updated and at// that point remove a previously declared activity component that// had been set as a preferred activity.  We try to clean this up// the next time we encounter that preferred activity, but it is// possible for the user flow to never be able to return to that// situation so here we do a sanity check to make sure we haven't// left any junk around.ArrayList<PreferredActivity> removed = new ArrayList<PreferredActivity>();for (int i=0; i<mSettings.mPreferredActivities.size(); i++) {PreferredIntentResolver pir = mSettings.mPreferredActivities.valueAt(i);removed.clear();for (PreferredActivity pa : pir.filterSet()) {if (mActivities.mActivities.get(pa.mPref.mComponent) == null) {removed.add(pa);}}if (removed.size() > 0) {for (int r=0; r<removed.size(); r++) {PreferredActivity pa = removed.get(r);Slog.w(TAG, "Removing dangling preferred activity: "+ pa.mPref.mComponent);pir.removeFilter(pa);}mSettings.writePackageRestrictionsLPr(mSettings.mPreferredActivities.keyAt(i));}}for (int userId : UserManagerService.getInstance().getUserIds()) {/* 为了方便授予权限修改了此处,注释掉了grantPermissionsUserIds初始化的条件* areDefaultRuntimePermissionsGrantedLPr(userId)的判断条件的含义:* true,正常启动,没有发生升级的情况* false,表示升级后第一次启动* 所以,该出的意思是,只有升级后第一次启动,发生了升级,才满足条件,执行赋予权限grantPermissionsUserIds *///modify by sunxiaolin 20190912//if (!mSettings.areDefaultRuntimePermissionsGrantedLPr(userId)) {grantPermissionsUserIds = ArrayUtils.appendInt(grantPermissionsUserIds, userId);//}}}sUserManager.systemReady();/* 跟上面的grantPermissionsUserIds条件有关,没有发生升级,grantPermissionsUserIds 为null,不执行			grantDefaultPermissions赋予权限* 发生升级,才执行mDefaultPermissionPolicy.grantDefaultPermissions(userId),执行默认授予权限的处理*/// If we upgraded grant all default permissions before kicking off.for (int userId : grantPermissionsUserIds) {Log.d(TAG, "sunxiaolin,systemReady,grantDefaultPermissions,userId:" + userId);mDefaultPermissionPolicy.grantDefaultPermissions(userId);}/**	没有发生升级,grantPermissionsUserIds 为null*	mDefaultPermissionPolicy.scheduleReadDefaultPermissionExceptions()为执行读取默认权限xml的处理*	xml路径为:/system/etc/default-permissions/default-car-permissions.xml*/if (grantPermissionsUserIds == EMPTY_INT_ARRAY) {// If we did not grant default permissions, we preload from this the// default permission exceptions lazily to ensure we don't hit the// disk on a new user creation.Log.d(TAG, "sunxiaolin,systemReady,grantPermissionsUserIds == EMPTY_INT_ARRAY");mDefaultPermissionPolicy.scheduleReadDefaultPermissionExceptions();}
}

授予权限的处理主要是在DefaultPermissionGrantPolicy中处理的。

\frameworks\base\services\core\java\com\android\server\pm\permission\DefaultPermissionGrantPolicy.java

public void grantDefaultPermissions(int userId) {//给系统组件和priv-app应用授予权限grantPermissionsToSysComponentsAndPrivApps(userId);//给系统中重要的应用包授予权限grantDefaultSystemHandlerPermissions(userId);//处理权限授予异常的情况,会去读default-car-permissions.xml的权限配置grantDefaultPermissionExceptions(userId);
}

不管grantPermissionsToSysComponentsAndPrivApps,grantDefaultSystemHandlerPermissions还是grantDefaultPermissionExceptions,最终都是执行了grantRuntimePermissions()方法,在grantRuntimePermissions中执行授权操作。

关于给第三方应用授权问题:

private void grantDefaultPermissionExceptions(int userId) {mHandler.removeMessages(MSG_READ_DEFAULT_PERMISSION_EXCEPTIONS);synchronized (mLock) {// mGrantExceptions is null only before the first read and then// it serves as a cache of the default grants that should be// performed for every user. If there is an entry then the app// is on the system image and supports runtime permissions.if (mGrantExceptions == null) {mGrantExceptions = readDefaultPermissionExceptionsLocked();}}Set<String> permissions = null;final int exceptionCount = mGrantExceptions.size();for (int i = 0; i < exceptionCount; i++) {String packageName = mGrantExceptions.keyAt(i);//modify by sunxiaolin 20190912//PackageParser.Package pkg = getSystemPackage(packageName);PackageParser.Package pkg = getPackage(packageName);List<DefaultPermissionGrant> permissionGrants = mGrantExceptions.valueAt(i);final int permissionGrantCount = permissionGrants.size();for (int j = 0; j < permissionGrantCount; j++) {DefaultPermissionGrant permissionGrant = permissionGrants.get(j);if (permissions == null) {permissions = new ArraySet<>();} else {permissions.clear();}permissions.add(permissionGrant.name);grantRuntimePermissions(pkg, permissions,permissionGrant.fixed, userId);}}
}

修改:

PackageParser.Package pkg = getSystemPackage(packageName);

为:

PackageParser.Package pkg = getPackage(packageName);
private void parseExceptions(XmlPullParser parser, Map<String, List<DefaultPermissionGrant>>outGrantExceptions) throws IOException, XmlPullParserException {final int outerDepth = parser.getDepth();int type;while ((type = parser.next()) != XmlPullParser.END_DOCUMENT&& (type != XmlPullParser.END_TAG || parser.getDepth() > outerDepth)) {if (type == XmlPullParser.END_TAG || type == XmlPullParser.TEXT) {continue;}if (TAG_EXCEPTION.equals(parser.getName())) {String packageName = parser.getAttributeValue(null, ATTR_PACKAGE);Log.i(TAG, "sunxiaolin,parseExceptions packageName:" + packageName);List<DefaultPermissionGrant> packageExceptions =outGrantExceptions.get(packageName);if (packageExceptions == null) {// The package must be on the system image//modify by sunxiaolin getSystemPackage()-->getPackage()PackageParser.Package pkg = getPackage(packageName);//PackageParser.Package pkg = getSystemPackage(packageName);if (pkg == null) {Log.w(TAG, "Unknown package:" + packageName);XmlUtils.skipCurrentTag(parser);continue;}// The package must support runtime permissionsif (!doesPackageSupportRuntimePermissions(pkg)) {Log.w(TAG, "Skipping non supporting runtime permissions package:" + packageName);XmlUtils.skipCurrentTag(parser);continue;}packageExceptions = new ArrayList<>();outGrantExceptions.put(packageName, packageExceptions);}
Log.i(TAG, "sunxiaolin,parseExceptions packageName:" + packageName);parsePermission(parser, packageExceptions);} else {Log.e(TAG, "Unknown tag " + parser.getName() + "under <exceptions>");}}
}

修改:

PackageParser.Package pkg = getSystemPackage(packageName);

为:

PackageParser.Package pkg = getPackage(packageName);

默认权限文件xml解析

private File[] getDefaultPermissionFiles() {ArrayList<File> ret = new ArrayList<File>();File dir = new File(Environment.getRootDirectory(), "etc/default-permissions");if (dir.isDirectory() && dir.canRead()) {Collections.addAll(ret, dir.listFiles());}dir = new File(Environment.getVendorDirectory(), "etc/default-permissions");if (dir.isDirectory() && dir.canRead()) {Collections.addAll(ret, dir.listFiles());}dir = new File(Environment.getOdmDirectory(), "etc/default-permissions");if (dir.isDirectory() && dir.canRead()) {Collections.addAll(ret, dir.listFiles());}dir = new File(Environment.getProductDirectory(), "etc/default-permissions");if (dir.isDirectory() && dir.canRead()) {Collections.addAll(ret, dir.listFiles());}// For IoT devices, we check the oem partition for default permissions for each app.if (mContext.getPackageManager().hasSystemFeature(PackageManager.FEATURE_EMBEDDED, 0)) {dir = new File(Environment.getOemDirectory(), "etc/default-permissions");if (dir.isDirectory() && dir.canRead()) {Collections.addAll(ret, dir.listFiles());}}return ret.isEmpty() ? null : ret.toArray(new File[0]);
}

default-car-permissions.xml中添加应用权限方法:
packages/services/Car/car_product/build/default-car-permissions.xml:system/etc/default-permissions/default-car-permissions.xml
packages\services\Car\car_product\build\default-car-permissions.xml

<exceptions><!-- This is an example of an exception:<exceptionpackage="foo.bar.permission"<permission name="android.permission.READ_CONTACTS" fixed="true"/><permission name="android.permission.READ_CALENDAR" fixed="false"/></exception>--><exceptionpackage="com.android.car.messenger"><!-- Contacts --><permission name="android.permission.READ_CONTACTS" fixed="false"/><!-- SMS --><permission name="android.permission.SEND_SMS" fixed="false"/><permission name="android.permission.READ_SMS" fixed="false"/></exception></exceptions>

这篇关于Android P包管理机制之PackageManagerService授予权限流程解析的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/733619

相关文章

线上Java OOM问题定位与解决方案超详细解析

《线上JavaOOM问题定位与解决方案超详细解析》OOM是JVM抛出的错误,表示内存分配失败,:本文主要介绍线上JavaOOM问题定位与解决方案的相关资料,文中通过代码介绍的非常详细,需要的朋... 目录一、OOM问题核心认知1.1 OOM定义与技术定位1.2 OOM常见类型及技术特征二、OOM问题定位工具

通过Docker容器部署Python环境的全流程

《通过Docker容器部署Python环境的全流程》在现代化开发流程中,Docker因其轻量化、环境隔离和跨平台一致性的特性,已成为部署Python应用的标准工具,本文将详细演示如何通过Docker容... 目录引言一、docker与python的协同优势二、核心步骤详解三、进阶配置技巧四、生产环境最佳实践

MyBatis分页查询实战案例完整流程

《MyBatis分页查询实战案例完整流程》MyBatis是一个强大的Java持久层框架,支持自定义SQL和高级映射,本案例以员工工资信息管理为例,详细讲解如何在IDEA中使用MyBatis结合Page... 目录1. MyBATis框架简介2. 分页查询原理与应用场景2.1 分页查询的基本原理2.1.1 分

深度解析Python中递归下降解析器的原理与实现

《深度解析Python中递归下降解析器的原理与实现》在编译器设计、配置文件处理和数据转换领域,递归下降解析器是最常用且最直观的解析技术,本文将详细介绍递归下降解析器的原理与实现,感兴趣的小伙伴可以跟随... 目录引言:解析器的核心价值一、递归下降解析器基础1.1 核心概念解析1.2 基本架构二、简单算术表达

深度解析Java @Serial 注解及常见错误案例

《深度解析Java@Serial注解及常见错误案例》Java14引入@Serial注解,用于编译时校验序列化成员,替代传统方式解决运行时错误,适用于Serializable类的方法/字段,需注意签... 目录Java @Serial 注解深度解析1. 注解本质2. 核心作用(1) 主要用途(2) 适用位置3

Debian 13升级后网络转发等功能异常怎么办? 并非错误而是管理机制变更

《Debian13升级后网络转发等功能异常怎么办?并非错误而是管理机制变更》很多朋友反馈,更新到Debian13后网络转发等功能异常,这并非BUG而是Debian13Trixie调整... 日前 Debian 13 Trixie 发布后已经有众多网友升级到新版本,只不过升级后发现某些功能存在异常,例如网络转

Java MCP 的鉴权深度解析

《JavaMCP的鉴权深度解析》文章介绍JavaMCP鉴权的实现方式,指出客户端可通过queryString、header或env传递鉴权信息,服务器端支持工具单独鉴权、过滤器集中鉴权及启动时鉴权... 目录一、MCP Client 侧(负责传递,比较简单)(1)常见的 mcpServers json 配置

redis-sentinel基础概念及部署流程

《redis-sentinel基础概念及部署流程》RedisSentinel是Redis的高可用解决方案,通过监控主从节点、自动故障转移、通知机制及配置提供,实现集群故障恢复与服务持续可用,核心组件包... 目录一. 引言二. 核心功能三. 核心组件四. 故障转移流程五. 服务部署六. sentinel部署

从原理到实战解析Java Stream 的并行流性能优化

《从原理到实战解析JavaStream的并行流性能优化》本文给大家介绍JavaStream的并行流性能优化:从原理到实战的全攻略,本文通过实例代码给大家介绍的非常详细,对大家的学习或工作具有一定的... 目录一、并行流的核心原理与适用场景二、性能优化的核心策略1. 合理设置并行度:打破默认阈值2. 避免装箱

Maven中生命周期深度解析与实战指南

《Maven中生命周期深度解析与实战指南》这篇文章主要为大家详细介绍了Maven生命周期实战指南,包含核心概念、阶段详解、SpringBoot特化场景及企业级实践建议,希望对大家有一定的帮助... 目录一、Maven 生命周期哲学二、default生命周期核心阶段详解(高频使用)三、clean生命周期核心阶