CN115659296A - File verification method, device and equipment and readable storage medium - Google Patents
File verification method, device and equipment and readable storage medium Download PDFInfo
- Publication number
- CN115659296A CN115659296A CN202211288917.7A CN202211288917A CN115659296A CN 115659296 A CN115659296 A CN 115659296A CN 202211288917 A CN202211288917 A CN 202211288917A CN 115659296 A CN115659296 A CN 115659296A
- Authority
- CN
- China
- Prior art keywords
- file
- authority
- verified
- standard
- referred
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
- 238000012795 verification Methods 0.000 title claims abstract description 63
- 238000000034 method Methods 0.000 title claims abstract description 33
- 238000009434 installation Methods 0.000 claims description 13
- 238000005538 encapsulation Methods 0.000 claims description 7
- 238000012360 testing method Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 238000004064 recycling Methods 0.000 description 1
Images
Landscapes
- Storage Device Security (AREA)
Abstract
The application discloses a file verification method, a device, equipment and a readable storage medium, comprising the following steps: acquiring a file to be verified; calling the referred authority of the file to be verified through a debugging bridge command; determining a standard authority corresponding to the file to be verified according to the file type of the file to be verified and an authority list, wherein the authority list comprises a corresponding relation between the file type and the standard authority; judging whether the consulted authority is the same as the standard authority or not; and if the consulted authority is the same as the standard authority, determining that the file to be verified passes the verification. Therefore, the authority to be referred of the file to be verified can be automatically called through the debugging bridge command, whether the authority to be referred accords with the standard authority or not is automatically judged, the verification result of the file to be verified is automatically generated, and compared with the mode that the authority to be referred of each file needs to be called through manually opening the file attribute in the prior art, whether the authority to be referred accords with the standard or not is manually judged, the verification efficiency of the file is effectively improved.
Description
Technical Field
The present application relates to the field of testing, and in particular, to a method, an apparatus, a device and a readable storage medium for verifying a file.
Background
An operating system of a mobile terminal such as a mobile phone, for example, an android (android) system, generally has dozens of applications, and is used by a user. However, if the applications are safe, that is, if there is a security risk of revealing personal information of the user, such as a phone number, an address book, an account, a password, and the like, a test is required.
Specifically, when an inappropriate referred right is assigned to an application file in the android client, other applications may read and acquire the content of the application file, and the risk of user information leakage is increased. When the referred authority of the application files is verified in the prior art, the referred authority of each file is manually called, whether the referred authority meets the standard or not is manually judged, when the number of the application files to be verified is large, the referred authority of each file can be checked only by spending very large manpower and long time, and the verification efficiency is low.
Disclosure of Invention
The embodiment of the application provides a file verification method, a file verification device, equipment and a readable storage medium, which can automatically call the referred authority of a file to be verified, automatically judge whether the referred authority meets the standard authority, and automatically generate a verification result of the file to be verified.
In view of this, an embodiment of the present application provides a file verification method, including:
acquiring a file to be verified;
calling the consulted authority of the file to be verified through a debugging bridge command;
determining a standard authority corresponding to the file to be verified according to the file type of the file to be verified and an authority list, wherein the authority list comprises a corresponding relation between the file type and the standard authority;
judging whether the referred authority is the same as the standard authority;
and if the referred authority is the same as the standard authority, determining that the file to be verified passes the verification.
Optionally, the invoking of the referred authority of the file to be authenticated through a debug bridge command includes:
switching to a root authority mode through a debugging bridge command;
and calling the referred authority of the file to be verified from the installation directory of the file to be verified through an encapsulation command in the root authority mode.
Optionally, the method further comprises:
and if the consulted authority is different from the standard authority, determining that the verification of the verification file fails, and sending an alarm prompt.
Optionally, the method of claim 1, further comprising:
acquiring the file content of the file to be verified;
judging whether the file to be verified comprises sensitive information or not according to the file content and a preset sensitive information base;
and if the file to be verified does not comprise the sensitive information, determining that the file to be verified passes the verification.
An embodiment of the present application further provides a file verification apparatus, including:
the acquisition unit is used for acquiring a file to be verified;
the invoking unit is used for invoking the consulted authority of the file to be verified through a debugging bridge command;
the first determining unit is used for determining the standard authority corresponding to the file to be verified according to the file type of the file to be verified and an authority list, wherein the authority list comprises the corresponding relation between the file type and the standard authority;
a judging unit configured to judge whether the referred authority is the same as the standard authority;
and the second determining unit is used for determining that the file to be verified passes the verification if the referred authority is the same as the standard authority.
Optionally, the invoking unit is specifically configured to:
switching to a root authority mode through a debugging bridge command;
and calling the referred authority of the file to be verified from the installation directory of the file to be verified through an encapsulation command in the root authority mode.
Optionally, the apparatus further comprises:
the second determining unit is further used for determining that the verification file fails to verify if the referred authority is different from the standard authority;
and the alarm unit is used for sending out an alarm prompt if the consulted authority is different from the standard authority.
Optionally, the apparatus further comprises:
the acquiring unit is further configured to acquire file content of the file to be verified;
the judging unit is further used for judging whether the file to be verified comprises sensitive information according to the file content and a preset sensitive information base;
the second determining unit is further configured to determine that the to-be-verified file passes verification if the to-be-verified file does not include sensitive information.
An embodiment of the present application further provides a computer device, including: a memory, a processor, and a bus system;
wherein the memory is used for storing programs;
the processor is used for executing the program in the memory to realize any one of the file verification methods;
the bus system is used for connecting the memory and the processor so as to enable the memory and the processor to communicate.
An embodiment of the present application further provides a computer-readable storage medium, which is characterized by storing instructions that, when executed on a computer, cause the computer to execute any one of the file verification methods described above.
The embodiment of the application provides a file verification method, which comprises the following steps: acquiring a file to be verified; calling the referred authority of the file to be verified through a debugging bridge command; determining a standard authority corresponding to the file to be verified according to the file type of the file to be verified and an authority list, wherein the authority list comprises a corresponding relation between the file type and the standard authority; judging whether the referred authority is the same as the standard authority; and if the consulted authority is the same as the standard authority, determining that the file to be verified passes the verification. Therefore, the authority to be referred of the file to be verified can be automatically called through the debugging bridge command, whether the authority to be referred accords with the standard authority or not is automatically judged, the verification result of the file to be verified is automatically generated, and compared with the mode that the authority to be referred of each file needs to be called through manually opening the file attribute in the prior art, whether the authority to be referred accords with the standard or not is manually judged, the verification efficiency of the file is effectively improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the embodiments or the prior art descriptions will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a schematic flowchart of a document verification method according to an embodiment of the present disclosure;
fig. 2 is a schematic structural diagram of a document authentication apparatus according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terms "first," "second," "third," "fourth," and the like in the description and claims of this application and in the preceding drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
When a certain application file in the android client is assigned with improper consulted rights, other applications can read and acquire the content of the application file, and the risk of user information leakage is increased. When the referred authority of the application files is verified in the prior art, the referred authority of each file is manually called, whether the referred authority meets the standard or not is manually judged, when the number of the application files to be verified is large, the referred authority of each file can be checked only by spending very large manpower and long time, and the verification efficiency is low.
Therefore, in order to solve the above problems, embodiments of the present application provide a file verification method, an apparatus, a device, and a readable storage medium, which can automatically retrieve the referred permission of a file to be verified, automatically determine whether the referred permission meets a standard permission, and automatically generate a verification result of the file to be verified.
Referring to fig. 1, a document verification method provided in an embodiment of the present application includes the following steps.
S101, obtaining a file to be verified.
In this embodiment, a to-be-verified file that needs to be verified can be obtained first. Specifically, the installation package of the application software may be obtained first, the application software is installed in the specified path through the debug bridge command, all application files in the application software are obtained, and finally the file to be verified is selected from all application files. It can be understood that the file to be verified may be a part of the key file in the whole application file, or may be the whole application file.
S102, calling the referred authority of the file to be verified through a debugging bridge command.
In this embodiment, after the file to be verified is obtained, the referred permission of the file to be verified can be called through the debugging bridge command. It is understood that the Debug Bridge command may be an Android Debug Bridge command (ADB), and ADB is a tool in Android sdk, which can directly operate and manage an Android simulator or a real Android device, and its main functions are to run a shell (command line) of the device, manage port mapping of the simulator or the device, upload/download files between a computer and the device, install local apk software to the simulator or the Android device, and so on. Therefore, the consulted authority of the file to be verified is automatically called through the debugging bridge command, and compared with the prior art that the consulted authority of each file needs to be called through manually opening the file attribute, the file verification efficiency is greatly improved.
In a possible implementation manner, the root authority mode can be switched to by a debugging bridge command; and calling the referred authority of the file to be verified from the installation directory of the file to be verified through an encapsulation command in the root authority mode. It can be understood that the file permissions of all files to be verified under the current directory can be obtained by switching a debugging bridge command Adb shell to a device command line mode, switching a su to a root permission mode, entering an installation directory of the files to be verified under the root permission mode, encapsulating a command ll/x.
S103, determining the standard authority corresponding to the file to be verified according to the file type and the authority list of the file to be verified.
In this embodiment, after the referred authority of the to-be-verified file is called, the file type of the to-be-verified file can be determined, and the standard authority corresponding to the to-be-verified file is determined according to the file type of the to-be-verified file and the authority list, where the authority list includes a corresponding relationship between the file type and the standard authority. It can be understood that an authority list can be established in advance, different standard authorities can be set in advance according to different file types, and the corresponding relationship of the authorities can be stored in the authority list. During verification, the file type of the file to be verified can be determined, and then the standard authority corresponding to the file to be verified is determined according to the file type of the file to be verified and the corresponding relation between the file type recorded in the authority list and the standard authority, so that whether the referred authority meets the standard or not can be determined by judging whether the referred authority of the file to be verified is the same as the standard authority or not.
And S104, judging whether the referred authority is the same as the standard authority or not.
In this embodiment, after the referred permission and the standard permission of the file to be verified are obtained, whether the referred permission is the same as the standard permission can be determined. It can be understood that each application file should have its predefined referred authority, that is, standard authority, and whether the file to be authenticated has the risk of revealing user information can be determined by judging whether the referred authority of the file to be authenticated is the same as the standard authority. For example, if the standard permission of the file to be verified is readable and the referred permission of the file to be verified is readable and writable, it may be determined that the referred permission of the file to be verified is different from that of the file to be verified, and it may be determined that the referred file of the file to be verified does not meet the standard.
And S105, if the referred authority is the same as the standard authority, determining that the file to be verified passes the verification.
In this embodiment, after it is determined that the referred authority is the same as the standard authority, it may be determined that the document to be verified passes verification. It can be understood that after the referred authority is determined to be the same as the standard authority, the document to be verified is determined to have no risk of revealing user information in the aspect of referred authority, and a verification result of 'verification passing' can be automatically output.
In a possible implementation mode, if the consulted authority is different from the standard authority, the verification of the verification file is determined to be failed, and an alarm prompt is sent out. It can be understood that after the consulted authority of the file to be verified is determined to be different from the standard authority, the file to be verified can be determined to have the risk of user information leakage, the verification result of 'verification failure' can be automatically output at the moment, the file name of the file to be verified and the name of the application software to which the file belongs are recorded, and an alarm prompt is sent to a worker.
In a possible implementation manner, the file content of the file to be verified can be obtained; judging whether the file to be verified comprises sensitive information or not according to the file content and a preset sensitive information base; and if the file to be verified does not contain the sensitive information, determining that the file to be verified passes the verification. It can be understood that, in order to further improve the security and compliance of the application file, the file content of the application file may be verified to determine whether the file content contains sensitive information. First, a sensitive information library may be preset, where the sensitive information library includes at least one preset sensitive information, and the sensitive information may include a phone number, communication content, a geographic location, contact information, an account, a password, calendar activity information, and the like. And finally, determining whether the file to be verified passes verification by judging whether the file to be verified comprises the sensitive information, thereby avoiding leakage of user information and improving the safety and the compliance of the application file.
The embodiment of the application provides a file verification method, which comprises the following steps: acquiring a file to be verified; calling the consulted authority of the file to be verified through a debugging bridge command; determining a standard authority corresponding to the file to be verified according to the file type of the file to be verified and an authority list, wherein the authority list comprises a corresponding relation between the file type and the standard authority; judging whether the referred authority is the same as the standard authority or not; and if the referred authority is the same as the standard authority, determining that the file to be verified passes the verification. Therefore, the authority to be referred of the file to be verified can be automatically called through the debugging bridge command, whether the authority to be referred accords with the standard authority or not is automatically judged, the verification result of the file to be verified is automatically generated, and compared with the mode that the authority to be referred of each file needs to be called through manually opening the file attribute in the prior art, whether the authority to be referred accords with the standard or not is manually judged, the verification efficiency of the file is effectively improved.
The following description will be made in conjunction with a practical application scenario:
when an application file of an application needs to be verified, the application needs to be installed firstly, after the application is installed successfully, a corresponding file path is inquired according to an application package name package, then a corresponding file authority is obtained by using an adb command, and if the standard authority of the file authority is readable and the authority of the file is readable and writable, the file authority is considered to be not as expected. In particular, the following steps may be performed:
A. usb connects android devices: and the developer selects to start and open adb debugging, and the root mobile phone and the adb devices can see the corresponding equipment.
B. Installing and applying: encapsulating in the adb command: adb install-path # path is the installation package path.
C. Switching to root authority: and switching the Adb shell to a device command line mode, and switching to the root authority by using su.
D. Acquiring an application file authority list: and entering a file installation directory, encapsulating a command ll/x, and acquiring all file permissions under the current directory.
E. And (4) permission checking: and viewing the returned file authority, if the returned authority is stored, the authority of others can be read and written, and the standard authority is readable, the authority is considered to be not in accordance with the expectation, and the risk exists.
The content of the application file can be verified, and whether the application file contains sensitive information or not can be judged. The corresponding installation folder can be obtained according to the package name package of the application, all files to which the application belongs are copied to the local, whether each file content contains sensitive information or not is checked in a recycling mode, the file content is compared with a sensitive information base, if the file content meets the expectation, the file content is judged to pass, if the file content does not meet the expectation, the file content is judged to not pass, and the following steps can be specifically executed:
A. acquiring an installation file: and the adb pull path1 path2# path1 in the encapsulated adb command is an android device application installation directory, and the path2 is a target storage directory.
B. Reading the file name and the file content: packaging a linux command findpath-name # path as a file path needing to be searched, and adding the path after a return result is obtained to obtain an absolute path of each file; the encapsulation linux command catpath # path is a file absolute path, and file content is obtained.
C. Detecting sensitive information of the file: and comparing the acquired file content with the sensitive information base, and if the file content contains the sensitive information content, determining that the detection is not passed.
Referring to fig. 2, an embodiment of the present application provides a document verification apparatus, including:
an obtaining unit 201, configured to obtain a file to be verified;
the invoking unit 202 is configured to invoke the referred authority of the file to be authenticated through a debug bridge command;
a first determining unit 203, configured to determine a standard permission corresponding to the file to be verified according to the file type of the file to be verified and a permission list, where the permission list includes a correspondence between the file type and the standard permission;
a judging unit 204 for judging whether the referred authority is the same as the standard authority;
a second determining unit 205, configured to determine that the to-be-verified document passes verification if the referred authority is the same as the standard authority.
Optionally, the invoking unit 202 is specifically configured to:
switching to a root authority mode through a debugging bridge command;
and calling the referred authority of the file to be verified from the installation directory of the file to be verified through an encapsulation command in the root authority mode.
Optionally, the apparatus further comprises:
the second determining unit 205 is further configured to determine that the verification document fails to verify if the referred right is different from the standard right;
and the alarm unit is used for sending an alarm prompt if the consulted authority is different from the standard authority.
Optionally, the apparatus further comprises:
the obtaining unit 201 is further configured to obtain file content of the file to be verified;
the judging unit 204 is further configured to judge whether the file to be verified includes sensitive information according to the file content and a preset sensitive information base;
the second determining unit 205 is further configured to determine that the file to be verified passes verification if the file to be verified does not include the sensitive information.
The embodiment of the application provides a verification device of files, can call the authority of being referred to of waiting to verify the file automatically through the debugging bridge order to judge automatically whether being referred to the authority and accord with standard authority, and the verification result of the file of waiting to verify of automatic generation, compare in prior art need call the authority of being referred to of every file through the manual work open file attribute, and the manual work judges the mode of whether according with the standard, effectively promoted the verification efficiency of file.
An embodiment of the present application further provides a computer device, including: a memory, a processor, and a bus system;
wherein the memory is used for storing programs;
the processor is used for executing the program in the memory to realize any one of the file verification methods;
the bus system is used for connecting the memory and the processor so as to enable the memory and the processor to communicate.
Embodiments of the present application further provide a computer-readable storage medium storing instructions, which when executed on a computer, cause the computer to perform any one of the above-mentioned document verification methods.
Finally, it should also be noted that, in this document, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising a," "8230," "8230," or "comprising" does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A method of document authentication, comprising:
acquiring a file to be verified;
calling the referred authority of the file to be verified through a debugging bridge command;
determining a standard authority corresponding to the file to be verified according to the file type of the file to be verified and an authority list, wherein the authority list comprises a corresponding relation between the file type and the standard authority;
judging whether the referred authority is the same as the standard authority;
and if the referred authority is the same as the standard authority, determining that the file to be verified passes the verification.
2. The method according to claim 1, wherein the invoking of the referred authority of the file to be authenticated through a debug bridge command comprises:
switching to a root authority mode through a debugging bridge command;
and calling the referred authority of the file to be verified from the installation directory of the file to be verified through an encapsulation command in the root authority mode.
3. The method of claim 1, further comprising:
and if the consulted authority is different from the standard authority, determining that the verification of the verification file fails, and sending an alarm prompt.
4. The method of claim 1, further comprising:
acquiring the file content of the file to be verified;
judging whether the file to be verified comprises sensitive information or not according to the file content and a preset sensitive information base;
and if the file to be verified does not comprise sensitive information, determining that the file to be verified passes the verification.
5. A document authentication device, comprising:
the acquisition unit is used for acquiring a file to be verified;
the invoking unit is used for invoking the consulted authority of the file to be verified through a debugging bridge command;
the first determining unit is used for determining the standard authority corresponding to the file to be verified according to the file type of the file to be verified and an authority list, wherein the authority list comprises the corresponding relation between the file type and the standard authority;
a judging unit configured to judge whether the referred authority is the same as the standard authority;
and the second determining unit is used for determining that the file to be verified passes the verification if the referred authority is the same as the standard authority.
6. The apparatus according to claim 5, wherein the retrieving unit is specifically configured to:
switching to a root authority mode through a debugging bridge command;
and calling the referred authority of the file to be verified from the installation directory of the file to be verified through an encapsulation command in the root authority mode.
7. The apparatus of claim 5, further comprising:
the second determining unit is further configured to determine that the verification of the verification document fails if the referred permission is different from the standard permission;
and the alarm unit is used for sending an alarm prompt if the consulted authority is different from the standard authority.
8. The apparatus of claim 5, further comprising:
the acquisition unit is further used for acquiring the file content of the file to be verified;
the judging unit is further used for judging whether the file to be verified comprises sensitive information according to the file content and a preset sensitive information base;
the second determining unit is further configured to determine that the file to be verified passes the verification if the file to be verified does not include the sensitive information.
9. A computer device, comprising: a memory, a processor, and a bus system;
wherein the memory is used for storing programs;
the processor is configured to execute a program in the memory to implement the method of any one of claims 1 to 4;
the bus system is used for connecting the memory and the processor so as to enable the memory and the processor to communicate.
10. A computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the method of any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211288917.7A CN115659296A (en) | 2022-10-20 | 2022-10-20 | File verification method, device and equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211288917.7A CN115659296A (en) | 2022-10-20 | 2022-10-20 | File verification method, device and equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115659296A true CN115659296A (en) | 2023-01-31 |
Family
ID=84989879
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211288917.7A Pending CN115659296A (en) | 2022-10-20 | 2022-10-20 | File verification method, device and equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115659296A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116955211A (en) * | 2023-09-21 | 2023-10-27 | 中国标准化研究院 | Standard compliance testing method and device, electronic equipment and storage medium |
-
2022
- 2022-10-20 CN CN202211288917.7A patent/CN115659296A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116955211A (en) * | 2023-09-21 | 2023-10-27 | 中国标准化研究院 | Standard compliance testing method and device, electronic equipment and storage medium |
| CN116955211B (en) * | 2023-09-21 | 2024-01-12 | 中国标准化研究院 | Standard compliance testing method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109032611B (en) | Script deployment method and device, computer equipment and storage medium | |
| CN108427613B (en) | Abnormal interface positioning method and device, computer equipment and storage medium | |
| CN111695156A (en) | Service platform access method, device, equipment and storage medium | |
| CN104360920A (en) | Automatic testing method and device for interface | |
| CN108763951B (en) | Data protection method and device | |
| CN107729198B (en) | Android system firmware verification method and device | |
| CN109669859B (en) | Service testing method, device, computer equipment and storage medium | |
| CN110083384B (en) | Application programming interface creating method and device | |
| CN109726134B (en) | Interface test method and system | |
| CN115659296A (en) | File verification method, device and equipment and readable storage medium | |
| CN111694704A (en) | Debugging information output method and device, electronic equipment and storage medium | |
| CN112559352A (en) | Interface test method, device, equipment and storage medium | |
| CN112650689A (en) | Test method, test device, electronic equipment and storage medium | |
| CN107343103A (en) | Control method and control device of application permission and mobile terminal | |
| WO2020233044A1 (en) | Plug-in verification method and device, and server and computer-readable storage medium | |
| CN111930579A (en) | Test machine deployment permission verification method and device, computer equipment and storage medium | |
| CN114818012B (en) | Linux file integrity measuring method based on white list | |
| CN114579473B (en) | Application testing method, device, equipment and storage medium | |
| CN115758356A (en) | Method, storage medium and equipment for implementing credible static measurement on Android application | |
| CN115587359A (en) | Permission detection method and device of application package, electronic equipment and storage medium | |
| CN113902458A (en) | Malicious user identification method and device and computer equipment | |
| CN113778551A (en) | Method and device for remotely modifying parameters based on multiple clients and computer equipment | |
| CN113986744A (en) | Method and device for testing warehouse and table components and storage medium | |
| CN113342660A (en) | File testing method, device, system, electronic equipment and readable storage medium | |
| CN112383536A (en) | Firewall verification method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |