![Android Selinux详解[四]--新增服务标签相关](http://pic.xiahunao.cn/yaotu/Android Selinux详解[四]--新增服务标签相关)
在工作过程中SElinux常用的有以下几个文件可用于新增标签可用于加标签的文件名含义对应的声明文件名(一般会声明的地方根本上放哪里都可以)file_contexts给 文件/目录/节点 新增标签file.tegenfs_contexts给节点新增标签与上一个不同的是不用执行restorecon操作file.tehwservice_contexts给hal服务新增标签hwservice.teproperty_contexts给属性新增标签property.teseapp_contexts给APP新增标签untrusted_app.te app.te...等等service_contexts给系统服务新增标签service.teservice有以下几种声明相应解释如下service type声明类型解释system_server_serviceAll service_manager types created by system_serverapp_api_serviceservices which should be available to all but isolated appsephemeral_app_api_serviceservices which should be available to all ephemeral appssystem_api_serviceservices which export only system_apiprotected_serviceservices which are explicitly disallowed for untrusted apps to accessvendor_serviceservices which served by vendor and also using the copy of libbinder on system (for instance via libbinder_ndk). services using a different copy of libbinder currently need their own context manager (e.g. vndservicemanager)service_manager_type由于系统服务最后都是添加到service manager中管理的所以系统服务的type声明都会有携带此type。Android源码中有很多服务相关的标签声明比如如下http://aospxref.com/android-12.0.0_r3/xref/system/sepolicy/public/service.te可以看到有如下几种标签声明service manage直接add的servicetype audioserver_service, service_manager_type;system server创建的service如果是新增的java层系统服务并且由system server拉起则基本都是如下声明type battery_service, system_server_service, service_manager_type;带有system_api_service的说明只有system api的服务type adb_service, system_api_service, system_server_service, service_manager_type;带有app_api_service的声明说明除了isolated apps外其他APP都可以访问的type alarm_service, app_api_service, ephemeral_app_api_service, system_server_service, service_manager_type;hal服务声明type hal_audio_service, vendor_service, protected_service, service_manager_type;type hal_audiocontrol_service, vendor_service, service_manager_type;在sepolicy/public/service.te这里还有一个neverallow此neverallow意思为不允许domain与对非service_manager_type vndservice_manager_type类型的service进行add find权限。# servicemanager handles registering or looking up named services. # It does not make sense to register or lookup something which is not a service. # Trigger a compile error if this occurs. neverallow domain ~{ service_manager_type vndservice_manager_type }:service_manager { add find };服务的type声明是和你的功能强相关的你可以根据你的功能去进行相应的type声明。假如你新增了一个系统java service那么一般声明如下也就是说必须携带system_server_service和service_manager_type其他的看情况type xxx_service, system_server_service, service_manager_type;type xxx_service, system_api_service, system_server_service, service_manager_type;type xxx_service, app_api_service, ephemeral_app_api_service, system_server_service, service_manager_type;假设你新增了一个native层service那么一般的声明如下也就是说必须携带service_manager_type并且不能携带system_server_servicetype yyy_service, service_manager_type;type yyy_service, app_api_service, service_manager_type;type yyy_service, app_api_service, system_api_service, service_manager_type;所以经过上述解释是否对服务该怎样进行type有一定的了解了呢。假设你新增了一个hal层service那么一般的声明如下也就是说必须携带vendor_service和service_manager_typetype zzz_service, vendor_service, service_manager_type;
在工作过程中SElinux常用的有以下几个文件可用于新增标签可用于加标签的文件名含义对应的声明文件名(一般会声明的地方根本上放哪里都可以)file_contexts给 文件/目录/节点 新增标签file.tegenfs_contexts给节点新增标签与上一个不同的是不用执行restorecon操作file.tehwservice_contexts给hal服务新增标签hwservice.teproperty_contexts给属性新增标签property.teseapp_contexts给APP新增标签untrusted_app.te app.te...等等service_contexts给系统服务新增标签service.teservice有以下几种声明相应解释如下service type声明类型解释system_server_serviceAll service_manager types created by system_serverapp_api_serviceservices which should be available to all but isolated appsephemeral_app_api_serviceservices which should be available to all ephemeral appssystem_api_serviceservices which export only system_apiprotected_serviceservices which are explicitly disallowed for untrusted apps to accessvendor_serviceservices which served by vendor and also using the copy of libbinder on system (for instance via libbinder_ndk). services using a different copy of libbinder currently need their own context manager (e.g. vndservicemanager)service_manager_type由于系统服务最后都是添加到service manager中管理的所以系统服务的type声明都会有携带此type。Android源码中有很多服务相关的标签声明比如如下http://aospxref.com/android-12.0.0_r3/xref/system/sepolicy/public/service.te可以看到有如下几种标签声明service manage直接add的servicetype audioserver_service, service_manager_type;system server创建的service如果是新增的java层系统服务并且由system server拉起则基本都是如下声明type battery_service, system_server_service, service_manager_type;带有system_api_service的说明只有system api的服务type adb_service, system_api_service, system_server_service, service_manager_type;带有app_api_service的声明说明除了isolated apps外其他APP都可以访问的type alarm_service, app_api_service, ephemeral_app_api_service, system_server_service, service_manager_type;hal服务声明type hal_audio_service, vendor_service, protected_service, service_manager_type;type hal_audiocontrol_service, vendor_service, service_manager_type;在sepolicy/public/service.te这里还有一个neverallow此neverallow意思为不允许domain与对非service_manager_type vndservice_manager_type类型的service进行add find权限。# servicemanager handles registering or looking up named services. # It does not make sense to register or lookup something which is not a service. # Trigger a compile error if this occurs. neverallow domain ~{ service_manager_type vndservice_manager_type }:service_manager { add find };服务的type声明是和你的功能强相关的你可以根据你的功能去进行相应的type声明。假如你新增了一个系统java service那么一般声明如下也就是说必须携带system_server_service和service_manager_type其他的看情况type xxx_service, system_server_service, service_manager_type;type xxx_service, system_api_service, system_server_service, service_manager_type;type xxx_service, app_api_service, ephemeral_app_api_service, system_server_service, service_manager_type;假设你新增了一个native层service那么一般的声明如下也就是说必须携带service_manager_type并且不能携带system_server_servicetype yyy_service, service_manager_type;type yyy_service, app_api_service, service_manager_type;type yyy_service, app_api_service, system_api_service, service_manager_type;所以经过上述解释是否对服务该怎样进行type有一定的了解了呢。假设你新增了一个hal层service那么一般的声明如下也就是说必须携带vendor_service和service_manager_typetype zzz_service, vendor_service, service_manager_type;
