KR102348312B1 - Method and system for detecting forgery of mobile application using collecting user identifier and signature - Google Patents

Abstract

On the client side, the signature information for the application and the user's identifier (eg, user ID) are transmitted to the server side, and the server side allows the application operator to decide whether to allow or block application authentication according to the business situation, so that all signatures are pre-written. You can flexibly detect forgery of mobile applications without registration.

Description

Mobile application forgery detection method and system using user identifier and signature collection

The following description relates to a mobile application forgery detection method and system using a user identifier and signature collection.

As a prior art for detecting forgery and falsification of mobile applications, the signature information used in the development and distribution of mobile applications is registered in advance in the authentication server to create a white list, and when the mobile application is executed, 'current execution and / or By comparing the 'signature information of the installed mobile application' with the 'signature information registered in the server (signature information registered in the whitelist)', the 'signature information of the currently running and/or installed mobile application' is not registered in the whitelist. In the case of unsigned information, there is a technology that detects that the currently running mobile application is forged or forged on the client side or the server side, and blocks the execution of the mobile application or stops the installation.

However, more and more diverse signature information such as a signature for development, a signature for distribution, and a signature for QA (Quality Assurance) are generated. In order to use the existing forgery detection technology, all signatures must be registered in advance. In other words, a whitelist must be maintained for tamper detection before providing a service. Therefore, if the normal signature information is not registered in advance, it is determined that the normal application is also a forged application, so there is a problem that the use of the corresponding application is impossible.

[Prior literature number]

Korean Patent Registration No. 10-1566141

On the client side, the signature information for the application and the user's identifier (eg, user ID) are transmitted to the server side, and the server side allows the application operator to decide whether to allow or block application authentication according to the business situation, so that all signatures are pre-written. A method and system for flexibly detecting forgery of a mobile application without registration are provided.

In the forgery detection method performed by a computer device including at least one processor, in response to the execution of the application being attempted in the mobile terminal by the at least one processor, app signature authentication information for the application from the mobile terminal receiving; receiving, by the at least one processor, a selection to allow or block authentication for the app signature authentication information through an operator terminal of the application; storing, by the at least one processor, as allowing or blocking authentication for the app signature authentication information according to the selection; allowing, by the at least one processor, execution of the application in the mobile terminal when the authentication is permitted; And when the authentication is blocked by the at least one processor, it provides a forgery detection method comprising the step of blocking the execution of the application in the mobile terminal.

According to one side, the step of receiving a selection to allow or block the authentication includes a first function for displaying the app signature authentication information and a second function for receiving a selection of allowing or blocking authentication for the app signing authentication information. providing the page; and confirming permission of authentication or blocking of authentication selected through the second function in the provided page.

According to another aspect, the page provides a third function for displaying a list of app signature authentication information for which authentication is permitted and a list of app signing authentication information for which authentication is blocked, and a third function for displaying the app signing authentication information for which authentication is allowed, the app for which authentication is blocked. It may be characterized by further comprising a fourth function for changing the signature authentication information and a fifth function for changing the authentication-blocked app signature authentication information into the authentication-permitted app signature authentication information.

According to another aspect, the step of allowing or blocking the authentication may include: adding the app signing authentication information to a whitelist when it is selected to allow authentication for the app signing authentication information; and when it is selected to block authentication for the app signature authentication information, adding the app signature authentication information to a black list.

According to another aspect, the forgery detection method comprises the steps of: receiving, by the at least one processor, app signature authentication information for the application from the mobile terminal in response to an attempt to re-execute the application in the mobile terminal; allowing, by the at least one processor, to re-execute the application when the app signature authentication information is stored as allowing authentication for the app signature authentication information; and blocking, by the at least one processor, when the app signature authentication information is stored as blocking authentication for the app signature authentication information, blocking re-execution of the application.

According to another aspect, the app signature authentication information may include user information about the user of the mobile terminal and signature information of the application. The app signature authentication information may further include information about a package name of the application and a version of the application as basic information of the application.

According to another aspect, the app signature authentication information further includes terminal information about the mobile terminal, and the terminal information is at least one of an Embedded MultiMedia Card (EMMC) ID, an International Mobile Station Equipment Identity (IMEI), and a MAC address. It may be characterized in that it further comprises. The terminal information may further include information about the package name of the application and the version of the application as basic information of the application.

In the forgery detection method performed by a computer device including at least one processor, in response to an attempt to execute an application installed in the computer device by the at least one processor, app signature authentication information for the application is extracted to do; and transmitting, by the at least one processor, the extracted app signing authentication information to an authentication server, wherein the app signing authentication information includes user information for a user of the computer device and signature information of the application It provides a forgery detection method, characterized in that.

Provided is a computer program stored in a computer-readable recording medium in combination with a computer device to execute the method on the computer device.

There is provided a computer-readable recording medium in which a program for executing the method in a computer device is recorded.

App-signing authentication information for the application from the mobile terminal, comprising at least one processor implemented to execute computer-readable instructions, in response to the at least one processor attempting to execute the application in the mobile terminal Receive, receive a selection to allow or block authentication for the app signature authentication information through the operator terminal of the application, store as allowing or blocking authentication for the app signature authentication information according to the selection, and the authentication When this is permitted, the execution of the application in the mobile terminal is allowed, and when the authentication is blocked, the computer device characterized in that the execution of the application is blocked in the mobile terminal.

at least one processor implemented to execute computer-readable instructions, wherein in response to an attempt to execute an application installed on a computer device by the at least one processor, extracting app signing authentication information for the application, , and transmits the extracted app signature authentication information to an authentication server, wherein the app signature authentication information provides a computer device, characterized in that it includes user information about a user of the computer device and signature information of the application.

On the client side, the signature information for the application and the user's identifier (eg, user ID) are transmitted to the server side, and the server side allows the application operator to decide whether to allow or block application authentication according to the business situation, so that all signatures are pre-written. You can flexibly detect forgery of mobile applications without registration.

1 is a diagram illustrating an example of a network environment according to an embodiment of the present invention.
2 is a block diagram illustrating an example of a computer device according to an embodiment of the present invention.
3 is a diagram illustrating an example of a general appearance of a forgery detection system according to an embodiment of the present invention.
4 is a flowchart illustrating an example of an app authentication permission scenario according to an embodiment of the present invention.
5 is a flowchart illustrating an example of an app authentication blocking scenario according to an embodiment of the present invention.
6 is a flowchart illustrating an example of a scenario for re-allowing an authentication-blocked app according to an embodiment of the present invention.
7 is a diagram illustrating an example of a user interface included in a page for authentication control of an app operator according to an embodiment of the present invention.
8 is a diagram illustrating an example of a method for detecting forgery of a mobile terminal according to an embodiment of the present invention.
9 is a diagram illustrating an example of a forgery detection method of an authentication server according to an embodiment of the present invention.
10 is a flowchart illustrating another example of an app authentication permission scenario according to an embodiment of the present invention.
11 is a flowchart illustrating another example of an app authentication blocking scenario according to an embodiment of the present invention.

Hereinafter, embodiments will be described in detail with reference to the accompanying drawings.

Forgery detection system according to embodiments of the present invention may be implemented by at least one computer device. In this case, the computer program according to an embodiment of the present invention may be installed and driven in the computer device, and the computer device may perform the forgery detection method according to the embodiments of the present invention under the control of the driven computer program. The above-described computer program may be stored in a computer-readable recording medium in combination with a computer device to execute the abnormal forgery detection method in the computer.

1 is a diagram illustrating an example of a network environment according to an embodiment of the present invention. The network environment of FIG. 1 shows an example including a plurality of electronic devices 110 , 120 , 130 , 140 , a plurality of servers 150 , 160 , and a network 170 . 1 is an example for explaining the invention, and the number of electronic devices or the number of servers is not limited as in FIG. 1 . In addition, the network environment of FIG. 1 only describes one example of environments applicable to the present embodiments, and the environment applicable to the present embodiments is not limited to the network environment of FIG. 1 .

The plurality of electronic devices 110 , 120 , 130 , and 140 may be a fixed terminal implemented as a computer device or a mobile terminal. Examples of the plurality of electronic devices 110 , 120 , 130 , 140 include a smartphone, a mobile phone, a navigation device, a computer, a notebook computer, a digital broadcasting terminal, a personal digital assistant (PDA), and a portable multimedia player (PMP). , tablet PCs, etc. As an example, in FIG. 1 , the shape of a smartphone is shown as an example of the electronic device 110 , but in embodiments of the present invention, the electronic device 110 is substantially connected to another electronic device through the network 170 using a wireless or wired communication method. It may refer to one of various physical computer devices capable of communicating with the devices 120 , 130 , 140 and/or the servers 150 and 160 .

The communication method is not limited, and not only a communication method using a communication network (eg, a mobile communication network, a wired Internet, a wireless Internet, a broadcasting network) that the network 170 may include, but also short-range wireless communication between devices may be included. For example, the network 170 may include a Personal Area Network (PAN), a Local Area Network (LAN), a Campus Area Network (CAN), a Metropolitan Area Network (MAN), a Wide Area Network (WAN), and a Broadband Network (BBN). , the Internet, and the like. In addition, the network 170 is a bus (Bus) network, star (Star) network, ring (Ring) network, mesh (Mesh) network, star-bus (Star-Bus) network, tree (Tree) or hierarchical (Hierarchical) ) may include any one or more of a network topology including a network, but is not limited thereto.

Each of the servers 150 and 160 communicates with the plurality of electronic devices 110 , 120 , 130 , 140 and the network 170 through a computer device or a plurality of computers to provide commands, codes, files, content, services, etc. It can be implemented in devices. For example, the server 150 provides a service (eg, an instant messaging service, a game service, a group call service (or voice conference service), messaging service, mail service, social network service, map service, translation service, financial service, payment service, search service, content providing service, etc.).

2 is a block diagram illustrating an example of a computer device according to an embodiment of the present invention. Each of the plurality of electronic devices 110 , 120 , 130 , 140 or the servers 150 and 160 described above may be implemented by the computer device 200 illustrated in FIG. 2 .

As shown in FIG. 2 , the computer device 200 may include a memory 210 , a processor 220 , a communication interface 230 , and an input/output interface 240 . The memory 210 is a computer-readable recording medium and may include a random access memory (RAM), a read only memory (ROM), and a permanent mass storage device such as a disk drive. Here, a non-perishable mass storage medium such as a ROM and a disk drive may be included in the computer device 200 as a separate permanent storage device distinct from the memory 210 . Also, an operating system and at least one program code may be stored in the memory 210 . These software components may be loaded into the memory 210 from a computer-readable recording medium separate from the memory 210 . The separate computer-readable recording medium may include a computer-readable recording medium such as a floppy drive, a disk, a tape, a DVD/CD-ROM drive, and a memory card. In another embodiment, the software components may be loaded into the memory 210 through the communication interface 230 rather than a computer-readable recording medium. For example, the software components may be loaded into the memory 210 of the computer device 200 based on a computer program installed by files received through the network 170 .

The processor 220 may be configured to process instructions of a computer program by performing basic arithmetic, logic, and input/output operations. The instructions may be provided to the processor 220 by the memory 210 or the communication interface 230 . For example, the processor 220 may be configured to execute a received instruction according to a program code stored in a recording device such as the memory 210 .

The communication interface 230 may provide a function for the computer device 200 to communicate with other devices (eg, the storage devices described above) through the network 170 . For example, a request, command, data, file, etc. generated by the processor 220 of the computer device 200 according to a program code stored in a recording device such as the memory 210 is transmitted to the network ( 170) to other devices. Conversely, signals, commands, data, files, etc. from other devices may be received by the computer device 200 through the communication interface 230 of the computer device 200 via the network 170 . A signal, command, or data received through the communication interface 230 may be transferred to the processor 220 or the memory 210 , and the file may be a storage medium (described above) that the computer device 200 may further include. persistent storage).

The input/output interface 240 may be a means for an interface with the input/output device 250 . For example, the input device may include a device such as a microphone, keyboard, or mouse, and the output device may include a device such as a display or a speaker. As another example, the input/output interface 240 may be a means for an interface with a device in which functions for input and output are integrated into one, such as a touch screen. At least one of the input/output devices 250 may include the computer device 200 and one device. For example, like a smart phone, a touch screen, a microphone, a speaker, etc. may be implemented in a form included in the computer device 200 .

Also, in other embodiments, the computer device 200 may include fewer or more components than those of FIG. 2 . However, there is no need to clearly show most of the prior art components. For example, the computer device 200 may be implemented to include at least a portion of the above-described input/output device 250 or may further include other components such as a transceiver and a database.

An “app” described below may mean an application.

3 is a diagram illustrating an example of a general appearance of a forgery detection system according to an embodiment of the present invention. The forgery detection system according to this embodiment may include a plurality of mobile terminals 310 , an authentication server 320 and a plurality of app operator terminals 330 .

Each of the plurality of mobile terminals 310 may be a subject receiving services provided by the app operators by installing and executing a desired app among various apps provided by the plurality of app operators. Each of the plurality of mobile terminals 310 may be implemented by a physical device such as the computer device 200 described with reference to FIG. 2 . After the installed app is executed, each of the plurality of mobile terminals 310 may use the service of the app operator by using a function provided by the app itself or a function provided through a server provided by the app operators. Meanwhile, each of the plurality of mobile terminals 310 may communicate with the authentication server 320 to authenticate the app while the app is running. At this time, when the app is authenticated, the execution of the app may be completed in the corresponding mobile terminal, but when the app is blocked, the execution of the app in the corresponding mobile terminal may be blocked. On the other hand, when each of the plurality of mobile terminals 310 requests authentication of the app, the signature information of the corresponding app and user information (eg, a user identifier such as a user ID) are matched and transmitted to the authentication server 320 . have.

The authentication server 320 may be a subject for authenticating the corresponding app according to the app authentication request from each of the plurality of mobile terminals 310 . Such an authentication server may be implemented by a physical device such as the computer device 200 . The authentication server may be implemented by two or more physical devices. The authentication server 320 may receive a result of authentication permission or authentication blocking for the authentication of the corresponding app through the app operator of the app for which authentication is requested, and may allow or block the execution of the app according to the received result. For example, the authentication server 320 provides the app's signature information and user information delivered from the mobile terminal requesting the app's authentication to the user interface (eg, through the web) provided for the app operator of the app. through the user interface of the page) can be provided to the app operator.

The plurality of app operator terminals 330 may be physical devices operated by app operators, and each of these physical devices corresponds to the computer device 200 described with reference to FIG. 2 or to be implemented as the computer device 200 . can The app operator may access the user interface provided by the authentication server 320 through his/her app operator terminal, and based on the signature information and user information of the app, and through the user interface, authentication for the execution of the app is allowed or You can choose to block authentication.

On the other hand, the authentication server 320 may store whether to allow or block the authentication of the app with respect to the signature of the app. In this case, the authentication server 320 can allow or block authentication without going through the app operator afterwards for the signature of the app whose authentication is allowed or blocked once through the app operator.

As such, the authentication server 320 can continue to generate a whitelist and a blacklist for each user and each signature of the app through the app operator, even if the whitelist for authentication of the app is not provided in advance. These whitelists and blacklists can be shared with the corresponding app operator, so that the app operator can identify users who attempt to forge the app.

4 is a flowchart illustrating an example of an app authentication permission scenario according to an embodiment of the present invention. 4 illustrates a mobile terminal 410 , an authentication server 320 , and an app operator terminal 420 . Here, the mobile terminal 410 may be one of the plurality of mobile terminals 310 described with reference to FIG. 3 , and the app operator terminal 430 may be one of the plurality of app operator terminals 330 described with reference to FIG. 3 . have. Steps 1 ( 431 ) to 7 ( 437 ) to be described later may be performed in connection with a process in which the mobile terminal 410 attempts to execute an app installed in the mobile terminal 410 .

In step 1 431 , the mobile terminal 410 may extract app signature information and user information. The app signature information may be signature information generated for an app installed in the mobile terminal 410 . If the app is forged, the app signature information of the forged app may be different from the app signature information of the original app. In addition, the user information may include a user identifier of the corresponding user on a service provided through the app. According to an embodiment, the user information may further include information of the mobile terminal 310 (at least one of an application package name, an application version, an EMMC ID, an IMEI, and a MAC address) in addition to the user identifier described above.

In step 2 432 , the mobile terminal 410 may transmit the extracted app signature information and user information to the authentication server 320 . For example, the mobile terminal 410 may transmit the app signature information and the user information to the authentication server 320 through the network 170 under the control of the app.

In step 3 (433), the authentication server 320 may expose the app signature information and user information to the app provider. For example, the authentication server 320 may expose app signature information and user information through a user interface of a page accessible to the app provider, and the app operator uses his/her app operator terminal 420 to access the page. By accessing it, it is possible to receive app signature information and user information.

In step 4 (434), the app operator terminal 420 may check user information and app signature information. At this time, the confirmation of the user information and the app signature information may be manually made by the app operator, or the app operator terminal 420 may be automatically made through the operation of comparing the user information and the app signature information according to a preset logic. . For example, the app operator terminal 420 may allow or block authentication of the corresponding app signature information by comparing the app signature information registered for the corresponding app with the app signature information of the app for which authentication is requested. In addition, the app operator terminal 420 may allow or block authentication of the app signature information separately from the app signature information for which authentication is requested for preset users. This embodiment describes a scenario in which authentication of the app signature information is permitted.

In step 5 (435), the app operator terminal 420 may request the authentication server 320 to store the corresponding app signature information to allow authentication. In this case, the authentication server 320 may store the app signature authentication information so that authentication of the corresponding user information and the corresponding app signature information is allowed. Such app signing authentication information may include corresponding user information and corresponding app signature information. In other words, the corresponding user information and the corresponding app signature information may be added to the whitelist of the authentication server 320 .

In step 6 ( 436 ), the authentication server 320 may expose authentication-approved app signature information and user information. As an example, the authentication server 320 may display app signature information, user information, and information indicating that authentication of the corresponding app signature information and user information is permitted through the user interface of the aforementioned page. The app operator may access the page through the app operator terminal 420 to receive the corresponding information. This may mean that the app operator can share the whitelist of the authentication server 320 through the page.

In step 7 (437), the authentication server 320 may allow the execution of the app. For example, the authentication server 320 may allow the execution of the app by allowing authentication of the app signature information and the user information transmitted by the mobile terminal 410 in step 1 ( 431 ).

After that, when the mobile terminal 410 requests authentication of the app with the same user information and app signature information, the authentication server 320 may allow authentication of the requested app signature information by inquiring the previously stored app signature authentication information. Therefore, it is possible to continuously allow the execution of the corresponding app without going through the app operator.

5 is a flowchart illustrating an example of an app authentication blocking scenario according to an embodiment of the present invention. 5 shows the mobile terminal 410, the authentication server 320, and the app operator terminal 420 described with reference to FIG. Steps 1 ( 510 ) to 7 ( 570 ) to be described later may be performed in connection with a process in which the mobile terminal 410 attempts to execute an app installed in the mobile terminal 410 .

In step 1 510 , the mobile terminal 410 may extract app signature information and user information. The app signature information may be signature information generated for an app installed in the mobile terminal 410 . If the app is forged, the app signature information of the forged app may be different from the app signature information of the original app. In addition, the user information may include a user identifier of the corresponding user on a service provided through the app. As described above, according to an embodiment, the user information may further include information (at least one of an EMMC ID, an IMEI, and a MAC address) of the mobile terminal 410 in addition to the above-described user identifier.

In step 2 520 , the mobile terminal 410 may transmit the extracted app signature information and user information to the authentication server 320 . For example, the mobile terminal 410 may transmit the app signature information and the user information to the authentication server 320 through the network 170 under the control of the app.

In step 3 (530), the authentication server 320 may expose the app signature information and user information to the app provider. For example, the authentication server 320 may expose app signature information and user information through a user interface of a page accessible to the app provider, and the app operator uses his/her app operator terminal 420 to access the page. By accessing it, it is possible to receive app signature information and user information.

In step 4 (540), the app operator terminal 420 may check user information and app signature information. At this time, the confirmation of the user information and the app signature information may be manually made by the app operator, or the app operator terminal 420 may be automatically made through the operation of comparing the user information and the app signature information according to a preset logic. . For example, the app operator terminal 420 may allow or block authentication of the corresponding app signature information by comparing the app signature information registered for the corresponding app with the app signature information of the app for which authentication is requested. In addition, the app operator terminal 420 may allow or block authentication of the app signature information separately from the app signature information for which authentication is requested for preset users. This embodiment describes a scenario in which authentication of the app signature information is blocked.

In step 5 (550), the app operator terminal 420 may request the authentication server 320 to store the authentication of the corresponding app signature information to be blocked. In this case, the authentication server 320 may store the app signature authentication information so that authentication of the corresponding user information and the corresponding app signature information is blocked. Such app signing authentication information may include corresponding user information and corresponding app signature information. In other words, the corresponding user information and the corresponding app signature information may be added to the blacklist of the authentication server 320 .

In step 6 (560), the authentication server 320 may expose the authentication-blocked app signature information and user information. As an example, the authentication server 320 may display app signature information, user information, and information indicating that authentication of the corresponding app signature information and user information is blocked through the user interface of the aforementioned page. The app operator may access the page through the app operator terminal 420 to receive the corresponding information. This may mean that the app operator can share the blacklist of the authentication server 320 through the page.

In step 7 (570), the authentication server 320 may block the execution of the app. For example, the authentication server 320 may block the execution of the app by blocking the authentication of the app signature information and the user information transmitted by the mobile terminal 410 in the first process 431 .

After that, when the mobile terminal 410 requests authentication of the app with the same user information and app signature information, the authentication server 320 may block the authentication of the requested app signature information by inquiring the previously stored app signature authentication information, , so it is possible to continuously block the execution of the app without going through the app operator.

In this way, the authentication server 320 allows the execution of the app while building a whitelist and blacklist for each user and for each app signature information through the app operator without having to build a whitelist for the app signature information for the app in advance. can be blocked In addition, after a specific user's app signature information and user information are stored in the whitelist and blacklist once, the user can continuously allow or block the execution of the corresponding app using the built-in whitelist and blacklist. .

6 is a flowchart illustrating an example of a scenario for re-allowing an authentication-blocked app according to an embodiment of the present invention. 6 shows the mobile terminal 410, the authentication server 320, and the app operator terminal 420 described with reference to FIGS. 4 and 5 . Steps 1 (610) to 4 (640) to be described later may be performed in connection with the previous app execution process, and steps 5 (650) to 8 (680) are performed by the mobile terminal 410 and the mobile terminal 410. ) can be performed in conjunction with the process of currently trying to run the installed app.

In a first process 610 , the authentication server 320 may expose app signature information and user information to an app provider. For example, the authentication server 320 may expose app signature information and user information through a user interface of a page accessible to the app provider, and the app operator uses his/her app operator terminal 420 to access the page. By accessing it, it is possible to receive app signature information and user information. In other words, the app provider can access the above-mentioned page at any time to check user information and app signature information related to their app. In addition, as already described, the app operator can check whether authentication is allowed or blocked for the app signature information and user information through the corresponding page, and if necessary, by blocking the permission of authentication or allowing the blocking of authentication can be changed to

In the second process 620 , the app operator terminal 420 may check user information and app signature information. At this time, the confirmation of the user information and the app signature information may be manually made by the app operator, or the app operator terminal 420 may be automatically made through the operation of comparing the user information and the app signature information according to a preset logic. . For example, the app operator terminal 420 may allow or block authentication of the corresponding app signature information by comparing the app signature information registered for the corresponding app with the app signature information of the app for which authentication is requested. In addition, the app operator terminal 420 may allow or block authentication of the app signature information separately from the app signature information for which authentication is requested for preset users. In this embodiment, a scenario is described in which the app operator changes the authentication of the blocked app signature information to allow through the app operator terminal 420 . To this end, the above-mentioned page may include a user interface for selecting one of permitting and blocking authentication for specific app signature information and user information.

In step 3 (630), the app operator terminal 420 may request to store the authentication server 320 to allow authentication of the corresponding app signature information. For example, when the app operator changes the authentication for the blocked app signature information to allow using the user interface of the above-described page, the above-described request may be transmitted to the authentication server 320 . The authentication server 320 may store the app signature authentication information so that authentication of the corresponding user information and the corresponding app signature information is allowed. In other words, user information and app signature information added to the blacklist of the authentication server 320 may be moved to the whitelist.

In step 4 (640), the authentication server 320 may expose authentication-approved app signature information and user information. As an example, the authentication server 320 may display app signature information, user information, and information indicating that authentication of the corresponding app signature information and user information is permitted through the user interface of the aforementioned page. The app operator may access the page through the app operator terminal 420 to receive the corresponding information.

Thereafter, when the mobile terminal 410 wants to run the corresponding app, the mobile terminal 410 may extract the app signature information and the user information in step 5 (650) according to the control of the app, and in step 6 (660). ) may transmit the extracted app signature information and user information to the authentication server 320 . In this case, the authentication server 320 may inquire the app signing authentication information for the app signing information and the user information transmitted in step 7 (670), and the user information and the app signing information are stored so that authentication is allowed. Therefore, in step 8 (680), it is possible to allow the execution of the app in the mobile terminal (410).

Conversely, it will be easy to understand from the above description that the authentication of blocked app signature information can be changed to allow again.

7 is a diagram illustrating an example of a user interface included in a page for authentication control of an app operator according to an embodiment of the present invention. 7 shows an allow table 710 including app signature authentication information for which authentication is permitted as a white list and a block table 720 including app signature authentication information for which authentication is blocked as a blacklist as a blacklist. For example, the first row of the permissions table 710 is the user identifier "AAA", the app name "A", the package name "cba", the permission time "2020-01-22 11:02:33", and the signature "AFAEAGRADSF" ", status "allowed", and the like. As a more specific example, while the user corresponding to the user identifier "AAA" requests authentication at the time of execution of the app corresponding to the app name "A" and the package name "cba", the user identifier "AAA" and the app signature information as user information The signature "AFEAAGRADSF" may be passed to the authentication server 320 . In this case, the authentication server 320 may expose user information and app signature information to the app operator, and the app operator checks the user information and the app signature information to allow authentication for the user information and the app signature information. It may request the authentication server 320 to store it. In this case, the corresponding app signature authentication information may be stored as the first row of the whitelist, the permission table 710 .

In this case, the user interfaces 711 for changing the authentication for each app signature authentication information from allow to block may be provided in the permission table 710 . Similarly, the blocking table 720 may be provided with user interfaces 721 for changing the authentication for each app signature authentication information from blocking to allowed. If the app signature authentication information corresponding to the user identifier "AAA" is changed from allow to block, the app signature authentication information corresponding to the user identifier "AAA" is deleted from the allow table 710 and block table 720 can be added to

8 is a diagram illustrating an example of a method for detecting forgery of a mobile terminal according to an embodiment of the present invention. The forgery detection method according to the present embodiment may be performed by the computer device 200 implementing the mobile terminal. In this case, the processor 220 of the computer device 200 may be implemented to execute a control command according to a code of an operating system included in the memory 210 or a code of at least one computer program. Here, the processor 220 causes the computer device 200 to perform the steps 810 and 820 included in the method of FIG. 8 according to a control command provided by the code stored in the computer device 200 . can control

In step 810 , the computer device 200 may extract app signature authentication information for the application in response to an attempt to execute the application installed in the computer device 200 . In this case, the app signature authentication information may include user information about the user of the computer device 200 and signature information of the application. The app signing authentication information may further include information about the package name of the application and the version of the application as basic information of the application.

According to an embodiment, the app signature authentication information may further include terminal information about the computer device 200 . As an example, the terminal information may include at least one of an EMMC ID, an IMEI, and a MAC address. The terminal information may further include information about the package name of the application and the version of the application as basic information of the application.

In step 820 , the computer device 200 may transmit the extracted app signature authentication information to the authentication server. Here, the authentication server may correspond to the authentication server 320 described above. In the transmitted app signing authentication information, whether to allow or block authentication may be determined as the authentication server is selected to allow or block authentication for the app signature authentication information through the operator terminal of the application. In this case, when the authentication for the app signature authentication information is allowed, the execution of the application may be allowed, and when the authentication for the app signature authentication information is blocked, the execution of the application may be blocked.

As such, as the app signature authentication information includes user information, it is possible to obtain information about a user who uses the forged app, rather than simply detecting forgery and falsification of the app.

9 is a diagram illustrating an example of a forgery detection method of an authentication server according to an embodiment of the present invention. The forgery detection method according to the present embodiment may be performed by the computer device 200 implementing the authentication server 320 . In this case, the processor 220 of the computer device 200 may be implemented to execute a control command according to a code of an operating system included in the memory 210 or a code of at least one computer program. Here, the processor 220 causes the computer device 200 to perform steps 910 and 980 included in the method of FIG. 9 according to a control command provided by a code stored in the computer device 200 . can control

In step 910 , the computer device 200 may receive app signature authentication information for the application from the mobile terminal in response to an attempt to execute the application in the mobile terminal. Here, the received app signature authentication information may correspond to the app signature authentication information transmitted in step 820 of FIG. 8 . In other words, it may include user information about the user of the mobile terminal and signature information of the application. In this case, the app signature authentication information may further include information about the package name of the application and the version of the application as basic information of the application. As already described, as the user information is transmitted together, it is possible to obtain information about the user who uses the forged app, rather than simply detecting the forgery of the app.

In step 920, the computer device 200 may receive a selection to allow or block authentication for the app signature authentication information through the operator terminal of the application. For example, the computer device 200 may provide a page including a first function for displaying the app signing authentication information and a second function for receiving a selection of allowing or blocking authentication for the app signing authentication information. In this case, the operator of the application can access the page through the operator terminal and select to allow or block authentication for the app signature authentication information. In this case, the computer device 200 may check the permission of the selected authentication or the blocking of the authentication through the second function in the provided page. In addition, the page is a third function that displays a list of app signing authentication information for which authentication is allowed and a list of app signing authentication information for which authentication is blocked, and the app signing authentication information for which authentication is allowed as the app signature authentication information for which authentication is blocked. It may further include a fourth function for changing and a fifth function for changing the authentication-blocked app signing authentication information to the authentication-permitted app signing authentication information. In this case, the operator of the application may block authentication again if necessary even if authentication has been previously allowed, and may allow authentication again if necessary even if authentication is blocked. In addition, since it is possible to review cases in which authentication is allowed and cases in which authentication is blocked for each user and for each app signature information, the operator of the application is responsible for the signature of the application generated by the computer device 200 as the authentication server 320 . It will be possible to share the whitelist and blacklist for

In operation 930, the computer device 200 may be stored as allowing or blocking authentication for the app signature authentication information according to selection. In this case, a list of app signature authentication information stored as allowing authentication may be a white list, and a list of app signing authentication information stored as blocking authentication may be a black list. To this end, the computer device 200 may add the app signature authentication information to the whitelist when it is selected to allow authentication for the app signature authentication information. Also, when the computer device 200 is selected to block authentication for the app signing authentication information, the computer device 200 may add the app signing authentication information to the blacklist.

In operation 940 , the computer device 200 may allow execution of an application in the mobile terminal when authentication is permitted.

In step 950 , the computer device 200 may block execution of the application in the mobile terminal when authentication is blocked.

In other words, the computer device 200 as the authentication server 320 can process authentication for the requested app signing authentication information through the operator of the application even in a situation in which a separate whitelist or blacklist is not prepared in advance, You can create a whitelist and a blacklist at the same time.

In operation 960 , the computer device 200 may receive app signature authentication information for the application from the mobile terminal in response to an attempt to re-execute the application in the mobile terminal. In other words, the computer device 200 may receive the app signature authentication information whenever an application is executed in the mobile terminal.

In step 970 , the computer device 200 may allow re-execution of the application when the app signing authentication information is stored as allowing authentication for the app signing authentication information. As described above, if it has already been stored as allowing authentication for the app signature authentication information delivered when the application is first executed in the mobile terminal, the computer device 200 does not need to go through the operator of the application, pre-stored information (white information in the list) can be used to allow re-execution of the application in the mobile terminal.

In step 980 , the computer device 200 may block re-execution of the application when the app signing authentication information is stored as blocking authentication for the app signing authentication information. As described above, if it has already been stored as blocking authentication for the app signature authentication information transmitted when the application is first executed in the mobile terminal, the computer device 200 does not need to go through the operator of the application, pre-stored information (black) information in the list) can be used to block re-execution of the application in the mobile terminal.

10 is a flowchart illustrating another example of an app authentication permission scenario according to an embodiment of the present invention. Processes 1001 to 1012 of FIG. 10 may be performed in connection with a process in which the mobile terminal 410 attempts to execute an app installed in the mobile terminal 410 . At this time, it is assumed that the authentication server 320 is installed in the mobile terminal 410 and stored so as to block the app signature authentication for a specific app that the mobile terminal 410 wants to run. Storing to block the app signing authentication may correspond to recording the app signing authentication information including the app signing authentication information, the app information, and the user information in relation to the specific app in the blacklist of the authentication server 320 .

In step 1 ( 1001 ), the mobile terminal 410 may extract app signature information, app information, and user information. As already described, the app signature information may be signature information generated for an app installed in the mobile terminal 410 . If the app is forged, the app signature information of the forged app may be different from the app signature information of the original app. In addition, the app information may include information on the package name of the app and the version of the app as basic information of the app, and the user information may include a user identifier of the corresponding user on a service provided through the app.

In step 2 1002 , the mobile terminal 410 may transmit the extracted app signature information, app information, and user information to the authentication server 320 . For example, the mobile terminal 410 may transmit the app signature information, the app information, and the user information to the authentication server 320 through the network 170 under the control of the app.

In step 3 ( 1003 ), the authentication server 320 may inquire the app signature authentication information. As described above, in this embodiment, the authentication server 320 stores information to allow app signature authentication for a specific app installed in the mobile terminal 410 . For example, the authentication server 320 may inquire whether to allow or block the execution of the app corresponding to the received app information and user information through the blacklist and/or whitelist, and in this embodiment, the authentication The server 320 may extract information to block the app signature authentication for the specific app through the blacklist.

In step 4 ( 1004 ), the authentication server 320 may block app execution. Here, the blocked app is a specific app installed in the mobile terminal 410 and may be an app corresponding to the app information and user information transmitted by the mobile terminal 410 . If additional processes (particularly steps 5 ( 1005 ) to 7 ( 1007 )) to be described later are not performed, authentication of the app signature information for the execution of the corresponding app may be continuously blocked.

In step 5 ( 1005 ), the authentication server 320 may expose app signature information, app information, and user information to the app operator terminal 420 . For example, the authentication server 320 may expose app signature information, app information, and user information through a user interface of a page accessible to the app provider, and the app operator uses his/her app operator terminal 420 to By accessing the page, you can receive app signature information, app information and user information.

In step 6 ( 1006 ), the app operator terminal 420 may check app signature information, app information, and user information. At this time, the verification of the app signature information, the app information and the user information may be manually made by the app operator, and the app operator terminal 420 compares the app signature information, the app information and the user information according to a preset logic. It can also be done automatically. For example, the app operator terminal 420 may allow or block authentication of the corresponding app signature information by comparing the app signature information registered for the corresponding app with the app signature information of the app for which authentication is requested. In addition, the app operator terminal 420 may allow or block authentication of the app signature information separately from the app signature information for which authentication is requested for preset users. This embodiment describes a scenario in which authentication of blocked app signature information is allowed again.

In step 7 (1007), the app operator terminal 420 may request the authentication server 320 to store the corresponding app signature information to allow authentication. In this case, the authentication server 320 may store the app signature authentication information in the whitelist so that authentication of the corresponding app signature information, the app information, and the user information is allowed. Such app signing authentication information may include corresponding app signing information, app information, and user information. In other words, the corresponding app signature information, app information, and user information recorded in the blacklist of the authentication server 320 may be moved to and recorded in the whitelist.

In step 8 (1008), the authentication server 320 may expose authentication-approved app signature information, app information, and user information. As an example, the authentication server 320 may display app signature information, app information, user information, and information indicating that authentication for the corresponding app signature information is permitted through the user interface of the above-described page. The app operator may access the page through the app operator terminal 420 to receive the corresponding information. This may mean that the app operator can share the whitelist of the authentication server 320 through the page.

Thereafter, as the authentication of the app signature information for the specific app of the mobile terminal 410 is permitted, the execution of the specific app may be permitted. Processes 9 ( 1009 ) to 12 ( 1012 ) represent processes in which the execution of the app is permitted. The mobile terminal 410 may extract the app signature information, the app information and the user information in step 9 ( 1009 ), and use the app signature information, the app information and the user information extracted in the step 10 ( 1010 ) to the authentication server 320 . can be sent to In step 11 (1011), the authentication server 320 may inquire the app signature authentication information. Since the authentication server 320 has stored the corresponding app signature information, app information and user information in the whitelist according to the request from the app operator terminal 420 in process 7 1007, the authentication server in process 12 1012 320 may allow execution of the corresponding app.

11 is a flowchart illustrating another example of an app authentication blocking scenario according to an embodiment of the present invention. Processes 1101 to 1112 of FIG. 11 may be performed in connection with a process in which the mobile terminal 410 attempts to execute an app installed in the mobile terminal 410 . At this time, it is assumed that the authentication server 320 is installed in the mobile terminal 410 and stored so as to allow app signature authentication for a specific app to be executed by the mobile terminal 410 . Storing to allow the app signing authentication may correspond to recording the app signing authentication information including the app signing authentication information, the app information, and the user information in relation to the specific app in the whitelist of the authentication server 320 .

In step 1 ( 1101 ), the mobile terminal 410 may extract app signature information, app information, and user information. As already described, the app signature information may be signature information generated for an app installed in the mobile terminal 410 . If the app is forged, the app signature information of the forged app may be different from the app signature information of the original app. In addition, the app information may include information on the package name of the app and the version of the app as basic information of the app, and the user information may include a user identifier of the corresponding user on a service provided through the app.

In step 2 1102 , the mobile terminal 410 may transmit the extracted app signature information, app information, and user information to the authentication server 320 . For example, the mobile terminal 410 may transmit the app signature information, the app information, and the user information to the authentication server 320 through the network 170 under the control of the app.

In step 3 (1103), the authentication server 320 may inquire the app signature authentication information. As described above, in this embodiment, the authentication server 320 stores information to allow app signature authentication for a specific app installed in the mobile terminal 410 . For example, the authentication server 320 may inquire whether to allow or block the execution of the app corresponding to the received app information and user information through the blacklist and/or whitelist, and in this embodiment, the authentication The server 320 may extract information to allow app signature authentication for the specific app through the whitelist.

In step 4 (1104), the authentication server 320 may block the execution of the app. Here, the permitted app is a specific app installed in the mobile terminal 410 and may be an app corresponding to the app information and user information transmitted by the mobile terminal 410 . If additional processes (particularly steps 5 ( 1105 ) to 7 ( 1107 )) to be described later are not performed, authentication of the app signature information for the execution of the corresponding app may be continuously permitted.

In step 5 ( 1105 ), the authentication server 320 may expose app signature information, app information, and user information to the app operator terminal 420 . For example, the authentication server 320 may expose app signature information, app information, and user information through a user interface of a page accessible to the app provider, and the app operator uses his/her app operator terminal 420 to By accessing the page, you can receive app signature information, app information and user information.

In step 6 (1106), the app operator terminal 420 may check the app signature information, the app information, and the user information. At this time, the verification of the app signature information, the app information and the user information may be manually made by the app operator, and the app operator terminal 420 compares the app signature information, the app information and the user information according to a preset logic. It can also be done automatically. For example, the app operator terminal 420 may allow or block authentication of the corresponding app signature information by comparing the app signature information registered for the corresponding app with the app signature information of the app for which authentication is requested. In addition, the app operator terminal 420 may allow or block authentication of the app signature information separately from the app signature information for which authentication is requested for preset users. This embodiment describes a scenario in which authentication of permitted app signature information is blocked again.

In step 7 (1107), the app operator terminal 420 may request to store the authentication server 320 to block the authentication of the corresponding app signature information. In this case, the authentication server 320 may store the app signature authentication information in the blacklist so that authentication of the corresponding app signature information, the app information, and the user information is blocked. Such app signing authentication information may include corresponding app signing information, app information, and user information. In other words, the corresponding app signature information, app information, and user information recorded in the whitelist of the authentication server 320 may be moved to and recorded in the blacklist.

In step 8 (1108), the authentication server 320 may expose the authentication-blocked app signature information, app information, and user information. As an example, the authentication server 320 may display app signature information, app information, user information, and information indicating that authentication for the corresponding app signature information is blocked through the user interface of the above-described page. The app operator may access the page through the app operator terminal 420 to receive the corresponding information. This may mean that the app operator can share the blacklist of the authentication server 320 through the page.

Thereafter, as the authentication of the app signature information for the specific app of the mobile terminal 410 is blocked, the execution of the specific app may be blocked. Steps 9 ( 1109 ) to 12 ( 1112 ) represent a process in which the execution of the app is blocked. The mobile terminal 410 may extract the app signature information, the app information and the user information in step 9 (1109), and use the app signature information, the app information and the user information extracted in the step 10 (1110) to the authentication server 320 can be sent to In step 11 ( 1111 ), the authentication server 320 may inquire the app signature authentication information. Since the authentication server 320 has stored the corresponding app signature information, app information and user information in the blacklist according to the request from the app operator terminal 420 in process 7 ( 1107 ), the authentication server in process 12 ( 1112 ) 320 may block the execution of the corresponding app.

As such, according to embodiments of the present invention, the client side transmits the signature information for the application and the user's identifier (eg, user ID) to the server side, and the server side allows or allows application authentication on the application operator side according to the business situation. By deciding to block, it is possible to flexibly detect forgery of mobile applications without registering all signatures in advance.

The system or apparatus described above may be implemented as a hardware component or a combination of a hardware component and a software component. For example, the devices and components described in the embodiments include, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), It may be implemented using one or more general purpose or special purpose computers, such as a Programmable Logic Unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and one or more software apps running on the operating system. A processing device may also access, store, manipulate, process, and generate data in response to execution of the software. For convenience of understanding, there is also an example in which one processing device is used, but those of ordinary skill in the art will recognize that the processing device includes a plurality of processing elements and/or a plurality of types of processing elements. It can be seen that including For example, the processing device may include a plurality of processors or one processor and one controller. Other Processing Configurations are also possible, such as a Parallel Processor.

The software may include a computer program, code, instructions, or a combination of one or more thereof, which configures the processing device to operate as desired or independently or collectively instructs the processing device to operate as desired. can do. The software and/or data may be stored in any type of machine, component, physical device, virtual equipment, computer storage medium or device to be interpreted in or provide instructions or data to the processing device. You can embody it. The software may be distributed over networked computer systems, and stored or executed in a distributed manner. Software and data may be stored in one or more computer-readable recording media.

The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, etc. alone or in combination. The medium may continuously store a computer executable program, or may be a temporary storage for execution or download. Also, the medium may be various recording means or storage means in the form of a single or a combination of several hardware. Examples of the medium include a hard disk, a magnetic medium such as a floppy disk and a magnetic tape, an optical recording medium such as CD-ROM and DVD, a magneto-optical medium such as a floppy disk, and those configured to store program instructions, including ROM, RAM, flash memory, and the like. In addition, examples of other media include an app store that distributes applications or a recording medium managed by a site or server that supplies or distributes other various software. Examples of program instructions include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like.

As described above, although the embodiments have been described with reference to the limited embodiments and drawings, various modifications and variations are possible for those skilled in the art from the above description. For example, the described techniques are performed in an order different from the described method, and/or the described components of the system, structure, apparatus, circuit, etc. are combined or combined in a different form than the described method, or other components Or substituted or substituted by equivalents may achieve an appropriate result.

Therefore, other implementations, other embodiments, and equivalents to the claims are also within the scope of the following claims.

Claims (17)

In the forgery detection method performed by a computer device comprising at least one processor,
receiving, by the at least one processor, app signature authentication information for the application from the mobile terminal in response to the execution of the application being attempted in a mobile terminal different from the computer device;
receiving, by the at least one processor, a selection to allow or block authentication for the app signature authentication information through an operator terminal of the application;
storing, by the at least one processor, as allowing or blocking authentication for the app signature authentication information according to the selection;
allowing, by the at least one processor, execution of the application in the mobile terminal when the authentication is permitted; and
Blocking, by the at least one processor, execution of the application in the mobile terminal when the authentication is blocked
including,
The operator terminal is a forgery detection method, characterized in that it comprises a terminal of the operator of the service provided through the application. According to claim 1,
The step of receiving a selection to allow or block the authentication is,
providing a page including a first function for displaying the app signature authentication information and a second function for receiving a selection of allowing or blocking authentication for the app signature authentication information; and
Confirming permission of authentication or blocking of authentication selected through the second function on the provided page
Forgery detection method comprising a. 3. The method of claim 2,
The page changes the third function to display a list of app signature authentication information for which authentication is allowed and a list of app signature authentication information for which authentication is blocked, and the app signature authentication information for which authentication is allowed to change to the app signature authentication information for which authentication is blocked Forgery detection method, characterized in that it further comprises a fourth function and a fifth function for changing the authentication-blocked app signature authentication information to the authentication-permitted app signature authentication information. According to claim 1,
The step of saving as allowing or blocking the authentication is,
adding the app signature authentication information to a whitelist when it is selected to allow authentication for the app signature authentication information; and
If it is selected to block authentication for the app signing authentication information, adding the app signing authentication information to a blacklist
Forgery detection method comprising a. According to claim 1,
receiving, by the at least one processor, app signature authentication information for the application from the mobile terminal in response to an attempt to re-execute the application in the mobile terminal;
allowing, by the at least one processor, to re-execute the application when the app signature authentication information is stored as allowing authentication for the app signature authentication information; and
If, by the at least one processor, the app signature authentication information is stored as blocking authentication for the app signature authentication information, blocking the re-execution of the application;
Forgery detection method further comprising a. According to claim 1,
The app signature authentication information is a forgery detection method, characterized in that it comprises user information for the user of the mobile terminal and the signature information of the application. 7. The method of claim 6,
The app signature authentication information is a forgery detection method, characterized in that it further comprises a package name of the application and the version of the application as basic information of the application. 7. The method of claim 6,
The app signature authentication information further includes terminal information for the mobile terminal,
The terminal information forgery detection method, characterized in that it includes at least one of an Embedded MultiMedia Card (EMMC) ID, an International Mobile Station Equipment Identity (IMEI), and a MAC address. In the forgery detection method performed by a computer device comprising at least one processor,
extracting, by the at least one processor, app signature authentication information for the application in response to an attempt to execute the application installed in the computer device; and
Transmitting, by the at least one processor, the extracted app signature authentication information to an authentication server
including,
The app signature authentication information includes user information about a user of the computer device and signature information of the application,
In the transmitted app signature authentication information, whether to allow or block authentication is determined as the authentication server receives a selection to allow or block authentication for the app signature authentication information through the operator terminal of the application,
The operator's terminal forgery detection method, characterized in that it comprises a terminal of the operator of the service provided through the application. 10. The method of claim 9,
In the transmitted app signature authentication information, whether to allow or block authentication is determined as the authentication server receives a selection to allow or block authentication for the app signature authentication information through the operator terminal of the application,
If the authentication for the app signing authentication information is allowed, the execution of the application is allowed,
When the authentication for the app signature authentication information is blocked, the execution of the application is blocked
Forgery detection method, characterized in that. A computer program stored in a computer-readable recording medium in combination with a computer device to cause the computer device to execute the method of any one of claims 1 to 10. A computer-readable recording medium in which a computer program for executing the method of any one of claims 1 to 10 in a computer device is recorded. A computer device comprising:
at least one processor implemented to execute computer-readable instructions
including,
by the at least one processor;
In response to an attempt to execute an application in a mobile terminal different from the computer device, receiving app signature authentication information for the application from the mobile terminal,
Acceptance or blocking of authentication for the app signature authentication information is selected through the operator terminal of the application,
Save as allowing or blocking authentication for the app signing authentication information according to the selection,
When the authentication is permitted, the execution of the application in the mobile terminal is allowed,
When the authentication is blocked, the execution of the application in the mobile terminal is blocked,
The operator terminal is to include the terminal of the operator of the service provided through the application
A computer device comprising a. 14. The method of claim 13,
by the at least one processor;
To provide a page including a first function for displaying the app signing authentication information and a second function for receiving a selection of allowing or blocking authentication for the app signing authentication information,
Confirming the permission or blocking of authentication selected through the second function on the provided page
A computer device comprising a. 14. The method of claim 13,
by the at least one processor;
If it is selected to allow authentication for the app signing authentication information, add the app signing authentication information to a whitelist;
If it is selected to block authentication for the app signing authentication information, adding the app signing authentication information to the blacklist
A computer device comprising a. 14. The method of claim 13,
by the at least one processor;
In response to the re-execution of the application is attempted in the mobile terminal, receiving the app signature authentication information for the application from the mobile terminal,
If the app signing authentication information is stored as allowing authentication for the app signing authentication information, allowing re-running of the application;
When the app signing authentication information is stored as blocking authentication for the app signing authentication information, blocking the re-execution of the application
A computer device comprising a. 14. The method of claim 13,
The app signature authentication information includes user information for a user of the mobile terminal and signature information of the application
A computer device comprising a.

Images