Browser privacy input tool construction method
By creating an extension in the browser, listening to tag switching events and obtaining password-related information, and combining MutationObserver class to monitor input content, the browser solves the insufficient security and user experience problems when processing sensitive information, and realizes effective protection of passwords and the risk of leakage.
Patent Information
- Application Number
- CN202411969936.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-30
- Publication Date
- 2025-04-25
AI Technical Summary
Existing browsers lack effective protection mechanisms when processing sensitive information, and are prone to threats from malware, phishing and data leakage, and have poor user experience, difficult to remember strong passwords, and unstable automatic filling function.
By creating a new browser extension, listen to the switching events of the browser tag, obtain the user's local password modification date and the domain name disclosure date, obtain the leaked password event record from the local library, and monitor the input tool content through the MutationObserver class, to achieve the security of the LeakagePrevention browser to control the input domain.
Effectively prevent the browser from automatically filling passwords, prompting users for risk of password leakage, and detecting and preventing exposure when others tamper with the current input content, protecting the security of users' passwords.
Smart Images
Figure CN119885151A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of Internet browsers, and in particular to a method for constructing a browser privacy input tool. Background Art
[0002] With the popularization of the Internet, the frequency of users entering sensitive information in browsers has increased significantly, such as passwords, credit card information, etc., especially in today's digital age, password protection has become the cornerstone of user account and personal data security. However, many existing browsers lack effective protection mechanisms when handling such sensitive information, and are vulnerable to threats such as malware, phishing and data leakage. Password leakage may lead to serious consequences such as account theft, data loss, identity fraud, etc. Therefore, a new tool is needed to enhance the privacy input security of users in browsers.
[0003] 1. Browser plug-in: Prevent the browser from automatically filling in passwords through browser plug-ins, but this method may affect the user experience and cannot prevent passwords from being modified through other methods.
[0004] 2. Password manager: Using a password manager can automatically fill in passwords, but this method may lead to the risk of password leakage and cannot prevent passwords from being modified by other methods.
[0005] 3. Local library comparison: Store the leaked password event records in the local library and compare them with the account information entered by the user. However, this method requires manual updating of the local library and cannot prevent password modification through other methods.
[0006] 4. One-Time Password (OTP): A one-time password is usually generated through SMS, email or dedicated hardware. Each time you log in, you need to enter a new OTP, which is valid for a short time and can only be used once.
[0007] Disadvantages of existing technology:
[0008] Insufficient security: In some cases, users may accidentally allow others to see their passwords; Susceptibility to keyloggers: Malware can record the passwords entered by users;
[0009] User experience issues: The requirement for strong passwords may make it difficult for users to remember and increase the chance of input errors; sometimes the auto-fill function does not work properly, causing users to enter passwords manually
[0010] Lack of flexibility: Many input boxes only support single password verification, which cannot effectively deal with security threats; some websites do not support seamless integration with password managers;
[0011] Inconvenient to use: A new dynamic password needs to be obtained each time, which increases the complexity of user operations. Summary of the invention
[0012] In view of the above problems, the present invention is proposed to provide a method for constructing a browser privacy input tool that overcomes the above problems or at least partially solves the above problems.
[0013] According to one aspect of the present invention, a method for constructing a browser privacy input tool is provided, the method comprising:
[0014] Create a new browser extension;
[0015] In the extension, listen for browser tab switching events;
[0016] Get the user's local password modification date;
[0017] Get the domain name public disclosure date;
[0018] Get the leaked password event record from the local repository.
[0019] Optionally, the monitoring of the browser tab switching event specifically includes:
[0020] When a new tab is loaded, the protectInputType function is called to monitor the input tool content through the MutationObserver class to implement the security of the LeakagePrevention browser control input field.
[0021] Optionally, in the protectInputType function, all input tags of type password are traversed; and a change event listener is added to each input tag.
[0022] Optionally, adding a change event listener to each input tag specifically includes:
[0023] When the input tag's type changes, check if the new type is password, and if not, change it to password.
[0024] Optionally, the step of obtaining the domain name disclosure date also includes:
[0025] Compare the user's local password modification date with the domain name public disclosure date;
[0026] If the user's local password modification date is earlier than the domain name public disclosure date, a warning prompt is displayed.
[0027] Optionally, after obtaining the leaked password event record from the local library, the step further includes:
[0028] Get the account information entered by the user;
[0029] Compare the account information entered by the user with the leakage event records in the local library;
[0030] If the account information entered by the user matches the leakage event record in the local library, a warning prompt is displayed.
[0031] The invention provides a method for constructing a browser privacy input tool, which includes: creating a new browser extension; in the extension, monitoring the switching event of the browser tab; obtaining the modification date of the user's local password; obtaining the date of the domain name's public leakage; and obtaining the leaked password event record from the local library. The method effectively prevents the browser from automatically filling in passwords and prompts the user of the risk of password leakage. When others tamper with the current input content, LeakagePrevention will detect it truthfully and make modifications to prevent exposure to others, thereby protecting the user's password security.
[0032] 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
[0033] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative work.
[0034] Figure 1 A flowchart of a method for constructing a browser privacy input tool provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0035] The exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.
[0036] The terms "comprises" and "having" and any variations thereof in the description embodiments, claims and drawings of the present invention are intended to cover non-exclusive inclusions, for example, including a series of steps or units.
[0037] The technical solution of the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments.
[0038] like Figure 1 As shown, a method for constructing a browser privacy input tool of the present invention includes:
[0039] Create a new browser extension;
[0040] In the extension, listen for browser tab switching events;
[0041] When a new tab is loaded, the protectInputType function is called to monitor the input tool content through the MutationObserver class to implement the security of the LeakagePrevention browser control input field;
[0042] In the protectInputType function, iterate over all input tags of type password;
[0043] Add a change event listener to each input tag;
[0044] When the input tag's type changes, check if the new type is password, and if not, change it to password;
[0045] Get the user's local password modification date;
[0046] Get the domain name public disclosure date;
[0047] Compare the user's local password modification date with the domain name public disclosure date;
[0048] If the user's local password modification date is earlier than the domain name public disclosure date, a warning prompt will be displayed;
[0049] Get the leaked password event records from the local repository;
[0050] Get the account information entered by the user;
[0051] Compare the account information entered by the user with the leakage event records in the local library;
[0052] If the account information entered by the user matches the leakage event record in the local library, a warning prompt is displayed.
[0053] Beneficial effects: The method and system of the present invention effectively prevent the browser from automatically filling in passwords and prompt users of the risk of password leakage. In addition, when others tamper with the current input content, LeakagePrevention will detect it truthfully and make modifications to prevent exposure to others, thereby protecting the user's password security.
[0054] The above specific implementation methods further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above are only specific implementation methods of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.
Claims
1. A method for constructing a browser privacy input tool, characterized in that: The construction method comprises: Create a new browser extension; In the extension, listen for browser tab switching events; Get the user's local password modification date; Get the date of public disclosure of the domain name; Get the leaked password event record from the local repository.
2. A method for constructing a browser privacy input tool according to claim 1, characterized in that: The monitoring of the browser tab switching event specifically includes: When a new tab is loaded, the protectInputType function is called to monitor the input tool content through the MutationObserver class to implement the security of the LeakagePrevention browser control input field.
3. A method for constructing a browser privacy input tool according to claim 1, characterized in that: In the protectInputType function, all input tags of type password are traversed; Add a change event listener to each input tag.
4. A method for constructing a browser privacy input tool according to claim 3, characterized in that: Adding a change event listener to each input tag specifically includes: When the input tag's type changes, check if the new type is password, and if not, change it to password.
5. A method for constructing a browser privacy input tool according to claim 1, characterized in that: The acquisition of the domain name after the public disclosure date also includes: Compare the user's local password modification date with the domain name public disclosure date; If the user's local password modification date is earlier than the domain name public disclosure date, a warning prompt is displayed.
6. A method for constructing a browser privacy input tool according to claim 1, characterized in that: After obtaining the leaked password event record from the local library, the method further includes: Get the account information entered by the user; Compare the account information entered by the user with the leakage event records in the local library; If the account information entered by the user matches the leakage event record in the local library, a warning prompt is displayed.