WO2023060957A1 - 操作系统中权限控制方法及装置、电子设备、存储介质 - Google Patents

操作系统中权限控制方法及装置、电子设备、存储介质 Download PDF

Info

Publication number
WO2023060957A1
WO2023060957A1 PCT/CN2022/105297 CN2022105297W WO2023060957A1 WO 2023060957 A1 WO2023060957 A1 WO 2023060957A1 CN 2022105297 W CN2022105297 W CN 2022105297W WO 2023060957 A1 WO2023060957 A1 WO 2023060957A1
Authority
WO
WIPO (PCT)
Prior art keywords
permission
authority
service
device node
access
Prior art date
Application number
PCT/CN2022/105297
Other languages
English (en)
French (fr)
Inventor
王锐
Original Assignee
北京字节跳动网络技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京字节跳动网络技术有限公司 filed Critical 北京字节跳动网络技术有限公司
Publication of WO2023060957A1 publication Critical patent/WO2023060957A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6227—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database where protection concerns the structure of data, e.g. records, types, queries
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices

Definitions

  • Embodiments of the present disclosure relate to rights management technologies for device nodes in an operating system, and in particular, to a method and device for controlling rights in an operating system, electronic equipment, storage media, computer program products, and computer programs.
  • no method of rights management is provided for accessing the device.
  • all applications in the operating system can access the device, which will cause all device nodes in the operating system to be exposed, and the user's private data will be leaked and may be tampered with, such as electronic devices such as cameras and microphones. Nodes can be opened at will, resulting in poor user experience.
  • the embodiments of the present disclosure provide a permission control method and device in an operating system, an electronic device, a storage medium, a computer program product, and a computer program, so as to at least solve the above technical problems existing in the prior art.
  • a permission control method in an operating system including:
  • the device service queries the first permission service about the access status of the first process's first permission to the first device node;
  • the device service receives a first query result returned by the first permission service, generates first feedback information based on the first query result, and outputs the first feedback information to an application corresponding to the first process; or
  • the device service receives the second query result returned by the first permission service, opens the first device node or outputs a first prompt message that the first device node has no permission to open to the application corresponding to the first process ;
  • the first query result and the second query result are searched and obtained by the first authority service in a setting database based on the information of the first device node and/or the identification information of the first process;
  • the setting database pre-stores the access states of the first authority of more than one device node for more than one application; the identification information of the first process is associated with the identification information of the application corresponding to the first process.
  • the method also includes:
  • the device service receives second indication information for the first feedback information from the application corresponding to the first process, starts the first device node based on the second indication information; and triggers the first permission service to In the setting database, modify the access status of the first device node to the first permission of the application corresponding to the first process to allow access.
  • the method also includes:
  • the device service receives third indication information for the first feedback information from the application corresponding to the first process, and outputs to the application corresponding to the first process based on the third indication information that the first device is not enabled.
  • the first prompt information of the node authority and triggering the first authority service to modify the access status of the first device node to the first authority of the application corresponding to the first process in the setting database to deny access .
  • the method also includes:
  • the first permission service searches the setting database for all data items about the first permission, or the first permission related to the application identification information in the query request. Data items, or data items of the first authority related to the device node identification information in the query request, or data items of the first authority related to the process identification in the query request, and output.
  • the method also includes:
  • the first authority service modifies the corresponding data item of the first authority in the setting database, and saves the modified data item of the first authority.
  • the method also includes:
  • the first permission service and the setting database are generated, and the first permission data item about the device node is set as a default value in the setting database.
  • an apparatus for controlling permissions in an operating system including:
  • a query unit configured to, in response to the first process's access request to the first device node, query the first permission service about the access status of the first process's first permission to the first device node;
  • a first receiving unit configured to receive a first query result returned by the first authority service
  • a first generating unit configured to generate first feedback information based on the first query result
  • an output unit configured to output the first feedback information to an application corresponding to the first process
  • a second receiving unit configured to receive a second query result returned by the first authority service
  • a processing unit configured to, in response to the second query result, enable the first device node or output a first prompt message that there is no permission to enable the first device node to an application corresponding to the first process;
  • the first query result and the second query result are searched and obtained by the first authority service in a setting database based on the information of the first device node and/or the identification information of the first process;
  • the setting database pre-stores the access states of the first authority of more than one device node for more than one application; the identification information of the first process is associated with the identification information of the application corresponding to the first process.
  • the device also includes:
  • a third receiving unit configured to receive second indication information for the first feedback information from an application corresponding to the first process
  • the processing unit is further configured to enable the first device node based on the second indication information; and trigger the first authority service to assign the first device node to the first device node in the setting database.
  • the access state of the first permission of the application corresponding to the process is changed to allow access.
  • the device also includes:
  • a fourth receiving unit configured to receive third indication information for the first feedback information from an application corresponding to the first process
  • the processing unit is further configured to output to the application corresponding to the first process based on the third indication information a first prompt message that the permission of the first device node is not enabled; and trigger the first permission service In the setting database, modify the access status of the first device node to the first permission of the application corresponding to the first process to deny access.
  • processing unit is further configured to:
  • triggering the first permission service to search for all data items related to the first permission in the setting database, or the first permission related to the application identification information in the query request or the data item of the first authority related to the device node identification information in the query request, or the data item of the first authority related to the process identification in the query request, and output.
  • processing unit is further configured to:
  • the first authority service modifies the corresponding data item of the first authority in the setting database, and saves the modified data item of the first authority.
  • the device also includes:
  • the second generating unit is configured to generate the first authority service and the setting database in response to the loading of the operating system, and set the first authority data item about the device node as a default value in the setting database .
  • an electronic device including a processor, a memory, and an executable program stored on the memory and capable of being run by the processor.
  • the processor runs the executable program, Execute the steps of the permission control method in the operating system.
  • a storage medium on which an executable program is stored, and when the executable program is executed by a processor, the steps of the permission control method in an operating system are implemented.
  • a computer program product including a computer program.
  • the computer program When the computer program is executed by a processor, the steps of the method for controlling rights in an operating system are implemented.
  • a computer program is provided, the computer program is executed by a processor to implement the steps of the permission control method in an operating system.
  • the embodiment of the present disclosure when the operating system is loaded, corresponding authority services and databases are generated for all sensitive device nodes, and the authority management status of sensitive device nodes is set in the database.
  • all applications require corresponding authorization to Sensitive device nodes are accessed; after obtaining the access rights of some applications to device nodes, the access rights of device nodes are subsequently enabled for the application; the embodiment of the present disclosure also supports the call of access rights to device nodes, and can receive according to user needs
  • the user modifies the permission status of the device node and stores it in the corresponding database, which is convenient for the user to open related applications to access the device node.
  • the embodiments of the present disclosure set the permission access state of the device node for the operating system, which facilitates the management of the permission of the device node, and greatly improves the user's experience of using the operating system.
  • FIG. 1 is a schematic flow diagram of a permission control method in an operating system according to an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of an architecture of permission control in an operating system according to an embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart of a method for controlling permissions in an operating system according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of an architecture of permission settings in an operating system according to an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of the composition and structure of an authority control device in an operating system according to an embodiment of the present disclosure
  • FIG. 6 is a structural diagram of an electronic device according to an embodiment of the present disclosure.
  • FIG. 1 is a schematic flowchart of a method for controlling permissions in an operating system according to an embodiment of the present disclosure. As shown in FIG. 1 , the method for controlling permissions in an operating system according to an embodiment of the present disclosure includes the following processing steps:
  • Step 101 in response to the first process's access request to the first device node, the device service queries the first permission service about the access status of the first process's first permission to the first device node.
  • the operating system when the operating system is loaded, a first authority service and a setting database are generated, and the first authority data item about the device node is set as a default value in the setting database.
  • the operating system mainly includes a Linux system.
  • the Linux system also known as the GNU/Linux operating system, includes but is not limited to various distributions such as Ubuntu, Redhat, and Debian.
  • the first authority especially refers to sensitive authority; it may also include common authority, signature authority and system signature authority, etc.
  • the access state includes deny access state, allow access state, default state and so on.
  • the default access state of the first authority when the operating system is loaded on the electronic device, the default access state of the first authority is set for all sensitive device nodes in all operating systems, that is, the access state of the first authority is the default value, and all applications are targeted at sensitive
  • the first access to a device node requires user authorization.
  • an access process of the application is generated, and an access request for the first device node to be accessed is sent to the device service;
  • the device service searches the setting database for the access state of the first device node for the first permission of the application corresponding to the first process. If it is in the default state, it needs to return relevant information about whether the user is authorized to the application corresponding to the first process. Open or refuse to open based on user authorization; if the application corresponding to the first process has visited the first device node before, determine whether to open the first device node according to the authorization corresponding to the previous access.
  • Step 102 the device service receives the first query result returned by the first permission service, generates first feedback information based on the first query result, and sends the first feedback information to the application corresponding to the first process output.
  • the first query result indicates that the access authority of the first device node to the application corresponding to the first process is a default setting, that is, the application corresponding to the first process accesses the first device node for the first time.
  • the device service needs to send first feedback information to the application corresponding to the first process, so as to ask whether the user agrees to access the first device node.
  • the first feedback information mainly includes information about whether to agree to access the first device node.
  • Step 103 the device service receives the second query result returned by the first permission service, and enables the first device node or outputs the first device node without permission to the first device node to the application corresponding to the first process.
  • a reminder message A reminder message.
  • the second query result means that the application corresponding to the first process accesses the first device node for the first time, and the access status of the first permission when the application corresponding to the first process accesses the first device node last time is taken as the current If the previous setting is that the first device node allows access to the application corresponding to the first process, the first device node will be opened directly; if the previous setting is that the first device node denies access to the application corresponding to the first process , then refuse to open the first device node, and the device service sends a first prompt message refusing to open the first device node to the application corresponding to the first process.
  • the first query result and the second query result are stored in the setting database by the first authority service based on the information of the first device node and/or the identification information of the first process Search and obtain in the setting database; the access status of the first permission of more than one device node for more than one application is pre-stored in the setting database; the identification information of the first process is the identification information of the application corresponding to the first process Associated.
  • the identification information between the application and its own process is the same or closely related, the corresponding application can be determined through the process identification, and the identification of the process corresponding to the application can be identified based on the application.
  • the setting database mainly refers to the encrypted database, which is set up for the first authority service, and is mainly used to store the access status of the sensitive authority of the device node, so as to enable the corresponding sensitive authority access for different applications, and the device node Protect privacy.
  • the method further includes: the device service receives second indication information for the first feedback information from the application corresponding to the first process, and based on the second indication information Start the first device node; and trigger the first permission service to modify the access status of the first device node to the first permission of the application corresponding to the first process in the setting database to allow access .
  • the second indication information is that the user chooses to allow the first process to access the first device node based on the first feedback information, and agrees that the application corresponding to the first process starts the first device node.
  • the device service triggers the first device node.
  • the first permission service modifies the access status of the first device node to the first permission of the application corresponding to the first process in the setting database to allow access, and after that, the application corresponding to the first process accesses again When the first device node is selected, the first device node may be directly started.
  • the method further includes: the device service receives third indication information for the first feedback information from the application corresponding to the first process, based on The third indication information outputs to the application corresponding to the first process a first prompt information that no permission of the first device node is enabled; and triggers the first permission service to add the first device node permission to the setting database.
  • a device node modifies the access state of the first permission of the application corresponding to the first process to deny access.
  • the third indication information is that the user chooses to deny the first process's access to the first device node based on the first feedback information.
  • the device service triggers the first permission service to set
  • the first device node modifies the access status of the first permission of the application corresponding to the first process to access denial, and thereafter, when the application corresponding to the first process accesses the first device node again, it will report to the first process corresponding
  • the application sends the indication information of refusing to open, and asks the user whether to open the information allowing access to the first device node.
  • the method further includes: in response to the query request for the first permission, the first permission service searches for all data items related to the first permission in the setting database, or matches with the query The data item of the first authority related to the application identification information in the request, or the data item of the first authority related to the device node identification information in the query request, or the first authority related to the process identification in the query request Permission data items, and output. That is, the embodiments of the present disclosure also support a query request for the first permission.
  • the query request may be to query all sensitive permission information by default, including both device node sensitive permission information and application sensitive permission information, or query
  • the request is to query the sensitive permission information of a certain application on the device node, or query the sensitive permission information of a certain process (based on the Process ID (PID)) to the device node, or query the sensitive permission information of a certain device node to which applications permission information.
  • PID Process ID
  • the embodiments of the present disclosure support querying the first permission information and its access status at any time, and the supported querying methods are wider.
  • the method further includes: in response to a modification request for a data item of the first authority, the first authority service modifies the corresponding data item of the first authority in the setting database, And save the modified data item of the first authority.
  • the user After querying the access status of the sensitive permissions of the relevant application for the device node or the access status of the sensitive permissions of the device node for the application or its process, the user can modify the access status of the sensitive permissions at any time based on the corresponding scenario, and the modified access status of the sensitive permissions It will be recorded and saved in the setting database, that is, the confidential database.
  • the modification here includes the modification of the relevant value of the access status of the original sensitive permission, and also includes the modification of the access status of the sensitive permission, such as adding or deleting.
  • the sensitive permission service program (the first permission service) is created in the Linux system to save the dynamic adjustment information of the sensitive permission of the application.
  • it is mainly to set and manage the access state of the sensitive authority (the first authority) of the device node.
  • the Linux system also includes common permissions, signature permissions, and system signature permissions. in:
  • Normal permissions are also called normal permissions. Even with this kind of permissions, the risk of the user's private data being leaked and tampered with is relatively high. For example, permission to set the time zone is a normal permission. If an app declares that it needs a normal permission, the system automatically grants the app that permission.
  • Sensitive permissions are also called dangerous permissions.
  • the access status of their permissions is opposite to that of ordinary permissions at runtime. Once an application obtains such permissions, the user's private data is at risk of being leaked and tampered with.
  • the READ_CONTACTS permission is a dangerous permission. If an app declares that it requires a dangerous permission, the user must explicitly grant that permission to the app.
  • Signature permission This type of permission is only open to applications with the same signature.
  • WeChat and QQ use the same signature when publishing, and WeChat can apply to access this permission in QQ and use the data controlled by the corresponding permission.
  • SignatureOrSystem permission similar to signature permission, but it not only requires the same signature, but also requires the same kind of system-level application. Generally, this type of permission is only used in prefabricated scenarios developed by mobile phone manufacturers.
  • the Linux device node refers to: in Linux, all devices are stored in the /dev directory in the form of files, and the device nodes are accessed through files.
  • the device node is the abstraction of the device by the Linux kernel.
  • a device node is a file.
  • Applications perform access to devices through a standardized set of calls that are independent of any particular driver. The driver is responsible for mapping these standard calls to specific operations of the actual hardware.
  • File nodes under the /dev directory are called special device nodes.
  • the so-called node refers to the entry, through which the purpose of operating (reading, writing, etc.) of a certain device is achieved, and the reason why the corresponding entry should be set in /dev is because the Linux system provides a corresponding virtual file system.
  • Various devices can be operated using consistent function interfaces (open(), read(), write(), close()...), etc., which can greatly reduce the complexity of applications accessing Linux peripherals.
  • the embodiment of the present disclosure is aimed at the management of the device node in the Linux system and setting its corresponding sensitive permission access state. That is, there is no method for managing access rights to devices in the current Linux system, and the embodiments of the present disclosure provide a corresponding method for dynamically managing application usage rights in the Linux system.
  • Fig. 2 is a schematic diagram of the architecture of authority control in the operating system of the embodiment of the present disclosure.
  • App the relevant application
  • the access status of the sensitive permissions of the Linux device node is managed and controlled. Therefore, when the App calls the Linux device node, it needs to obtain the access status of the sensitive permission of the Linux device node to be called through the device service.
  • the device service sends a query to the sensitive permission service Request, the sensitive permission service queries the corresponding encrypted database, obtains the access status of the sensitive permission of the Linux device node to be accessed by the current application, and makes corresponding access management based on the corresponding access status.
  • the default sensitive permission is to ask whether to allow access to the device node.
  • the microphone service calls the sensitive permission service to query whether the application is allowed to access the microphone. If the access is allowed, the microphone function will be enabled for the application. If the access is not allowed, the prompt message of failure to open the microphone will be returned. In the scene of asking the status, a system dialog box can pop up, and the user can choose whether to allow the relevant application to access the device node, and the user makes a decision.
  • the sensitive authority is selected, the access state of the sensitive authority selected by the user is saved in the encrypted database of the sensitive authority service program.
  • FIG. 3 is a schematic flow diagram of a permission control method in an operating system according to an embodiment of the present disclosure. As shown in FIG. 3 , the permission control method according to an embodiment of the present disclosure includes:
  • the Linux system runs the sensitive authority service program, which generates an encrypted database and stores the corresponding relationship between the application package name information and the sensitive authority information.
  • the access sensitive permission service program queries the access status of the sensitive permissions of the application. That is, when an App needs to access a device node with sensitive permissions, the Linux device service obtains the process PID information of the current App.
  • an application When an application queries sensitive permission information through Inter-Process Communication (IPC), it sends the application PID and specific sensitive information as parameters to the sensitive permission service program at the same time. That is, the Linux device service sends the access status of the sensitive permission of the device node to the sensitive permission service. At this time, the sensitive permission service queries the access status of the sensitive permission of the PID for the device node according to the PID of the process, and makes a corresponding management policy according to the queried access status of the sensitive permission.
  • IPC Inter-Process Communication
  • the sensitive permission service program can query information such as the application package name according to the PID.
  • the access state of the sensitive permission includes at least three states: a default state, a denied state, and an allowed state.
  • a system pop-up box pops up, asking the user whether to agree or deny access to the Linux device node function. And continue the following process according to the user's choice of running access or denying access.
  • the sensitive permission query finds that the access permission of the application to the device node is in a denied state, the relevant information about the denial of access to the device node is returned, and the function of the Linux device node is prohibited from being enabled.
  • the sensitive authority query finds that the application's access authority to the device node is allowed, the function of the Linux device node is normally enabled.
  • the device node is opened or refused to be opened.
  • the sensitive permission service program will apply package name and other information, and after the selection of access to the device node
  • the access status of the sensitive permissions is stored in the encrypted database at the same time, so that the sensitive permissions of the device node can be managed based on the selected sensitive permissions access status when the application next accesses.
  • the service program of the Linux device node when an application requests to use sensitive devices such as cameras and microphones, the service program of the Linux device node reversely reads the PID information of the requesting application through the local IPC communication mechanism, and saves the PID information of the application.
  • the Linux device node service calls the sensitive permission service program through the local IPC communication mechanism to query the sensitive permission interface.
  • the query parameters can include the application PID information and the information of the accessed device node.
  • the sensitive permission service according to its own If the relevant data stored in the encrypted database is the default value, a system pop-up box will pop up to ask the user whether to allow access to the device node.
  • the related device node is directly opened or refused to be opened based on the access state of the sensitive authority of the device node in the encrypted database.
  • Fig. 4 is a schematic diagram of the structure of permission setting in the operating system of the embodiment of the disclosure. As shown in Fig. 4, in the embodiment of the disclosure, it also supports the function of querying and modifying the access status of sensitive permissions, through the system settings in the App Function, you can query the access status of the application's sensitive permissions for device nodes in the encrypted database through the sensitive permission service. That is, the embodiment of the present disclosure can provide App with a corresponding query interface to query all sensitive permission information, such as querying the sensitive permission information of a certain application package, querying the sensitive permission information of a certain PID, and setting the sensitive permission information of a certain application package information, delete sensitive permission information of an application package, create and store sensitive permission information in an encrypted database, etc.
  • the embodiment of the present disclosure can provide App with a corresponding query interface to query all sensitive permission information, such as querying the sensitive permission information of a certain application package, querying the sensitive permission information of a certain PID, and setting the sensitive permission information of a certain application package information, delete
  • the stored data about the access status of sensitive permissions in the encrypted database includes information such as application package name, binary executable file name, sensitive permission name, and sensitive permission status.
  • the application process name is queried according to the PID
  • the application package name information is queried according to the process name.
  • the sensitive permission status specifically includes:
  • the system settings in the App can call the sensitive permission service interface to query the sensitive permission information of the application, and modify the relevant information of the sensitive permission in the encrypted database.
  • FIG. 5 is a schematic diagram of the composition and structure of the authority control device in the operating system of the embodiment of the present disclosure.
  • the authority control device in the operating system of the embodiment of the present disclosure includes:
  • the query unit 50 is configured to, in response to the first process's access request to the first device node, query the first permission service about the access status of the first process's first permission to the first device node;
  • the first receiving unit 51 is configured to receive the first query result returned by the first authority service
  • a first generating unit 52 configured to generate first feedback information based on the first query result
  • an output unit 53 configured to output the first feedback information to an application corresponding to the first process
  • the second receiving unit 54 is configured to receive the second query result returned by the first authority service
  • a processing unit 55 configured to, in response to the second query result, enable the first device node or output a first prompt message that there is no permission to enable the first device node to an application corresponding to the first process;
  • the first query result and the second query result are searched and obtained by the first authority service in a setting database based on the information of the first device node and/or the identification information of the first process;
  • the setting database pre-stores the access states of the first authority of more than one device node for more than one application; the identification information of the first process is associated with the identification information of the application corresponding to the first process.
  • the permission control device in the operating system in the embodiment of the present disclosure further includes:
  • a third receiving unit (not shown in FIG. 5 ), configured to receive second indication information for the first feedback information from an application corresponding to the first process;
  • the processing unit 55 is further configured to enable the first device node based on the second indication information; and trigger the first authority service to assign the first device node to the second device node in the setting database.
  • the access state of the first permission of the application corresponding to a process is changed to allow access.
  • the permission control device in the operating system in the embodiment of the present disclosure further includes:
  • a fourth receiving unit (not shown in FIG. 5 ), configured to receive third indication information for the first feedback information from an application corresponding to the first process;
  • the processing unit 55 is further configured to, based on the third indication information, output to the application corresponding to the first process a first prompt message that the permission of the first device node is not enabled; and trigger the first permission service to In the setting database, modify the access state of the first device node to the first permission of the application corresponding to the first process to deny access.
  • processing unit 55 is further configured to:
  • triggering the first permission service to search for all data items related to the first permission in the setting database, or the first permission related to the application identification information in the query request or the data item of the first authority related to the device node identification information in the query request, or the data item of the first authority related to the process identification in the query request, and output.
  • processing unit 55 is further configured to:
  • the first authority service modifies the corresponding data item of the first authority in the setting database, and saves the modified data item of the first authority.
  • the permission control device in the operating system in the embodiment of the present disclosure further includes:
  • the second generating unit (not shown in FIG. 5 ) is configured to generate the first authority service and the setting database in response to the loading of the operating system, and set the settings about the device node in the setting database.
  • the first permission data item is a default value.
  • the query unit 50, the first receiving unit 51, the first generating unit 52, the output unit 53, the second receiving unit 54, the third receiving unit, the fourth receiving unit, the second generating unit, etc. may be One or more central processing units (CPU, Central Processing Unit), application-specific integrated circuits (ASIC, Application Specific Integrated Circuit), digital signal processors (Digital Signal Processor, DSP), programmable logic devices (PLD, Programmable Logic Device ), complex programmable logic device (CPLD, Complex Programmable Logic Device), field-programmable gate array (FPGA, Field-Programmable Gate Array), general-purpose processor, controller, microcontroller (MCU, Micro Controller Unit), micro Implemented by a processor (Microprocessor), or other electronic components, for executing the steps of the permission control method in the operating system of the foregoing embodiments.
  • CPU Central Processing Unit
  • ASIC Application Specific Integrated Circuit
  • DSP digital signal processors
  • PLD Programmable logic devices
  • CPLD Complex Programmable Logic Device
  • FPGA Field-Programm
  • the electronic device 11 includes one or more processors 111 and a memory 112 .
  • the processor 111 may be a central processing unit (CPU) or other form of processing unit having data processing capabilities and/or instruction execution capabilities, and may control other components in the electronic device 11 to perform desired functions.
  • CPU central processing unit
  • the processor 111 may be a central processing unit (CPU) or other form of processing unit having data processing capabilities and/or instruction execution capabilities, and may control other components in the electronic device 11 to perform desired functions.
  • Memory 112 may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and/or non-volatile memory.
  • the volatile memory may include, for example, a random access memory (RAM, Random Access Memory) and/or a cache memory (cache).
  • the non-volatile memory may include, for example, a read-only memory (ROM, Read Only Memory), a hard disk, a flash memory, and the like.
  • One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 111 may execute the program instructions to implement the permission control method in the operating system of each embodiment of the present disclosure described above and /or other desired functionality.
  • Various contents such as input signal, signal component, noise component, etc. may also be stored in the computer-readable storage medium.
  • the electronic device 11 may further include: an input device 113 and an output device 114 , and these components are interconnected through a bus system and/or other forms of connection mechanisms (not shown in FIG. 6 ).
  • the input device 113 may include, for example, a keyboard, a mouse, and the like.
  • the output device 114 can output various information to the outside, including determined distance information, direction information, and the like.
  • the output device 114 may include, for example, a display, a speaker, a printer, a communication network and remote output devices connected thereto, and the like.
  • the electronic device 11 may also include any other appropriate components.
  • the embodiments of the present disclosure also describe a storage medium on which an executable program is stored, and the executable program is executed by a processor in the steps of the method for controlling authority in the operating system of the foregoing embodiments.
  • embodiments of the present disclosure may also be computer program products, which include computer program instructions that, when executed by a processor, cause the processor to perform the above-mentioned "exemplary method" of this specification. Steps in methods according to various embodiments of the present disclosure described in section.
  • the computer program product can be written in any combination of one or more programming languages to execute the program codes for performing the operations of the embodiments of the present disclosure, and the programming languages include object-oriented programming languages, such as Java, C++, etc. , also includes conventional procedural programming languages, such as the "C" language or similar programming languages.
  • the program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server to execute.
  • embodiments of the present disclosure may also be a computer-readable storage medium, on which computer program instructions are stored, and the computer program instructions, when executed by a processor, cause the processor to perform the above-mentioned "Exemplary Method" section of this specification. Steps in methods according to various embodiments of the present disclosure described in .
  • the computer readable storage medium may employ any combination of one or more readable media.
  • the readable medium may be a readable signal medium or a readable storage medium.
  • the readable storage medium may include, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or devices, or any combination thereof.
  • readable storage media include: electrical connection with one or more conductors, portable disk, hard disk, random access memory (RAM), read only memory (ROM), erasable Type programmable read-only memory (EPROM, Erasable Programmable Read-Only Memory or flash memory), optical fiber, portable compact disk read-only memory (Compact Disc Read-Only Memory, CD-ROM), optical storage device, magnetic storage device, or the above any suitable combination.
  • Embodiments of the present disclosure may also be computer programs, which, when executed by a processor, implement the steps of the method for controlling rights in an operating system of the foregoing embodiments.
  • each component or each step can be decomposed and/or reassembled. These decompositions and/or recombinations should be considered equivalents of the present disclosure.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Databases & Information Systems (AREA)
  • Storage Device Security (AREA)

Abstract

一种操作系统中权限控制方法及装置、电子设备、存储介质。所述方法包括：响应于第一进程对第一设备节点的访问请求，设备服务向第一权限服务查询所述第一进程对所述第一设备节点的第一权限的访问状态（101）；所述设备服务接收所述第一权限服务返回的第一查询结果，基于所述第一查询结果生成第一反馈信息，将所述第一反馈信息向所述第一进程对应的应用输出（102）；或所述设备服务接收所述第一权限服务返回的第二查询结果，开启所述第一设备节点或向所述第一进程对应的应用输出无开启所述第一设备节点权限的第一提示信息（103）。为操作系统设置了设备节点的权限访问状态，方便针对设备节点的权限管理，大大提升了用户对操作系统的使用体验。

Description

操作系统中权限控制方法及装置、电子设备、存储介质
相关申请的交叉引用
本公开要求于2021年10月14日提交中国专利局、申请号为202111196972.9、申请名称为“操作系统中权限控制方法及装置、电子设备、存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本文中。
技术领域
本公开实施例涉及操作系统中针对设备节点的权限管理技术，尤其涉及一种操作系统中权限控制方法及装置、电子设备、存储介质、计算机程序产品及计算机程序。
背景技术
在一些操作系统中，未设置任何针对访问设备的权限管理方法。这样，操作系统中的所有应用均能对设备进行访问，这将导致操作系统中的所有设备节点暴露于外，用户的隐私数据将被泄露并可能被篡改，如电子设备的摄像头、麦克风等设备节点，可以随意打开而导致用户体验较差。
发明内容
有鉴于此，本公开实施例提供一种操作系统中权限控制方法及装置、电子设备、存储介质、计算机程序产品及计算机程序，以至少解决现有技术中存在的以上技术问题。
根据本公开实施例的第一方面，提供一种操作系统中权限控制方法，包括：
响应于第一进程对第一设备节点的访问请求，设备服务向第一权限服务查询所述第一进程对所述第一设备节点的第一权限的访问状态；
所述设备服务接收所述第一权限服务返回的第一查询结果，基于所述第一查询结果生成第一反馈信息，将所述第一反馈信息向所述第一进程对应的应用输出；或所述设备服务接收所述第一权限服务返回的第二查询结果，开启所述第一设备节点或向所述第一进程对应的应用输出无开启所述第一设备节点权限的第一提示信息；
其中，所述第一查询结果和所述第二查询结果由所述第一权限服务基于所述第一设备节点的信息和/或所述第一进程的标识信息在设定数据库中查找获取；所述设定数据库中预存储有一个以上设备节点的第一权限针对一种以上应用的访问状态；所述第一进程的标识信息与所述第一进程对应的应用的标识信息相关联。
在一个实施例中，所述方法还包括：
所述设备服务接收所述第一进程对应的应用针对所述第一反馈信息的第二指示信息，基于所述第二指示信息开启所述第一设备节点；并触发所述第一权限服务在所述设定数据库中将所述第一设备节点对于所述第一进程对应的应用的第一权限的访问状态修改为允许访问。
在一个实施例中，所述方法还包括：
所述设备服务接收所述第一进程对应的应用针对所述第一反馈信息的第三指示信息，基于所述第三指示信息向所述第一进程对应的应用输出无开启所述第一设备节点权限的第一提示信息；并触发所述第一权限服务在所述设定数据库中将所述第一设备节点对于所述第一进程对应的应用的第一权限的访问状态修改为拒绝访问。
在一个实施例中，所述方法还包括：
响应于针对第一权限的查询请求，所述第一权限服务在所述设定数据库中查找所有关于第一权限的数据项，或与所述查询请求中的应用标识信息相关的第一权限的数据项、或与所述查询请求中的设备节点标识信息相关的第一权限的数据项，或与所述查询请求中的进程标识相关的第一权限的数据项，并输出。
在一个实施例中，所述方法还包括：
响应于针对第一权限的数据项的修改请求，所述第一权限服务在所述设定数据库中对相应的第一权限的数据项进行修改，并保存修改后的第一权限的数据项。
在一个实施例中，所述方法还包括：
响应于所述操作系统的装载，生成所述第一权限服务和所述设定数据库，在所述设定数据库中设置关于设备节点的第一权限数据项为默认值。
根据本公开实施例的第二方面，提供一种操作系统中权限控制装置，包括：
查询单元，用于响应于第一进程对第一设备节点的访问请求，向第一权限服务查询所述第一进程对所述第一设备节点的第一权限的访问状态；
第一接收单元，用于接收所述第一权限服务返回的第一查询结果；
第一生成单元，用于基于所述第一查询结果生成第一反馈信息；
输出单元，用于将所述第一反馈信息向所述第一进程对应的应用输出；
第二接收单元，用于接收所述第一权限服务返回的第二查询结果；
处理单元，用于响应于所述第二查询结果，开启所述第一设备节点或向所述第一进程对应的应用输出无开启所述第一设备节点权限的第一提示信息；
其中，所述第一查询结果和所述第二查询结果由所述第一权限服务基于所述第一设备节点的信息和/或所述第一进程的标识信息在设定数据库中查找获取；所述设定数据库中预存储有一个以上设备节点的第一权限针对一种以上应用的访问状态；所述第一进程的标识信息与所述第一进程对应的应用的标识信息相关联。
在一个实施例中，所述装置还包括：
第三接收单元，用于接收所述第一进程对应的应用针对所述第一反馈信息的第二指示信息；
所述处理单元还用于，基于所述第二指示信息开启所述第一设备节点；并触发所述第一权限服务在所述设定数据库中将所述第一设备节点对于所述第一进程对应的应用的第一权限的访问状态修改为允许访问。
在一个实施例中，所述装置还包括：
第四接收单元，用于接收所述第一进程对应的应用针对所述第一反馈信息的第三指示信息；
所述处理单元还用于，基于所述第三指示信息向所述第一进程对应的应用输出无开启所述第一设备节点权限的第一提示信息；并触发所述第一权限服务在所述设定数据库中将所述第一设备节点对于所述第一进程对应的应用的第一权限的访问状态修改为拒绝访问。
在一个实施例中，所述处理单元，还用于：
响应于针对第一权限的查询请求，触发所述第一权限服务在所述设定数据库中查找所有关于第一权限的数据项，或与所述查询请求中的应用标识信息相关的第一权限的数据项、或与所述查询请求中的设备节点标识信息相关的第一权限的数据项，或与所述查询请求中的进程标识相关的第一权限的数据项，并输出。
在一个实施例中，所述处理单元，还用于：
响应于针对第一权限的数据项的修改请求，所述第一权限服务在所述设定数据库中对相应的第一权限的数据项进行修改，并保存修改后的第一权限的数据项。
在一个实施例中，所述装置还包括：
第二生成单元，用于响应于所述操作系统的装载，生成所述第一权限服务和所述设定数据库，在所述设定数据库中设置关于设备节点的第一权限数据项为默认值。
根据本公开实施例的第三方面，提供一种电子设备，包括处理器、存储器及存储在存储器上并能够由所述处理器运行的可执行程序，所述处理器运行所述可执行程序时执行所述的操作系统中权限控制方法的步骤。
根据本公开实施例的第四方面，提供一种存储介质，其上存储由可执行程序，所述可执行程序被处理器执行时实现所述的操作系统中权限控制方法的步骤。
据本公开实施例的第五方面，提供一种计算机程序产品，包括计算机程序，所述计算机程序被处理器执行时，实现所述的操作系统中权限控制方法的步骤。
据本公开实施例的第六方面，提供一种计算机程序，所述计算机程序在被处理器执行实现所述的操作系统中权限控制方法的步骤。
本公开实施例中，在操作系统装载时，即为所有的敏感设备节点生成相应的权限服务和数据库，数据库中设置有关于敏感设备节点的权限管理状态，默认所有的应用均需要相应授权才能对敏感设备节点进行访问；当得到一些应用对设备节点的访问权限后，后续为该应用开启设备节点的访问权限；本公开实施例还支持对设备节点的访问权限的调用，并能根据用户需求接收用户针对设备节点的权限状态修改，并存储于相应数据库中，方便用户开启相关应用对设备节点的访问。本公开实施例为操作系统设置了设备节点的权限访问状态，方便针对设备节点的权限管理，大大提升了用户对操作系统的使用体验。
附图说明
为了更清楚地说明本公开实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍。显而易见地，下面描述中的附图是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本公开实施例的操作系统中权限控制方法的流程示意图；
图2为本公开实施例的操作系统中权限控制的架构示意图；
图3为本公开实施例的操作系统中权限控制方法的流程示意图；
图4为本公开实施例的操作系统中权限设置的架构示意图；
图5为本公开实施例的操作系统中权限控制装置的组成结构示意图；
图6为本公开实施例的电子设备的结构图。
具体实施方式
以下结合附图，详细阐明本公开实施例技术方案的实质。
图1为本公开实施例的操作系统中权限控制方法的流程示意图，如图1所示，本公开实施例的操作系统中权限控制方法包括以下处理步骤：
步骤101，响应于第一进程对第一设备节点的访问请求，设备服务向第一权限服务查询所述第一进程对所述第一设备节点的第一权限的访问状态。
本公开实施例中，在操作系统装载时，生成第一权限服务和设定数据库，在所述设定数据库中设置关于设备节点的第一权限数据项为默认值。这里，操作系统主要包括Linux系统。
本领域技术人员应当理解，本公开实施例的技术方案适用于所有不具有设备节点相应权限管理的操作系统中。在本公开的实施例中，Linux系统，又称GNU/Linux操作系统，包括但不限于Ubuntu、Redhat、Debian等各种发行版。
第一权限尤指敏感权限；也可以包括普通权限、签名权限及系统签名权限等。访问状态包括拒绝访问状态、同意访问状态以及默认状态等。本公开实施例中，当操作系统装载于电子设备上时，为所有操作系统中的所有敏感设备节点设置默认的第一权限访问状态，即第一权限的访问状态为默认值，所有应用针对敏感设备节点的首次访问均需要用户授权。
本公开实施例中，当用户开启了相应的应用，该应用在开启后需要访问相应的设备时，生成该应用的访问进程，并向设备服务发送针对待访问的第一设备节点的访问请求；设备服务在设定数据库中查找第一设备节点针对所述第一进程对应的应用的第一权限的访问状态，若处于默认状态，需要向第一进程对应的应用返回用户是否授权的相关信息，基于用户授权情况进行开启或拒绝开启；若第一进程对应的应用之前已访问过第一设备节点，则根据之前访问时对应的授权情况确定是否开启该第一设备节点。
步骤102，所述设备服务接收所述第一权限服务返回的第一查询结果，基于所述第一查询结果生成第一反馈信息，将所述第一反馈信息向所述第一进程对应的应用输出。
这里，第一查询结果是表示第一设备节点对于所述第一进程对应的应用的访问权限为默认设置，即该所述第一进程对应的应用首次访问该第一设备节点。此时，所述设备服务需要向所述第一进程对应的应用发送第一反馈信息，以询问用户是否同意访问第一设备节点。本公开实施例中，第一反馈信息主要包括是否同意访问第一设备节点的信息。
步骤103，所述设备服务接收所述第一权限服务返回的第二查询结果，开启所述第一设备节点或向所述第一进程对应的应用输出无开启所述第一设备节点权限的第一提示信息。
本公开实施例中，第二查询结果是指第一进程对应的应用非首次访问第一设备节点，将第一进程对应的应用前一次访问第一设备节点时的第一权限的访问状态作为当前的权限访问状态，若前一次设置为第一设备节点对第一进程对应的应用允许访问，则直接开启 第一设备节点，若前一次设置为第一设备节点对第一进程对应的应用拒绝访问，则拒绝开启第一设备节点，所述设备服务向第一进程对应的应用发送拒绝开启第一设备节点的第一提示信息。
本公开实施例中，所述第一查询结果和所述第二查询结果由所述第一权限服务基于所述第一设备节点的信息和/或所述第一进程的标识信息在设定数据库中查找获取；所述设定数据库中预存储有一个以上设备节点的第一权限针对一种以上应用的访问状态；所述第一进程的标识信息与所述第一进程对应的应用的标识信息相关联。这里，即应用与其自身的进程之间的标识信息相同或紧密关联，通过进程标识能够确定出其对应的应用，基于应用能识别出该应用对应的进程的标识。设定数据库主要是指加密数据库，该加密数据库是为第一权限服务设置的，主要用于存储设备节点的敏感权限的访问状态，以针对不同的应用开启其相应的敏感权限访问，对设备节点进行隐私保护。
本公开实施例中，在步骤102之后，所述方法还包括：所述设备服务接收所述第一进程对应的应用针对所述第一反馈信息的第二指示信息，基于所述第二指示信息开启所述第一设备节点；并触发所述第一权限服务在所述设定数据库中将所述第一设备节点对于所述第一进程对应的应用的第一权限的访问状态修改为允许访问。
这里，第二指示信息即为用户基于第一反馈信息选择了允许第一进程对第一设备节点的访问，同意第一进程对应的应用开启第一设备节点，此时，所述设备服务触发所述第一权限服务在所述设定数据库中将所述第一设备节点对于所述第一进程对应的应用的第一权限的访问状态修改为允许访问，此后，第一进程对应的应用再次访问第一设备节点时，可以直接开启该第一设备节点。
作为一种实现方式，本公开实施例中，在步骤102之后，所述方法还包括：所述设备服务接收所述第一进程对应的应用针对所述第一反馈信息的第三指示信息，基于所述第三指示信息向所述第一进程对应的应用输出无开启所述第一设备节点权限的第一提示信息；并触发所述第一权限服务在所述设定数据库中将所述第一设备节点对于所述第一进程对应的应用的第一权限的访问状态修改为拒绝访问。这里，第三指示信息即为用户基于第一反馈信息选择了拒绝第一进程对第一设备节点的访问，此时，所述设备服务触发所述第一权限服务在所述设定数据库中将所述第一设备节点对于所述第一进程对应的应用的第一权限的访问状态修改为拒绝访问，此后，第一进程对应的应用再次访问第一设备节点时，向所述第一进程对应的应用发送拒绝开启的指示信息，并询问用户是否开启允许访问第一设备节点的信息。
本公开实施例中，所述方法还包括：响应于针对第一权限的查询请求，所述第一权限服务在所述设定数据库中查找所有关于第一权限的数据项，或与所述查询请求中的应用标识信息相关的第一权限的数据项、或与所述查询请求中的设备节点标识信息相关的第一权限的数据项，或与所述查询请求中的进程标识相关的第一权限的数据项，并输出。即，本公开实施例还支持针对第一权限的查询请求，该查询请求可以是默认查询所有的敏感权限信息，既包括设备节点的敏感权限信息，也包括应用的敏感权限信息等，或者，查询请求是查询某个应用对设备节点的敏感权限信息，或查询某个进程(基于进程标识(Process ID，PID))对设备节点的敏感权限信息，或者是查询某个设备节点对哪些应用的敏感权限信息。本公开实施例支持随时对第一权限信息及其访问状态的查询，所支持的查询方式更广泛。
本公开实施例中，所述方法还包括：响应于针对第一权限的数据项的修改请求，所述第一权限服务在所述设定数据库中对相应的第一权限的数据项进行修改，并保存修改后的第一权限的数据项。在查询出相关应用针对设备节点的敏感权限的访问状态或设备节点对应用或其进程的敏感权限访问状态后，用户可以基于相应的场景随时修改敏感权限的访问状态，修改后的敏感权限访问状态将被记录保存于设定数据库即保密数据库中。这里的修改包括对原有敏感权限的访问状态的相关值的修改，也包括对敏感权限的访问状态的添加或删除等修改。
以下结合具体示例，对本公开实施例的技术方案作进一步的详细说明。这里，以操作系统为Linux系统为例，其他操作系统也适用于本公开实施例的技术方案。
本公开实施例中，通过在Linux系统中创建敏感权限的服务程序(第一权限服务)，以保存应用的敏感权限动态调整的信息。本公开实施例中，主要是对设备节点敏感权限(第一权限)的访问状态进行设置及管理。Linux系统中除敏感权限外，还包括普通权限、签名权限及系统签名权限等。其中：
普通权限(normal permission)也叫正常权限，即使拥有了该类权限，用户的隐私数据被泄露篡改的风险也比较大。例如，设置时区的权限就是正常权限。如果应用声明其需要正常权限，系统会自动向应用授予该权限。
敏感权限(dangerous permission)也叫危险权限，运行时其权限访问状态与普通权限相反，一旦某个应用获取了该类权限，用户的隐私数据就面临被泄露篡改的风险。比如READ_CONTACTS权限就属于危险权限。如果应用声明其需要危险权限，则用户必须明确向应用授予该权限。
签名权限(signature permission)：该类权限只对拥有相同签名的应用开放，比如手机QQ自定义了一个许可(permission)且在权限标签中加入android:protectionLevel＝“signature”，而访问它的某个数据时，必须要拥有该权限。然后微信和QQ发布时采用相同的签名，微信就可以申请访问QQ中的此权限，并使用对应权限控制的数据。其他程序即使获知了该开放数据的接口，也在Manifest注册了权限，但由于应用签名不同，仍无法访问的对应的数据。
系统签名权限(signatureOrSystem permission)：与signature permission类似，但其不仅要求签名相同，还要求是同类的系统级应用，一般手机厂商开发的预制场景下才会用到该类权限。
本公开实施例中，Linux设备节点是指：在Linux中，所有设备都以文件的形式存放在/dev目录下，设备节点均通过文件的方式进行访问，设备节点是Linux内核对设备的抽象，一个设备节点就是一个文件。应用程序通过一组标准化的调用执行访问设备，这些调用独立于任何特定的驱动程序。而驱动程序负责将这些标准调用映射到实际硬件的特有操作。/dev目录下的文件节点被称为特殊设备节点。所谓节点是指入口，通过这样的入口来达到操作(读、写等)某设备的目的，而之所以要统一在/dev设置相应的入口，是因为Linux系统提供了相应的虚拟文件系统，其可以使用一致的函数接口(open()、read()、write()、close()……)等来操作各种不同的设备，这可以大大降低应用程序访问Linux外围设备的复杂性。本公开实施例正是针对Linux系统中的设备节点，设置其对应的敏感权限访问状 态的管理。即当前的Linux系统中没有针对访问设备权限进行管理的方法，本公开实施例在Linux系统中提供了相应的动态管理应用使用权限的方法。
图2为本公开实施例的操作系统中权限控制的架构示意图，如图2所示，本公开实施例中，操作系统中的相关应用(App)对Linux设备节点访问时，由于对Linux设备节点的敏感权限的访问状态作了管理控制，因此，App在调用Linux设备节点时，需要通过设备服务获取待调用的Linux设备节点的敏感权限的访问状态，具体地，设备服务向敏感权限服务发送查询请求，敏感权限服务查询相应的加密数据库，获取当前的应用对待访问的Linux设备节点的敏感权限的访问状态，并基于相应的访问状态作出相应的访问管理。
即通过在Linux系统中通过创建敏感权限的服务程序，并为敏感权限服务设置相应的保密数据库，保存应用的敏感权限的访问状态的动态调整的信息，方便相关应用基于敏感权限的访问状态来访问相应的设备节点。
所有Linux安装的应用，默认敏感权限都为询问是否允许访问设备节点的权限，当应用启动访问设备节点的敏感权限时比如使用设备麦克风，麦克风服务调用敏感权限服务，查询该应用是否允许访问麦克风，如果允许访问则为应用开启麦克风功能，如果不允许访问则返回打开麦克风失败的提示信息，在询问状态的场景下，可以弹出系统对话框，由用户选择是否为允许相关应用访问设备节点，用户作出敏感权限的选择后，将用户选择的敏感权限的访问状态保存到敏感权限服务程序的加密数据库中。
图3为本公开实施例的操作系统中权限控制方法的流程示意图，如图3所示，本公开实施例的权限控制方法包括：
Linux系统启动时运行敏感权限服务程序，敏感权限服务程序生成加密数据库，存储应用包名信息与敏感权限信息的对应关系。
当App访问具有敏感权限的设备节点时，设备相关服务在打开Linux设备节点时，访问敏感权限服务程序查询该应用的敏感权限的访问状态。即当App需要访问具有敏感权限的设备节点时，Linux设备服务获取当前App的进程PID信息。
应用通过进程间通信(Inter-Process Communication，IPC)查询敏感权限信息时，将应用PID和具体使用的敏感信息作为参数同时发送给敏感权限服务程序。即Linux设备服务向敏感权限服务发送设备节点的敏感权限的访问状态。此时，敏感权限服务根据进程的PID查询该PID针对设备节点的敏感权限的访问状态，并根据查询到的敏感权限的访问状态作出相应的管理策略。
敏感权限服务程序可以根据PID查询应用包名等信息。本公开实施例中，敏感权限的访问状态包括至少三个状态：默认状态、拒绝状态，允许状态。
当敏感权限查询到应用对设备节点的访问权限为默认状态时，弹出系统弹框，询问用户是同意还是拒绝访问Linux设备节点功能。并根据用户所选择的运行访问或拒绝访问继续以下的流程。
当敏感权限查询到应用对设备节点的访问权限为拒绝状态时，返回拒绝访问设备节点的相关信息，禁止开启该Linux设备节点的功能。
当敏感权限查询到应用对设备节点的访问权限为允许状态时，正常开启该Linux设备节点的功能。
前述步骤中，在用户在系统弹框选择了敏感权限的状态后，执行对设备节点的开启或拒绝开启，此时，敏感权限服务程序将应用包名等信息，针对设备节点的访问的选择后的敏感权限访问状态同时存放在加密数据库中，以在应用下次访问时基于该选择后的敏感权限访问状态管理设备节点的敏感权限。
本公开实施例中，当应用请求使用相机、麦克风等敏感设备时，Linux设备节点的服务程序通过本地IPC通信机制，反向读取请求应用PID信息，保存应用的PID信息。Linux设备节点服务在打开Linux设备节点之前通过本地IPC通信机制调用敏感权限服务程序查询敏感权限接口，查询参数可以包括应用PID信息和访问的设备节点的信息，敏感权限服务收到查询参数后根据自身的加密数据库中所存储的相关数据，若为默认值，弹出系统弹框询问用户是否允许访问设备节点，用户选择后根据用户选择的结果保存到自己的加密数据库中，下次访问该敏感权限时直接返回结果。若为非首次访问，则直接基于加密数据库中的设备节点的敏感权限的访问状态开启或拒绝开启相关的设备节点。
图4为本公开实施例的操作系统中权限设置的架构示意图，如图4所示，本公开实施例中，还支持针对敏感权限访问状态的查询及修改设置的功能，通过App中的系统设置功能，可以通过敏感权限服务在加密数据库中查询到该应用针对设备节点的敏感权限的访问状态。即本公开实施例可以为App提供相应的查询接口，以查询所有敏感权限信息，如可以查询某个应用包的敏感权限信息，查询某个PID的敏感权限信息，设置某个应用包的敏感权限信息，删除某个应用包的敏感权限信息，在加密数据库中创建并存储敏感权限信息等。加密数据库中关于敏感权限的访问状态的存储数据包括有应用包名，二进制可执行文件名，敏感权限名，敏感权限状态等信息。本公开实施例中，根据PID查询应用进程名，根据进程名查询应用包名信息，敏感权限状态具体包括：
Figure PCTCN2022105297-appb-000001
本领域技术人员应当理解，上述的敏感权限的访问状态仅为示例性说明，并非是用于限定敏感权限的访问状态，也支持其他状态设定。
本公开实施例中，App中的系统设置可以调用敏感权限服务接口查询应用敏感权限信息，并修改加密数据库中的敏感权限的相关信息。
图5为本公开实施例的操作系统中权限控制装置的组成结构示意图，如图5所示，本公开实施例的操作系统中权限控制装置包括：
查询单元50，用于响应于第一进程对第一设备节点的访问请求，向第一权限服务查询所述第一进程对所述第一设备节点的第一权限的访问状态；
第一接收单元51，用于接收所述第一权限服务返回的第一查询结果；
第一生成单元52，用于基于所述第一查询结果生成第一反馈信息；
输出单元53，用于将所述第一反馈信息向所述第一进程对应的应用输出；
第二接收单元54，用于接收所述第一权限服务返回的第二查询结果；
处理单元55，用于响应于所述第二查询结果，开启所述第一设备节点或向所述第一进程对应的应用输出无开启所述第一设备节点权限的第一提示信息；
其中，所述第一查询结果和所述第二查询结果由所述第一权限服务基于所述第一设备节点的信息和/或所述第一进程的标识信息在设定数据库中查找获取；所述设定数据库中预存储有一个以上设备节点的第一权限针对一种以上应用的访问状态；所述第一进程的标识信息与所述第一进程对应的应用的标识信息相关联。
在一个实施例中，在图5所示的操作系统中权限控制装置的基础上，本公开实施例的操作系统中权限控制装置还包括：
第三接收单元(图5中未示出)，用于接收所述第一进程对应的应用针对所述第一反馈信息的第二指示信息；
所述处理单元55还用于，基于所述第二指示信息开启所述第一设备节点；并触发所述第一权限服务在所述设定数据库中将所述第一设备节点对于所述第一进程对应的应用的第一权限的访问状态修改为允许访问。
在一个实施例中，在图5所示的操作系统中权限控制装置的基础上，本公开实施例的操作系统中权限控制装置还包括：
第四接收单元(图5中未示出)，用于接收所述第一进程对应的应用针对所述第一反馈信息的第三指示信息；
所述处理单元55还用于，基于所述第三指示信息向所述第一进程对应的应用输出无开启所述第一设备节点权限的第一提示信息；并触发所述第一权限服务在所述设定数据库中将所述第一设备节点对于所述第一进程对应的应用的第一权限的访问状态修改为拒绝访问。
在一个实施例中，所述处理单元55，还用于：
响应于针对第一权限的查询请求，触发所述第一权限服务在所述设定数据库中查找所有关于第一权限的数据项，或与所述查询请求中的应用标识信息相关的第一权限的数据项、或与所述查询请求中的设备节点标识信息相关的第一权限的数据项，或与所述查询请求中的进程标识相关的第一权限的数据项，并输出。
在一个实施例中，所述处理单元55，还用于：
响应于针对第一权限的数据项的修改请求，所述第一权限服务在所述设定数据库中对相应的第一权限的数据项进行修改，并保存修改后的第一权限的数据项。
在一个实施例中，在图5所示的操作系统中权限控制装置的基础上，本公开实施例的操作系统中权限控制装置还包括：
第二生成单元(图5中未示出)，用于响应于所述操作系统的装载，生成所述第一权限服务和所述设定数据库，在所述设定数据库中设置关于设备节点的第一权限数据项为默认值。
在示例性实施例中，查询单元50、第一接收单元51、第一生成单元52、输出单元53、第二接收单元54、第三接收单元、第四接收单元和第二生成单元等可以被一个或多个中央处理器(CPU，Central Processing Unit)、应用专用集成电路(ASIC，Application Specific Integrated Circuit)、数字信号处理器(Digital Signal Processor，DSP)、可编程逻辑器件(PLD，Programmable Logic Device)、复杂可编程逻辑器件(CPLD，Complex Programmable Logic  Device)、现场可编程门阵列(FPGA，Field-Programmable Gate Array)、通用处理器、控制器、微控制器(MCU，Micro Controller Unit)、微处理器(Microprocessor)、或其他电子元件实现，用于执行前述实施例的操作系统中权限控制方法的步骤。
在本公开实施例中，图5示出的操作系统中权限控制装置中各个单元执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
下面，参考图6来描述根据本公开实施例的电子设备11。
如图6所示，电子设备11包括一个或多个处理器111和存储器112。
处理器111可以是中央处理单元(CPU)或者具有数据处理能力和/或指令执行能力的其他形式的处理单元，并且可以控制电子设备11中的其他组件以执行期望的功能。
存储器112可以包括一个或多个计算机程序产品，所述计算机程序产品可以包括各种形式的计算机可读存储介质，例如易失性存储器和/或非易失性存储器。所述易失性存储器例如可以包括随机存取存储器(RAM，Random Access Memory)和/或高速缓冲存储器(cache)等。所述非易失性存储器例如可以包括只读存储器(ROM，Read Only Memory)、硬盘、闪存等。在所述计算机可读存储介质上可以存储一个或多个计算机程序指令，处理器111可以运行所述程序指令，以实现上文所述的本公开的各个实施例的操作系统中权限控制方法以及/或者其他期望的功能。在所述计算机可读存储介质中还可以存储诸如输入信号、信号分量、噪声分量等各种内容。
在一个示例中，电子设备11还可以包括：输入装置113和输出装置114，这些组件通过总线系统和/或其他形式的连接机构(图6中未示出)互连。
该输入装置113可以包括例如键盘、鼠标等等。
该输出装置114可以向外部输出各种信息，包括确定出的距离信息、方向信息等。该输出装置114可以包括例如显示器、扬声器、打印机、以及通信网络及其所连接的远程输出设备等等。
当然，为了简化，图6中仅示出了该电子设备11中与本公开有关的组件中的一些，省略了诸如总线、输入/输出接口等等的组件。除此之外，根据具体应用情况，电子设备11还可以包括任何其他适当的组件。
本公开实施例还记载了一种存储介质，其上存储有可执行程序，所述可执行程序被处理器执行前述实施例的操作系统中权限控制方法的步骤。
除了上述方法和设备以外，本公开的实施例还可以是计算机程序产品，其包括计算机程序指令，所述计算机程序指令在被处理器运行时使得所述处理器执行本说明书上述“示例性方法”部分中描述的根据本公开各种实施例的方法中的步骤。
所述计算机程序产品可以以一种或多种程序设计语言的任意组合来编写用于执行本公开实施例操作的程序代码，所述程序设计语言包括面向对象的程序设计语言，诸如Java、C++等，还包括常规的过程式程序设计语言，诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算设备上执行、部分地在用户设备上执行、作为一个独立的软件包执行、部分在用户计算设备上部分在远程计算设备上执行、或者完全在远程计算设备或服务器上执行。
此外，本公开的实施例还可以是计算机可读存储介质，其上存储有计算机程序指令，所述计算机程序指令在被处理器运行时使得所述处理器执行本说明书上述“示例性方法”部分中描述的根据本公开各种实施例的方法中的步骤。
所述计算机可读存储介质可以采用一个或多个可读介质的任意组合。可读介质可以是可读信号介质或者可读存储介质。可读存储介质例如可以包括但不限于电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。可读存储介质的更具体的例子(非穷举的列表)包括：具有一个或多个导线的电连接、便携式盘、硬盘、随机存取存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(EPROM，Erasable Programmable Read-Only Memory或闪存)、光纤、便携式紧凑盘只读存储器(Compact Disc Read-Only Memory，CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。
本公开的实施例还可以是计算机程序，该计算机程序在被处理器执行时实现前述实施例的操作系统中权限控制方法的步骤。
以上结合具体实施例描述了本公开的基本原理，但是，需要指出的是，在本公开中提及的优点、优势、效果等仅是示例而非限制，不能认为这些优点、优势、效果等是本公开的各个实施例必须具备的。另外，上述公开的具体细节仅是为了示例的作用和便于理解的作用，而非限制，上述细节并不限制本公开为必须采用上述具体的细节来实现。
本公开中涉及的器件、装置、设备、系统的方框图仅作为例示性的例子并且不意图要求或暗示必须按照方框图示出的方式进行连接、布置、配置。如本领域技术人员将认识到的，可以按任意方式连接、布置、配置这些器件、装置、设备、系统。诸如“包括”、“包含”、“具有”等等的词语是开放性词汇，指“包括但不限于”，且可与其互换使用。这里所使用的词汇“或”和“和”指词汇“和/或”，且可与其互换使用，除非上下文明确指示不是如此。这里所使用的词汇“诸如”指词组“如但不限于”，且可与其互换使用。
还需要指出的是，在本公开的装置、设备和方法中，各部件或各步骤是可以分解和/或重新组合的。这些分解和/或重新组合应视为本公开的等效方案。
提供所公开的方面的以上描述以使本领域的任何技术人员能够做出或者使用本公开。对这些方面的各种修改对于本领域技术人员而言是非常显而易见的，并且在此定义的一般原理可以应用于其他方面而不脱离本公开的范围。因此，本公开不意图被限制到在此示出的方面，而是按照与在此公开的原理和新颖的特征一致的最宽范围。
为了例示和描述的目的已经给出了以上描述。此外，此描述不意图将本公开的实施例限制到在此公开的形式。尽管以上已经讨论了多个示例方面和实施例，但是本领域技术人员将认识到其某些变型、修改、改变、添加和子组合。

Claims (16)

  1. 一种操作系统中权限控制方法，其特征在于，所述方法包括：
    响应于第一进程对第一设备节点的访问请求，设备服务向第一权限服务查询所述第一进程对所述第一设备节点的第一权限的访问状态；
    所述设备服务接收所述第一权限服务返回的第一查询结果，基于所述第一查询结果生成第一反馈信息，将所述第一反馈信息向所述第一进程对应的应用输出；或所述设备服务接收所述第一权限服务返回的第二查询结果，开启所述第一设备节点或向所述第一进程对应的应用输出无开启所述第一设备节点权限的第一提示信息；
    其中，所述第一查询结果和所述第二查询结果由所述第一权限服务基于所述第一设备节点的信息和/或所述第一进程的标识信息在设定数据库中查找获取；所述设定数据库中预存储有一个以上设备节点的第一权限针对一种以上应用的访问状态；所述第一进程的标识信息与所述第一进程对应的应用的标识信息相关联。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述设备服务接收所述第一进程对应的应用针对所述第一反馈信息的第二指示信息，基于所述第二指示信息开启所述第一设备节点；并触发所述第一权限服务在所述设定数据库中将所述第一设备节点对于所述第一进程对应的应用的第一权限的访问状态修改为允许访问。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    所述设备服务接收所述第一进程对应的应用针对所述第一反馈信息的第三指示信息，基于所述第三指示信息向所述第一进程对应的应用输出无开启所述第一设备节点权限的第一提示信息；并触发所述第一权限服务在所述设定数据库中将所述第一设备节点对于所述第一进程对应的应用的第一权限的访问状态修改为拒绝访问。
  4. 根据权利要求1至3任一项所述的方法，其特征在于，所述方法还包括：
    响应于针对第一权限的查询请求，所述第一权限服务在所述设定数据库中查找所有关于第一权限的数据项，或与所述查询请求中的应用标识信息相关的第一权限的数据项、或与所述查询请求中的设备节点标识信息相关的第一权限的数据项，或与所述查询请求中的进程标识相关的第一权限的数据项，并输出。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    响应于针对第一权限的数据项的修改请求，所述第一权限服务在所述设定数据库中对相应的第一权限的数据项进行修改，并保存修改后的第一权限的数据项。
  6. 根据权利要求1至5任一项所述的方法，其特征在于，所述方法还包括：
    响应于所述操作系统的装载，生成所述第一权限服务和所述设定数据库，在所述设定数据库中设置关于设备节点的第一权限数据项为默认值。
  7. 一种操作系统中权限控制装置，其特征在于，所述装置包括：
    查询单元，用于响应于第一进程对第一设备节点的访问请求，向第一权限服务查询所述第一进程对所述第一设备节点的第一权限的访问状态；
    第一接收单元，用于接收所述第一权限服务返回的第一查询结果；
    第一生成单元，用于基于所述第一查询结果生成第一反馈信息；
    输出单元，用于将所述第一反馈信息向所述第一进程对应的应用输出；
    第二接收单元，用于接收所述第一权限服务返回的第二查询结果；
    处理单元，用于响应于所述第二查询结果，开启所述第一设备节点或向所述第一进程对应的应用输出无开启所述第一设备节点权限的第一提示信息；
    其中，所述第一查询结果和所述第二查询结果由所述第一权限服务基于所述第一设备节点的信息和/或所述第一进程的标识信息在设定数据库中查找获取；所述设定数据库中预存储有一个以上设备节点的第一权限针对一种以上应用的访问状态；所述第一进程的标识信息与所述第一进程对应的应用的标识信息相关联。
  8. 根据权利要求7所述的装置，其特征在于，所述装置还包括：
    第三接收单元，用于接收所述第一进程对应的应用针对所述第一反馈信息的第二指示信息；
    所述处理单元还用于，基于所述第二指示信息开启所述第一设备节点；并触发所述第一权限服务在所述设定数据库中将所述第一设备节点对于所述第一进程对应的应用的第一权限的访问状态修改为允许访问。
  9. 根据权利要求7或8所述的装置，其特征在于，所述装置还包括：
    第四接收单元，用于接收所述第一进程对应的应用针对所述第一反馈信息的第三指示信息；
    所述处理单元还用于，基于所述第三指示信息向所述第一进程对应的应用输出无开启所述第一设备节点权限的第一提示信息；并触发所述第一权限服务在所述设定数据库中将所述第一设备节点对于所述第一进程对应的应用的第一权限的访问状态修改为拒绝访问。
  10. 根据权利要求7至9任一项所述的装置，其特征在于，所述处理单元，还用于：
    响应于针对第一权限的查询请求，触发所述第一权限服务在所述设定数据库中查找所有关于第一权限的数据项，或与所述查询请求中的应用标识信息相关的第一权限的数据项、或与所述查询请求中的设备节点标识信息相关的第一权限的数据项，或与所述查询请求中的进程标识相关的第一权限的数据项，并输出。
  11. 根据权利要求10所述的装置，其特征在于，所述处理单元，还用于：
    响应于针对第一权限的数据项的修改请求，所述第一权限服务在所述设定数据库中对相应的第一权限的数据项进行修改，并保存修改后的第一权限的数据项。
  12. 根据权利要求7至11任一项所述的装置，其特征在于，所述装置还包括：
    第二生成单元，用于响应于所述操作系统的装载，生成所述第一权限服务和所述设定数据库，在所述设定数据库中设置关于设备节点的第一权限数据项为默认值。
  13. 一种电子设备，包括处理器、存储器及存储在存储器上并能够由所述处理器运行的可执行程序，所述处理器运行所述可执行程序时执行如权利要求1至6任一项所述的操作系统中权限控制方法的步骤。
  14. 一种存储介质，其上存储由可执行程序，所述可执行程序被处理器执行时实现如权利要求1至6任一项所述的操作系统中权限控制方法的步骤。
  15. 一种计算机程序产品，其特征在于，包括计算机程序，所述计算机程序在被处理器执行时实现如权利要求1至6任一项所述的操作系统中权限控制方法的步骤。
  16. 一种计算机程序，其特征在于，所述计算机程序被处理器执行时实现如权利要求1至6任一项所述的操作系统中权限控制方法的步骤。
PCT/CN2022/105297 2021-10-14 2022-07-12 操作系统中权限控制方法及装置、电子设备、存储介质 WO2023060957A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111196972.9 2021-10-14
CN202111196972.9A CN113987505A (zh) 2021-10-14 2021-10-14 操作系统中权限控制方法及装置、电子设备、存储介质

Publications (1)

Publication Number Publication Date
WO2023060957A1 true WO2023060957A1 (zh) 2023-04-20

Family

ID=79738576

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/105297 WO2023060957A1 (zh) 2021-10-14 2022-07-12 操作系统中权限控制方法及装置、电子设备、存储介质

Country Status (2)

Country Link
CN (1) CN113987505A (zh)
WO (1) WO2023060957A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024095195A1 (en) 2022-11-02 2024-05-10 Nextkidney Sa Sorbent device for regeneration of dialysate

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113987505A (zh) * 2021-10-14 2022-01-28 北京鲸鲮信息系统技术有限公司 操作系统中权限控制方法及装置、电子设备、存储介质
CN117633818A (zh) * 2022-08-15 2024-03-01 华为技术有限公司 应用敏感行为提醒方法、相关装置及通信系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102289633A (zh) * 2011-09-02 2011-12-21 广东欧珀移动通信有限公司 Android平台下的应用程序动态权限管理方法
CN103617380A (zh) * 2013-11-28 2014-03-05 北京邮电大学 应用程序权限动态控制方法和系统
CN105094996A (zh) * 2015-07-21 2015-11-25 电子科技大学 基于动态权限验证的Android系统安全增强方法及系统
US11012452B1 (en) * 2018-01-09 2021-05-18 NortonLifeLock, Inc. Systems and methods for establishing restricted interfaces for database applications
CN113987505A (zh) * 2021-10-14 2022-01-28 北京鲸鲮信息系统技术有限公司 操作系统中权限控制方法及装置、电子设备、存储介质

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103294940A (zh) * 2013-05-23 2013-09-11 广东欧珀移动通信有限公司 一种Android系统权限控制方法及移动智能终端
CN103905651A (zh) * 2014-04-30 2014-07-02 北京邮电大学 智能终端中应用权限管理方法及系统
US9787685B2 (en) * 2014-06-24 2017-10-10 Xiaomi Inc. Methods, devices and systems for managing authority

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102289633A (zh) * 2011-09-02 2011-12-21 广东欧珀移动通信有限公司 Android平台下的应用程序动态权限管理方法
CN103617380A (zh) * 2013-11-28 2014-03-05 北京邮电大学 应用程序权限动态控制方法和系统
CN105094996A (zh) * 2015-07-21 2015-11-25 电子科技大学 基于动态权限验证的Android系统安全增强方法及系统
US11012452B1 (en) * 2018-01-09 2021-05-18 NortonLifeLock, Inc. Systems and methods for establishing restricted interfaces for database applications
CN113987505A (zh) * 2021-10-14 2022-01-28 北京鲸鲮信息系统技术有限公司 操作系统中权限控制方法及装置、电子设备、存储介质

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024095195A1 (en) 2022-11-02 2024-05-10 Nextkidney Sa Sorbent device for regeneration of dialysate

Also Published As

Publication number Publication date
CN113987505A (zh) 2022-01-28

Similar Documents

Publication Publication Date Title
WO2023060957A1 (zh) 操作系统中权限控制方法及装置、电子设备、存储介质
JP5592969B2 (ja) セキュアなブラウザベースのアプリケーション
US9465955B1 (en) System for and methods of controlling user access to applications and/or programs of a computer
JP6248153B2 (ja) 信頼レベルのアクティブ化
US5572711A (en) Mechanism for linking together the files of emulated and host system for access by emulated system users
US9773102B2 (en) Selective file access for applications
US9589131B2 (en) Method and computer device to control software file downloads
US7647629B2 (en) Hosted code runtime protection
US10831915B2 (en) Method and system for isolating application data access
JP2002182983A (ja) データベースへのアクセス制御方法、データベース装置、リソースへのアクセス制御方法、情報処理装置
US10592660B2 (en) Capability access management
CN113268450A (zh) 文件访问方法及装置、电子设备、存储介质
JP2006107505A (ja) アクセス認可のａｐｉ
JP2006526219A (ja) セキュアなファームウェア格納及びサービスアクセスを提供する方法及び装置
US8732811B2 (en) Systems and methods for implementing security services
JP5069369B2 (ja) 統合されたアクセス認可
CN113935014A (zh) 设备节点的开启控制方法及装置、电子设备、存储介质
US11983288B1 (en) Operating system enhancements to prevent surreptitious access to user data files
JP4638505B2 (ja) 電子デバイス内の安全なプログラム解釈方法
CN114417323B (zh) 数据引用方法、装置、设备及介质
CN112580023A (zh) 影子栈管理方法及装置、介质、设备
JP2008521111A5 (zh)

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22879904

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 16.07.2024)