Data security method and device for fingerprint browser, equipment and medium

Abstract

The invention provides a data security method and device for a fingerprint browser, equipment and a medium. The method comprises the following steps: setting a security rule configurator in the fingerprint browser; a plug-in in the fingerprint browser requests to read cookies corresponding to a domain name in the configured domain name list; if the id of the plug-in does not exist, the fingerprint browser is directly released; if the id of the plug-in exists, the fingerprint browser compares the id of the plug-in according to a plug-in white list in the security rule configurator; if the comparison is passed, releasing is carried out; if the comparison is not passed, carrying out interception; when a plug-in in the fingerprint browser requests to read the cookies corresponding to the domain names outside the configured domain name list, the cookies are directly released, so that data of a fingerprint browser user based on a chromium kernel can be protected from being stolen by a third-party plug-in; and the data of the fingerprint browser cannot be used in other browsers.

Description

Technical Field

[0001] The present invention relates to the technical field of browser user data security, and in particular to a method, device, equipment and medium for data security of a fingerprint browser. Background Art

[0002] Existing browsers include fingerprint browsers, and the current fingerprint browsers are implemented based on the chromium kernel. However, this type of fingerprint browser does not have any security control over the plug-in's chrome.cookies API. The plug-in has very large permissions to cookies. As long as the cookies are declared in the manifest file, the plug-in can obtain cookies from all websites, and permissions cannot be set according to the website. A public encryption method is used to protect cookie data. Public encryption methods are easily cracked, and this data can be copied to other browsers and used directly. There is no protection for the plug-in's storage data, and this data can be copied to other browsers and used directly.

[0003] Therefore, when users use the fingerprint browser implemented on the basis of the Chromium kernel, they may install some external third-party plug-ins; and some bad plug-ins will secretly upload the cookies and storage in the user's fingerprint browser to their own server, thus causing security problems for the user's account. Summary of the invention

[0004] The technical problem to be solved by the present invention is to provide a method, device, equipment and medium for data security of fingerprint browsers, which can protect the data of users of fingerprint browsers based on the Chromium kernel from being stolen by third-party plug-ins; and ensure that the data of the fingerprint browser of the present invention cannot be used in other browsers.

[0005] In a first aspect, the present invention provides a method for data security of a fingerprint browser, comprising the following steps:

[0006] Step 1: Set a security rule configurator in the fingerprint browser, wherein the security rule configurator is provided with a configuration domain name list and a plug-in whitelist;

[0007] Step 2: A plug-in in the fingerprint browser requests to read the cookie corresponding to a domain name in the configured domain name list; if the plug-in ID does not exist, the fingerprint browser directly releases it; if the plug-in ID exists, the fingerprint browser compares the plug-in ID with the plug-in whitelist in the security rule configurator; if the comparison passes, it is released; if not, it is intercepted;

[0008] If a plug-in in the fingerprint browser requests to read the cookie corresponding to a domain name outside the configured domain name list, it will be allowed directly.

[0009] In a second aspect, the present invention provides a device for data security of a fingerprint browser, comprising the following modules:

[0010] A setting module is used to set a security rule configurator in the fingerprint browser, wherein the security rule configurator is provided with a configuration domain name list and a plug-in whitelist;

[0011] Verification module: A plug-in in the fingerprint browser requests to read the cookie corresponding to a domain name in the configured domain name list; if the plug-in ID does not exist, the fingerprint browser directly releases it; if the plug-in ID exists, the fingerprint browser compares the plug-in ID with the plug-in whitelist in the security rule configurator; if the comparison passes, it is released; if the comparison fails, it is intercepted;

[0012] If a plug-in in the fingerprint browser requests to read the cookie corresponding to a domain name outside the configured domain name list, it will be allowed directly.

[0013] In a third aspect, the present invention provides an electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method described in the first aspect when executing the program.

[0014] In a fourth aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in the first aspect.

[0015] One or more technical solutions provided by the present invention have at least the following technical effects or advantages:

[0016] The present invention can protect the cookies of users of fingerprint browsers based on the Chromium kernel from being stolen by third-party plug-ins; and the cookies and storage of the fingerprint browsers use their own unique encryption, which cannot be cracked, thereby making the data unusable in other browsers; through the two encryption methods of the present invention, the fingerprint browser of the present invention has its own data format and is compatible with the data formats of various other browsers.

[0017] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The present invention will be further described below in conjunction with embodiments with reference to the accompanying drawings.

[0019] Figure 1 is a flow chart of the method in Embodiment 1 of the present invention;

[0020] Figure 2 It is a schematic diagram of the structure of the device in the second embodiment of the present invention. DETAILED DESCRIPTION

[0021] The embodiments of the present application solve the security problem of user data of fingerprint browsers based on the Chromium kernel by providing a method, apparatus, device and medium for data security of fingerprint browsers.

[0022] The technical solution in the embodiment of the present application has the following general idea:

[0023] Propose a method similar to the control plugin chrome.cookie api, providing the following functions:

[0024] Supports configuring whitelist of plugins; supports configuring domain names of cookies to be protected;

[0025] All APIs of chrome.cookies are wrapped with a layer of security controller.

[0026] Security Rules Configurator:

[0027] Technical means:

[0028] The back-end data is stored in MySQL; the front-end uses web pages to configure security rules.

[0029] Enter the domain name to be protected on the web page, separate multiple domains with , and enter the plug-in ID to be included in the whitelist;

[0030] The saved data structure is as follows:

[0031] "extension_control":{

[0032] / / Whitelist extension ids

[0033] "extension_white_list":["pkgccpejnmalmdinmhkkfafefagiiiad"],

[0034] "cookies":{

[0035] / / Cookies protected domain name list

[0036] "domain_protected_list":["www.amazon.com",".amazon.com"]

[0037] }

[0038] }

[0039] For example, if we configure www.amazon.com as the domain name to be protected, then plugins that are not in the whitelist will not be able to read the cookies under Amazon.

[0040] Security Rules Controller:

[0041] First, inject security rule verification into the following three Chrome cookie APIs before Chromium generates the corresponding functions. (chrome.cookies.get, chrome.cookies.set, chrome.cookies.remove); storage is different from cookies; cookies can be obtained across plugins, which brings security issues; storage cannot be obtained across plugins, but storage can copy files and use them directly in other Chrome-type browsers.

[0042] Find the code for generating these three APIs in Chromium in the extension_function_dispatcher.cc file.

[0043] Inject security controls into the code that generates these three functions.

[0044] If the plugin ID does not exist, it indicates that the code is not initiated by the plugin, and it will be released directly.

[0045] If the plugin id has a value and is in the whitelist, it will be allowed to pass directly.

[0046] If the plugin id has a value and is not in the whitelist, the three APIs chrome.cookies.get, chrome.cookies.set, and chrome.cookies.remove operate as follows:

[0047] If the API wants to obtain the cookie of a protected domain name, the API will be intercepted and an exception will be returned;

[0048] Otherwise, release directly.

[0049] When the running API is chrome.cookies.getAll, the injection security rule filtering is performed in the callback function of the API, as follows:

[0050] If the plugin ID does not exist, it indicates that the code is not initiated by the plugin, and it is released directly;

[0051] If the plugin id has a value and is in the whitelist, it will be allowed directly;

[0052] If the plugin id has a value and is not in the whitelist, you need to remove the cookies under the protected domain name from all the cookies obtained;

[0053] The code settings are as follows:

[0054] 1.chrome.cookies.get,chrome.cookies.set,chrome.cookies.remove

[0055] Add the following settings to the ExtensionFunctionDispatcher::CreateExtensionFunction function:

[0056] If the extension object exists and extension.id is not in extension_white_list,

[0057] Then params.name == "cookies.get" & ¶ms.arguments.url.host is in domain_black_list && extension.id != params.arguments.url.host, and finally returns an error of no permission.

[0058] if extension does not exist || extension.id == params.arguments.url.host;

[0059] Then just release it and return normally.

[0060] If the extension object exists and extension.id is in extension_white_list;

[0061] Then just let it go.

[0062] 2.chrome.cookies.getAll

[0063] Add the following settings to the CookiesGetAllFunction::GetAllCookiesCallback function:

[0064] If the extension object does not exist, it is allowed to pass directly and returns normally.

[0065] If the extension object exists and extension.id exists in extension_white_list,

[0066] Then just release it and return normally.

[0067] If extension.is does not exist in extension_white_list, you need to filter the cookies whose domain in the cookie_list value is in domain_black_list, and finally return the filtered cookies.

[0068] By storing and encrypting cookies, specific data is encrypted and cannot be cracked; regular data is encrypted so that other browsers can also use it, as follows:

[0069] Chromium stores cookies in Sqllite

[0070] Create a class MyCookieCryptoDelegate that inherits net::CookieCryptoDelegate.

[0071] Overload the EncryptString and DecryptString encryption and decryption methods.

[0072] The general steps to implement in the overloaded method body are:

[0073] When setting cookies, use the fingerprint browser's own (non-public) encryption algorithm to encrypt and write to sqllite

[0074] When reading cookies, first try to decrypt them using Chromium's own decryption function. If successful, they are released directly.

[0075] If Chromium's own decryption fails, use a non-public decryption algorithm to decrypt. If successful, it will be released directly, otherwise an error will be reported.

[0076] By storing and encrypting storage, specific data is encrypted and cannot be cracked; regular data is encrypted so that other browsers can also use it, as follows:

[0077] Chromium stores storage in Leveldb

[0078] In the API set up by Leveldb, we use our own non-public encryption algorithm to encrypt and write to Leveldb.

[0079] In the API read by Leveldb, first use the decryption function provided by Chromium to try to decrypt it. If successful, it will be released directly.

[0080] If the built-in public algorithm fails to decrypt, a non-public decryption algorithm is used for decryption. If successful, it is released directly, otherwise an error is reported.

[0081] Embodiment 1

[0082] like Figure 1 As shown, this embodiment provides a method for data security of a fingerprint browser, comprising the following steps:

[0083] Step 1: Set a security rule configurator in the fingerprint browser, wherein the security rule configurator is provided with a configuration domain name list and a plug-in whitelist;

[0084] Step 2: A plug-in in the fingerprint browser requests to read the cookie corresponding to a domain name in the configured domain name list; if the plug-in ID does not exist, the fingerprint browser directly releases it; if the plug-in ID exists, the fingerprint browser compares the plug-in ID with the plug-in whitelist in the security rule configurator; if the comparison passes, it is released; if not, it is intercepted;

[0085] If a plug-in in the fingerprint browser requests to read the cookie corresponding to a domain name outside the configured domain name list, it will be allowed directly.

[0086] In this embodiment, preferably, it also includes step 3. When the fingerprint browser sets the cookie, the cookie corresponding to the domain name in the configured domain name list in the security rule configurator is encrypted using the first encryption algorithm and written into sqllite; the cookies corresponding to other domain names are encrypted using the encryption algorithm provided by Chromium, and then written into sqllite; when reading the cookie, first use the decryption provided by Chromium to try to decrypt it, if successful, it is directly released; if the decryption provided by Chromium fails, the decryption algorithm corresponding to the first encryption algorithm is used for decryption, if successful, it is directly released, otherwise an error is reported.

[0087] This embodiment preferably also includes step 4, the fingerprint browser stores the storage in Leveldb; the storage corresponding to the domain name in the configured domain name list in the security rule configurator is encrypted using the second encryption algorithm and written into Leveldb; the storage corresponding to other domain names is encrypted using the encryption algorithm provided by Chromium, and then written into Leveldb; when reading the storage, first use the decryption provided by Chromium to try to decrypt, if successful, directly release; if the decryption provided by Chromium fails, use the decryption algorithm corresponding to the second encryption algorithm to decrypt, if successful, directly release, otherwise an error is reported.

[0088] In this embodiment, preferably, step 2 is specifically:

[0089] When a plug-in in the fingerprint browser reads the cookie corresponding to a domain name in the configured domain name list through the API chrome.cookies.get, chrome.cookies.set or chrome.cookies.remove, if the plug-in id does not exist, the fingerprint browser will directly release it; if the plug-in id exists, the fingerprint browser will compare the plug-in id with the plug-in whitelist in the security rule configurator; if the comparison passes, it will be released; if not, it will be blocked;

[0090] When a plug-in in the fingerprint browser reads cookies through the API chrome.cookies.getAll, if the plug-in id does not exist, the fingerprint browser will directly release it; if the plug-in id exists, the fingerprint browser will compare the plug-in id with the plug-in whitelist in the security rule configurator; if the comparison is successful, it will be released; if the comparison is not successful, the cookie corresponding to the domain name in the configured domain name list in the cookie will be cleared and then released;

[0091] If a plug-in in the fingerprint browser requests to read the cookie corresponding to a domain name outside the configured domain name list, it will be allowed directly.

[0092] Based on the same inventive concept, the present application also provides a device corresponding to the method in Example 1, see Example 2 for details.

[0093] Embodiment 2

[0094] like Figure 2 As shown, in this embodiment, a device for data security of a fingerprint browser is provided, including the following modules:

[0095] A setting module is used to set a security rule configurator in the fingerprint browser, wherein the security rule configurator is provided with a configuration domain name list and a plug-in whitelist;

[0096] Verification module: A plug-in in the fingerprint browser requests to read the cookie corresponding to a domain name in the configured domain name list; if the plug-in ID does not exist, the fingerprint browser directly releases it; if the plug-in ID exists, the fingerprint browser compares the plug-in ID with the plug-in whitelist in the security rule configurator; if the comparison passes, it is released; if the comparison fails, it is intercepted;

[0097] If a plug-in in the fingerprint browser requests to read the cookie corresponding to a domain name outside the configured domain name list, it will be allowed directly.

[0098] In this embodiment, preferably, a cookie storage module is also included. When the fingerprint browser sets cookies, the cookies corresponding to the domain names in the configured domain name list in the security rule configurator are encrypted using the first encryption algorithm and written into sqllite; the cookies corresponding to other domain names are encrypted using the encryption algorithm provided by Chromium, and then written into sqllite; when reading cookies, first use the decryption provided by Chromium to try to decrypt, if successful, directly release; if the decryption provided by Chromium fails, use the decryption algorithm corresponding to the first encryption algorithm to decrypt, if successful, directly release, otherwise an error is reported.

[0099] In this embodiment, preferably, it also includes a storage module, and the fingerprint browser stores the storage in Leveldb; the storage corresponding to the domain name in the configured domain name list in the security rule configurator is encrypted using the second encryption algorithm and written into Leveldb; the storage corresponding to other domain names is encrypted using the encryption algorithm provided by Chromium, and then written into Leveldb; when reading the storage, first use the decryption provided by Chromium to try to decrypt, if successful, it is directly released; if the decryption provided by Chromium fails, the decryption algorithm corresponding to the second encryption algorithm is used for decryption, if successful, it is directly released, otherwise an error is reported.

[0100] In this embodiment, preferably, the verification module is specifically:

[0101] When a plug-in in the fingerprint browser reads the cookie corresponding to a domain name in the configured domain name list through the API chrome.cookies.get, chrome.cookies.set or chrome.cookies.remove, if the plug-in id does not exist, the fingerprint browser will directly release it; if the plug-in id exists, the fingerprint browser will compare the plug-in id with the plug-in whitelist in the security rule configurator; if the comparison passes, it will be released; if not, it will be blocked;

[0102] When a plug-in in the fingerprint browser reads cookies through the API chrome.cookies.getAll, if the plug-in id does not exist, the fingerprint browser will directly release it; if the plug-in id exists, the fingerprint browser will compare the plug-in id with the plug-in whitelist in the security rule configurator; if the comparison is successful, it will be released; if the comparison is not successful, the cookie corresponding to the domain name in the configured domain name list in the cookie will be cleared and then released;

[0103] If a plug-in in the fingerprint browser requests to read the cookie corresponding to a domain name outside the configured domain name list, it will be allowed directly.

[0104] Since the device introduced in the second embodiment of the present invention is a device used to implement the method of the first embodiment of the present invention, those skilled in the art can understand the specific structure and deformation of the device based on the method introduced in the first embodiment of the present invention, so it is not described here in detail. All devices used in the method of the first embodiment of the present invention belong to the scope of protection of the present invention.

[0105] Based on the same inventive concept, the present application provides an electronic device embodiment corresponding to the first embodiment, see the third embodiment for details.

[0106] Embodiment 3

[0107] This embodiment provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, any implementation method in the first embodiment can be implemented.

[0108] Since the electronic device introduced in this embodiment is a device used to implement the method in the first embodiment of the present application, based on the method introduced in the first embodiment of the present application, a person skilled in the art can understand the specific implementation of the electronic device of the present embodiment and its various variations, so how the electronic device implements the method in the embodiment of the present application is not described in detail here. As long as a person skilled in the art implements the device used by the method in the embodiment of the present application, it belongs to the scope of protection of the present application.

[0109] Based on the same inventive concept, the present application provides a storage medium corresponding to the first embodiment, see the fourth embodiment for details.

[0110] Embodiment 4

[0111] This embodiment provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, any implementation method in the first embodiment can be implemented.

[0112] The technical solution provided in the embodiments of the present application has at least the following technical effects or advantages:

[0113] The embodiment of the present application can protect the cookies of users of fingerprint browsers based on the Chromium kernel from being stolen by third-party plug-ins, wherein the protected storage files are encrypted in a unique way, so that even if a third party copies the files, they cannot use them;

[0114] The cookies and storage of the fingerprint browser in the embodiment of the present application use their own unique encryption, which cannot be cracked, thereby making the data unusable in other browsers;

[0115] Through the encryption method of the present invention, the fingerprint browser of the present invention has its own data format and is compatible with the data formats of other various browsers.

[0116] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0117] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0118] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0119] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0120] Although the specific implementation modes of the present invention are described above, those skilled in the art should understand that the specific implementation modes described are only illustrative and are not intended to limit the scope of the present invention. Equivalent modifications and changes made by those skilled in the art in accordance with the spirit of the present invention should be included in the scope of protection of the claims of the present invention.

Claims

1. A method for data security of a fingerprint browser, characterized in that: The steps include: Step 1: Set a security rule configurator in the fingerprint browser, wherein the security rule configurator is provided with a configuration domain name list and a plug-in whitelist; Step 2: A plug-in in the fingerprint browser requests to read the cookie corresponding to a domain name in the configured domain name list; if the plug-in ID does not exist, the fingerprint browser directly releases it; if the plug-in ID exists, the fingerprint browser compares the plug-in ID with the plug-in whitelist in the security rule configurator; If the comparison is passed, it will be released; if it is not passed, it will be intercepted; If a plug-in in the fingerprint browser requests to read the cookie corresponding to a domain name outside the configured domain name list, it will be allowed directly.

2. A method for data security of a fingerprint browser according to claim 1, characterized in that: It also includes step 3. When the fingerprint browser sets a cookie, the cookie corresponding to the domain name in the configured domain name list in the security rule configurator is encrypted using the first encryption algorithm and written into sqllite; the cookies corresponding to other domain names are encrypted using the encryption algorithm provided by Chromium and then written into sqllite; when reading the cookie, first use the decryption provided by Chromium to try to decrypt it. If successful, it is released directly; if the decryption provided by Chromium fails, the decryption algorithm corresponding to the first encryption algorithm is used for decryption. If successful, it is released directly, otherwise an error is reported.

3. A method for data security of a fingerprint browser according to claim 1, characterized in that: It also includes step 4, the fingerprint browser stores the storage in Leveldb; The storage corresponding to the domain name in the configured domain name list in the security rule configurator is encrypted using the second encryption algorithm and written into Leveldb; The storage corresponding to other domain names is encrypted using Chromium's built-in encryption algorithm and then written to Leveldb. When reading the storage, first use Chromium's built-in decryption algorithm to try to decrypt it. If successful, it is released directly. If Chromium's built-in decryption fails, use the decryption algorithm corresponding to the second encryption algorithm to decrypt it. If successful, it is released directly, otherwise an error is reported.

4. The method for data security of a fingerprint browser according to claim 1, characterized in that: The step 2 is specifically as follows: When a plug-in in the fingerprint browser reads the cookie corresponding to a domain name in the configured domain name list through the API chrome.cookies.get, chrome.cookies.set or chrome.cookies.remove, if the plug-in id does not exist, the fingerprint browser will directly release it; if the plug-in id exists, the fingerprint browser will compare the plug-in id with the plug-in whitelist in the security rule configurator; if the comparison passes, it will be released; if not, it will be blocked; When a plug-in in the fingerprint browser reads cookies through the API chrome.cookies.getAll, if the plug-in id does not exist, the fingerprint browser will directly release it; if the plug-in id exists, the fingerprint browser will compare the plug-in id with the plug-in whitelist in the security rule configurator; if the comparison is successful, it will be released; if the comparison is not successful, the cookie corresponding to the domain name in the configured domain name list in the cookie will be cleared and then released; If a plug-in in the fingerprint browser requests to read the cookie corresponding to a domain name outside the configured domain name list, it will be allowed directly.

5. A device for data security of fingerprint browser, characterized in that: Includes the following modules: A setting module is used to set a security rule configurator in the fingerprint browser, wherein the security rule configurator is provided with a configuration domain name list and a plug-in whitelist; Verification module: A plug-in in the fingerprint browser requests to read the cookie corresponding to a domain name in the configured domain name list; if the plug-in ID does not exist, the fingerprint browser directly releases it; if the plug-in ID exists, the fingerprint browser compares the plug-in ID with the plug-in whitelist in the security rule configurator; If the comparison is passed, it will be released; if it is not passed, it will be intercepted; If a plug-in in the fingerprint browser requests to read the cookie corresponding to a domain name outside the configured domain name list, it will be allowed directly.

6. The device for data security of a fingerprint browser according to claim 5, characterized in that: It also includes a cookie storage module. When the fingerprint browser sets cookies, the cookies corresponding to the domain names in the configured domain name list in the security rule configurator are encrypted using the first encryption algorithm and written into sqllite; the cookies corresponding to other domain names are encrypted using the encryption algorithm provided by Chromium and then written into sqllite; when reading cookies, first use the decryption provided by Chromium to try to decrypt, if successful, it is directly released; if the decryption provided by Chromium fails, the decryption algorithm corresponding to the first encryption algorithm is used for decryption, if successful, it is directly released, otherwise an error is reported.

7. The device for data security of a fingerprint browser according to claim 5, characterized in that: It also includes a storage module, and the fingerprint browser stores the storage in Leveldb; The storage corresponding to the domain name in the configured domain name list in the security rule configurator is encrypted using the second encryption algorithm and written into Leveldb; The storage corresponding to other domain names is encrypted using Chromium's built-in encryption algorithm and then written to Leveldb. When reading the storage, first use Chromium's built-in decryption algorithm to try to decrypt it. If successful, it is released directly. If Chromium's built-in decryption fails, use the decryption algorithm corresponding to the second encryption algorithm to decrypt it. If successful, it is released directly, otherwise an error is reported.

8. The device for data security of a fingerprint browser according to claim 5, characterized in that: The verification module is specifically: When a plug-in in the fingerprint browser reads the cookie corresponding to a domain name in the configured domain name list through the API chrome.cookies.get, chrome.cookies.set or chrome.cookies.remove, if the plug-in id does not exist, the fingerprint browser will directly release it; if the plug-in id exists, the fingerprint browser will compare the plug-in id with the plug-in whitelist in the security rule configurator; if the comparison passes, it will be released; if not, it will be blocked; When a plug-in in the fingerprint browser reads cookies through the API chrome.cookies.getAll, if the plug-in id does not exist, the fingerprint browser will directly release it; if the plug-in id exists, the fingerprint browser will compare the plug-in id with the plug-in whitelist in the security rule configurator; if the comparison is successful, it will be released; if the comparison is not successful, the cookie corresponding to the domain name in the configured domain name list in the cookie will be cleared and then released; If a plug-in in the fingerprint browser requests to read the cookie corresponding to a domain name outside the configured domain name list, it will be allowed directly.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the method according to any one of claims 1 to 4 is implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 4 is implemented.

Images