A method and system for customizing development of a browser-side email communication plug-in
By adding the static URL and functional files of the target email address to the browser plugin, parsing the email logic, and replacing DOM elements, the problems of multi-email compatibility and encryption/decryption complexity are solved, thus achieving ease of use and scalability of the browser-side email communication plugin.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- YANGZHOU ZHONGKE NETWORK INFORMATION TECH CO LTD
- Filing Date
- 2023-11-01
- Publication Date
- 2026-06-16
AI Technical Summary
Existing email security protocols and plugins suffer from problems such as inability to adapt to multiple email accounts, complex encryption and decryption operations, and poor user-friendliness.
Customized development of browser-side email communication plugins is achieved by adding the static URL of the target email address and customized functional files to the browser plugin, parsing the email sending and receiving logic, replacing static DOM elements, obtaining and displaying keywords of user privacy information.
It achieves ease of use and scalability across different email vendors, reduces development and maintenance costs, and improves system adaptability, scalability, and user experience.
Smart Images
Figure CN117407624B_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of cyberspace security technology, and specifically relates to a method and system for customizing browser-based email communication plugins. Background Technology
[0002] With the rapid development of internet information security technology and the gradual improvement of users' security awareness, more and more users have realized the importance of personal privacy information security, resulting in an increasing proportion of people with a need for personal privacy information protection. Among privacy information, users' email information accounts for a large proportion, and information exchange in various business scenarios in daily life mainly involves email. In order to effectively protect users' email privacy information security, the academic community has proposed a variety of security protocols, such as the Public Key Protocol (PGP) and the Secure Multipurpose Internet Mail Extensions (S / MIME) to solve email security problems. However, these protocols and methods are mainly based on the PKI public key infrastructure system, which has the problems of being difficult to deploy and maintain and having high development costs.
[0003] To address this issue, Chinese patent application "Email Encryption / Decryption Method, System, Device and Computer-Readable Storage Medium" (application number: CN202210337476.9) proposes a lightweight system that protects users' email information in the form of a client plugin. Compared to the traditional method of changing the protocol, this improves usability to some extent. However, it still has the problem that it can only provide security protection for the Outlook client. On the one hand, users need to download and install the Outlook client before they can use the product. On the other hand, if users use multiple email accounts at the same time, the client plugin will not be able to meet the user's need for confidentiality of email information in multiple email accounts.
[0004] In addition, the Chinese patent application "Method and Apparatus for Sending and Receiving Emails" (application number: CN201911385870.4) discloses a method of signing the original email text and time by calling the private key in the USBKEY through a browser plugin, encrypting the email content using the public and private keys generated by the email client, and then sending the signature and encrypted email content to the recipient to ensure encrypted transmission of the email content. However, this device still requires the user to manually perform the encryption and decryption operations on the email content, which is very complicated to use and has poor user-friendliness. Summary of the Invention
[0005] To address the technical problems existing in the prior art, this invention provides a method and system for customizing browser-based email communication plugins, in order to solve the problem that existing client plugins cannot meet users' confidentiality needs for email information in multiple mailboxes, and that existing encryption and decryption operations for email content are complex and have poor user-friendliness.
[0006] To achieve the above objectives, the technical solution adopted by the present invention is as follows:
[0007] This invention provides a method for customizing browser-based email communication plugins, including:
[0008] Add the static URL of the target email address to the browser plugin development folder;
[0009] In the browser plugin development folder, add the customized functional files for the target email address;
[0010] By customizing the content of predefined static elements, the static DOM element content of the target email's compose interface is replaced.
[0011] Obtain the keywords of the email sending logic and the keywords of the user's personal privacy information involved in the email content, and present the keywords of the user's personal privacy information involved in the email content as parameters;
[0012] Retrieve the email receiving logic and the corresponding valid email information, and present it in code form.
[0013] Retrieve the DOM elements corresponding to the logical layout of any received email in the target email inbox folder, as well as the DOM elements corresponding to the plaintext information of the received email. Then, replace the sub-tag information content of the DOM elements corresponding to the plaintext information of the received email or perform customized reproduction of the DOM elements corresponding to the logical layout of the received email.
[0014] Retrieve the receiving logic of sent emails and the corresponding valid email information, and present it in code form;
[0015] Retrieve the DOM elements corresponding to the logical layout of any sent email in the sent folder of the target email address, as well as the DOM elements corresponding to the plaintext information of the sent email. Then, replace the sub-tag information content of the DOM elements corresponding to the plaintext information of the sent email, or customize and reproduce the DOM elements corresponding to the logical layout of the sent email.
[0016] Furthermore, the process of adding the target email's static URL to the browser plugin development folder is as follows:
[0017] Log in to the target email address and record its static URL; the target email address is a web-based email address accessible through a browser.
[0018] Add the static URL of the target email address to the `matches` keyword in the `content_scripts` module of the manifest file under the browser plugin development files.
[0019] Furthermore, the process of adding the target email's customized functional files to the browser plugin development folder is as follows:
[0020] Add the plugin functionality that customizes the web interface of the target email address to the `js` keyword in the `content_scripts` module of the `manifest` file under the browser plugin development files.
[0021] Furthermore, the process of replacing the static DOM element content of the target email's compose interface using predefined static element customization is as follows:
[0022] Open the target email's compose interface and record the static DOM element content of the target email's compose interface; the static DOM element content of the target email's compose interface includes the send button in the email sending interface, the link to add images to the email body, and the link to upload email attachments;
[0023] Replace the text of the send button in the email sending interface with "encrypted send";
[0024] Replace adding image links in the email body with adding encrypted image links in a custom format;
[0025] Replace the email attachment upload link with a custom encrypted attachment link.
[0026] Furthermore, the process of obtaining keywords for email sending logic and keywords related to user personal privacy information in the email content, and presenting these keywords as parameters, is as follows:
[0027] Open the target email's compose interface and add all user privacy information elements within the target email's compose interface;
[0028] Click the send button on the target email's sending interface, and at the same time use a data packet capture tool to capture the effective data packet information of the email at different stages of the email sending process;
[0029] The effective data packets of the email at different stages of the email sending process are screened and filtered to obtain keywords of the email sending logic and keywords of user personal privacy information involved in the email content.
[0030] Keywords related to user personal privacy information in the sent email content are presented as parameters.
[0031] Furthermore, the process of obtaining the email receiving logic and the corresponding valid email information, and presenting it in code, is as follows:
[0032] Open the target email inbox folder and locate the unread emails within it.
[0033] Click on unread emails in the inbox and use a data packet capture tool to capture valid data packets at different stages of the email retrieval process.
[0034] The valid data packet information at different stages of the email retrieval process is filtered and sorted to obtain the email receiving logic and the valid email information corresponding to the email receiving logic, and presented in code form.
[0035] Furthermore, the process involves retrieving the DOM elements corresponding to the logical layout of any received email within the target email's inbox folder, as well as the DOM elements corresponding to the plaintext information of the received email. The process then involves replacing the sub-tag information of the DOM elements corresponding to the plaintext information of the received email or customizing the DOM elements corresponding to the logical layout of the received email. The details are as follows:
[0036] Open any received email in the target email inbox folder and record the DOM elements corresponding to the logical layout of the received emails and the DOM elements corresponding to the plaintext information of the received emails.
[0037] When parsing emails, if it is possible to replace the content of the DOM element corresponding to the plaintext information of the received email, then the content of the child tag information of the DOM element corresponding to the plaintext information of the received email will be replaced; otherwise, the DOM element corresponding to the logical layout of the received email will be customized and reproduced.
[0038] Furthermore, the process of obtaining the receiving logic for sent emails and the corresponding valid email information, and presenting it in code form, is as follows:
[0039] Open the sent email folder in the target email address, and click on any sent email in the sent email folder interface. At the same time, use a data packet capture tool to capture the effective data packet information of the email at different stages of the sent email display process.
[0040] The valid data packet information at different stages of the sent email display process is filtered and sorted to obtain the receiving logic of the sent email display process and the valid email information corresponding to the receiving logic of the sent email, and presented in code form.
[0041] Furthermore, the process involves obtaining the DOM elements corresponding to the logical layout of any sent email within the target email's sent folder, as well as the DOM elements corresponding to the plaintext information of the sent email. The process also includes replacing the sub-tag information of the DOM elements corresponding to the plaintext information of the sent email or customizing the DOM elements corresponding to the logical layout of the sent email. The details are as follows:
[0042] Open any sent email in the sent folder of the target email address, and record the DOM elements corresponding to the logical layout of the sent email and the DOM elements corresponding to the plaintext information of the sent email.
[0043] When parsing emails, if it is possible to replace the content of the DOM element corresponding to the plaintext information of the sent email, then the content of the child tag information of the DOM element corresponding to the plaintext information of the sent email will be replaced; otherwise, the DOM element corresponding to the logical layout of the sent email will be customized and reproduced.
[0044] This invention also provides a browser-based email communication plugin customization development system, comprising:
[0045] The browser plugin working address and functional customization unit are used to add the static URL of the target email address to the browser plugin development folder; and to add the customized functional files of the target email address to the browser plugin development folder.
[0046] The browser plugin encryption module's customization unit is used to replace the static DOM element content of the target email's composing interface with pre-determined static element customization content; obtain the keywords of the email sending logic and the keywords of the user's personal privacy information involved in the sent email content, and present the keywords of the user's personal privacy information involved in the sent email content in the form of parameters;
[0047] The browser plugin decryption module's customization unit is used to obtain the receiving logic of retrieved emails and the corresponding valid email information, and present it in code form; obtain the DOM elements corresponding to the logical layout of retrieved emails and the DOM elements corresponding to the plaintext information of retrieved emails in any retrieved email in the target email's inbox folder, and replace the sub-tag information content of the DOM elements corresponding to the plaintext information of retrieved emails or perform customized reproduction of the DOM elements corresponding to the logical layout of retrieved emails; obtain the receiving logic of sent emails and the corresponding valid email information, and present it in code form; obtain the DOM elements corresponding to the logical layout of sent emails and the DOM elements corresponding to the plaintext information of sent emails in any sent email in the target email's sent folder, and replace the sub-tag information content of the DOM elements corresponding to the plaintext information of sent emails or perform customized reproduction of the DOM elements corresponding to the logical layout of sent emails.
[0048] Compared with the prior art, the beneficial effects of the present invention are as follows:
[0049] This invention provides a method and system for customizing browser-based email communication plugins. By analyzing the static interfaces and email sending and receiving logic of different email vendors, the working address and functionality of the browser plugin, as well as its encryption and decryption modules, can be customized. Developers only need to implement the core encryption / decryption process and login process suite once for reuse in different forms, enabling out-of-the-box functionality and improving system scalability and maintainability. Furthermore, users are completely unaware of the system's operation; from the user's perspective, usability and user-friendliness are consistent with the initial web-based email version before system installation, without adding any extra burden. This simplifies compatibility issues with different email vendors, significantly reducing development and maintenance costs, and greatly enhancing future compatibility and scalability for different email vendors. Attached Figure Description
[0050] Figure 1 This is a flowchart illustrating the browser-side email communication plugin customization development method described in the embodiment;
[0051] Figure 2 This is a flowchart illustrating the browser plugin's working address and the customization process for its functionality in this embodiment.
[0052] Figure 3 This is a flowchart illustrating the customization process of the browser encryption module in this embodiment;
[0053] Figure 4This is a flowchart of the customization process of the browser decryption module in the embodiment. Detailed Implementation
[0054] To make the technical problems solved by the present invention, the technical solutions, and the beneficial effects clearer, the following specific embodiments provide a further detailed description of the present invention. It should be understood that the specific embodiments described herein are merely illustrative and are not intended to limit the scope of the invention.
[0055] This invention provides a method for customizing browser-based email communication plugins, comprising the following steps:
[0056] Step 1: In the browser plugin development folder, add the static URL of the target email address; specifically, log in to the target email address and record its static URL; the target email address is the web version of the email address in the browser; add the static URL of the target email address to the `matches` keyword of the `content_scripts` module in the manifest file under the browser plugin development folder.
[0057] Step 2: In the browser plugin development folder, add the customized functional files for the target email address; specifically, add the plugin functionality for customizing the web interface of the target email address to the js keyword in the content_scripts module of the manifest file under the browser plugin development folder.
[0058] Step 3: Replace the static DOM element content of the target email's compose interface using predefined static element customization; this specifically includes the following steps:
[0059] Open the target email's compose interface and record the static DOM element content of the target email's compose interface; the static DOM element content of the target email's compose interface includes the send button in the email sending interface, the link to add images to the email body, and the link to upload email attachments;
[0060] Replace the text of the send button in the email sending interface with "encrypted send";
[0061] Replace adding image links in the email body with adding encrypted image links in a custom format;
[0062] Replace the email attachment upload link with a custom encrypted attachment link.
[0063] Step 4: Obtain keywords for the email sending logic and keywords related to user privacy information in the email content, and present these keywords as parameters; specifically, this includes the following steps:
[0064] Open the target email's compose interface and add all user privacy information elements within the target email's compose interface;
[0065] Click the send button on the target email's sending interface, and at the same time use a data packet capture tool to capture the effective data packet information of the email at different stages of the email sending process;
[0066] The effective data packets of the email at different stages of the email sending process are screened and filtered to obtain keywords of the email sending logic and keywords of user personal privacy information involved in the email content.
[0067] Keywords related to user personal privacy information in the sent email content are presented as parameters.
[0068] Step 5: Obtain the email receiving logic and the corresponding valid email information, and present it in code form; specifically, this includes the following steps:
[0069] Open the target email inbox folder and locate the unread emails within it.
[0070] Click on unread emails in the inbox and use a data packet capture tool to capture valid data packets at different stages of the email retrieval process.
[0071] The valid data packet information at different stages of the email retrieval process is filtered and sorted to obtain the email receiving logic and the valid email information corresponding to the email receiving logic, and presented in code form.
[0072] Step 6: Obtain the DOM elements corresponding to the logical layout of any received email in the target email's inbox folder, as well as the DOM elements corresponding to the plaintext information of the received email. Then, replace the sub-tag information content of the DOM elements corresponding to the plaintext information of the received email, or customize the DOM elements corresponding to the logical layout of the received email. Specifically, this includes the following steps:
[0073] Open any received email in the target email inbox folder and record the DOM elements corresponding to the logical layout of the received emails and the DOM elements corresponding to the plaintext information of the received emails.
[0074] When parsing emails, if it is possible to replace the content of the DOM element corresponding to the plaintext information of the received email, then the content of the child tag information of the DOM element corresponding to the plaintext information of the received email will be replaced; otherwise, the DOM element corresponding to the logical layout of the received email will be customized and reproduced.
[0075] Step 7: Obtain the receiving logic of the sent emails and the corresponding valid email information, and present it in code form; this includes the following steps:
[0076] Open the sent email folder in the target email address, and click on any sent email in the sent email folder interface. At the same time, use a data packet capture tool to capture the effective data packet information of the email at different stages of the sent email display process.
[0077] The valid data packet information at different stages of the sent email display process is filtered and sorted to obtain the receiving logic of the sent email display process and the valid email information corresponding to the receiving logic of the sent email, and presented in code form.
[0078] Step 8: Obtain the DOM elements corresponding to the logical layout of any sent email in the sent folder of the target email address, as well as the DOM elements corresponding to the plaintext information of the sent email. Then, replace the sub-tag information content of the DOM elements corresponding to the plaintext information of the sent emails, or customize the DOM elements corresponding to the logical layout of the sent emails. This includes the following steps:
[0079] Open any sent email in the sent folder of the target email address, and record the DOM elements corresponding to the logical layout of the sent email and the DOM elements corresponding to the plaintext information of the sent email.
[0080] When parsing emails, if it is possible to replace the content of the DOM element corresponding to the plaintext information of the sent email, then the content of the child tag information of the DOM element corresponding to the plaintext information of the sent email will be replaced; otherwise, the DOM element corresponding to the logical layout of the sent email will be customized and reproduced.
[0081] The present invention also provides a browser-side email communication plugin customization development system, including a browser plugin working address and functionality customization unit, a browser plugin encryption module customization unit, and a browser plugin decryption module customization unit.
[0082] The browser plugin working address and functionality customization unit is used to add the static URL of the target email address to the browser plugin development folder; add the customized functional files of the target email address to the browser plugin development folder; the browser plugin encryption module customization unit is used to replace the static DOM element content of the target email's composing interface using pre-determined static element customization content; obtain the keywords of the email sending logic and the keywords of the user's personal privacy information involved in the sent email content, and present the keywords of the user's personal privacy information involved in the sent email content in the form of parameters; the browser plugin decryption module customization unit is used to obtain the email receiving logic and the valid email information corresponding to the email receiving logic, and present it in the form of code; obtain the target email inbox folder. The system retrieves the DOM elements corresponding to the logical layout of received emails and the DOM elements corresponding to the plaintext information of received emails from any received email. It then replaces the sub-tag information of the DOM elements corresponding to the plaintext information of received emails or performs customized reproduction of the DOM elements corresponding to the logical layout of received emails. It also retrieves the receiving logic of sent emails and the corresponding valid email information, presenting it in code form. Finally, it retrieves the DOM elements corresponding to the logical layout of sent emails and the DOM elements corresponding to the plaintext information of sent emails from any sent email in the sent folder of the target mailbox, and replaces the sub-tag information of the DOM elements corresponding to the plaintext information of sent emails or performs customized reproduction of the DOM elements corresponding to the logical layout of sent emails.
[0083] The browser-based email communication plugin customization development method and system described in this invention realizes a user-friendly, lightweight, and secure email communication system that can be customized for different email providers in the form of a browser plugin. Customization allows for customization of the static interface for sending and receiving emails, as well as the email sending and receiving logic, to meet the needs of different email providers and users. The core encryption / decryption process and login process suite only need to be implemented once for reuse in different forms, enabling out-of-the-box operation and improving the system's scalability and maintainability. Furthermore, for users of the current system, the entire operation process is seamless. From the user's perspective, the ease of use and user-friendliness are consistent with the initial web-based email version before system installation, without adding any extra burden to the user.
[0084] Example
[0085] As attached Figure 1 As shown, this embodiment provides a method for customizing browser-side email communication plugins, including the following steps:
[0086] Step 1: Customize the browser plugin's working address and functionality; see attached. Figure 2 As shown, the browser plugin's working address and functionality customization specifically include the following steps:
[0087] Step 11: Open the manifest file in the browser plugin development folder and add the static URL of the target email address; the target email address is the web version of the email address in the browser; specifically: log in to the original target vendor's web version email address, obtain and record the static URL link of the target email address; add the static URL link of the target email address to the matches keyword in the content_scripts module of the manifest file in the browser plugin development folder to complete the URL matching.
[0088] Step 12: Open the manifest file in the browser plugin development folder and add the target-valid customized functional files; specifically, add the plugin function that runs in the web version interface of the target email to the js keyword of the content_scripts module in the manifest file in the browser plugin development folder, so as to complete the customized matching of the target email's functions.
[0089] Step 2: Customization of the browser plugin encryption module; The customization of the browser plugin encryption module aims to achieve the best user experience; see attached... Figure 3 As shown, the specific steps include:
[0090] Step 21: Customize the static encryption interface; specifically including:
[0091] Step 211: Open the target email's compose interface and record the static DOM element content of the target email's compose interface; specifically, open the target email's compose interface, press F12, and record the send button, image links added to the email body, and email attachment upload links in the web version of different email providers' emails.
[0092] Step 212: Replace the static DOM element content of the target email's compose interface with pre-defined customized static element content; specifically, replace the text of the send button in the email sending interface with encrypted send; replace the image link added to the email body with a customized encrypted image link; and replace the email attachment upload link with a customized encrypted attachment link.
[0093] Step 22: Customizing the email sending logic; specifically including:
[0094] Step 221: Prepare the proxy plugin Proxy Switchyomega and the packet capture tool Burp Suite.
[0095] Step 222: Add a new scenario mode under the Scenario Mode module in the proxy plugin proxy switchyomega, and name the new scenario mode burpsuite; set the server IP address of the proxy plugin to 127.0.0.1, and set the proxy port to 8080.
[0096] Step 223: Start the proxy plugin Proxy Switchyomega and select the custom Burp Suite mode as the proxy scenario mode.
[0097] Step 224: Open the compose interface of the target email address and add all user privacy information elements in the compose interface of the target email address; among them, all user privacy information elements include the email body, the image information added in the body, the email attachment information, the email subject, the email recipient's email address, the email CC's email address, and the email BCC's email address.
[0098] Step 225: Launch the packet capture tool Burp Suite; click the send button on the target email's sending interface, and use Burp Suite to capture the email data packets during the email sending process; the target IP address and port number of the packet capture tool do not need to be changed. When you click the send button on the email sending interface, you can obtain the email data packets during the email sending process in the proxy module of Burp Suite.
[0099] Step 226: By clicking the Forward button on the packet capture interface of the proxy module of the packet capture tool Burp Suite, obtain the effective data packet information of the email at different stages of the email sending process.
[0100] Step 227: For the valid data packets of the email at different stages of the email sending process, filter the data packets containing valid email information, and then capture the valid data packets by clicking the Action button of the packet capture tool Burp Suite and clicking the Send to Repeater option.
[0101] Step 228: Based on step 227, for the intercepted data packets containing valid information, the Repeater module filters the valid information to obtain the keywords of the email sending logic; wherein, the keywords of the email sending logic include Post, Host, Accept and Content-Type.
[0102] Step 229: Based on step 227, extract keywords related to user personal privacy information from the intercepted data packet containing valid information, and present the keywords related to user personal privacy information in the sent email content as parameters.
[0103] Based on steps 2210, 228, and 229, customize the keywords for the email sending logic and the keyword requirements for user personal privacy information involved in the email content to complete the customized development of the target email sending function module.
[0104] Step 3: Customization of the browser plugin decryption module; During the customization of the browser plugin decryption module, due to differences in the email receiving logic among different email providers, to achieve the best user experience and optimal customization, this includes customizing the decrypted display of emails in the inbox folder and the decrypted display of emails in the sent folder, as shown in the attached document. Figure 4 As shown, the specific steps include:
[0105] Step 31: Customize the decryption and display of emails in the inbox folder; specifically including:
[0106] Step 311: Customizing the email retrieval logic
[0107] Step 311a: Prepare the proxy plugin Proxy Switchyomega and the packet capture tool Burp Suite.
[0108] Step 311b: Add a new scenario mode under the scenario mode module in the proxy plugin proxy switchyomega, and name the new scenario mode as burpsuite; set the server IP address of the proxy plugin to 127.0.0.1, and set the proxy port to 8080.
[0109] Step 311c: Start the proxy plugin proxy switchyomega and select the custom Burp Suite mode as the proxy scenario mode.
[0110] Step 311d: Open the target email inbox folder and find the unread emails in the target email inbox folder.
[0111] Step 311e: Launch the packet capture tool Burp Suite; click on the unread email in the inbox interface, and use the packet capture tool to capture the email data packet information during the email retrieval process; the target IP address and port number of the packet capture tool do not need to be changed. While clicking on the unread email in the inbox interface, the email data packet information during the email retrieval process can be obtained in the proxy module of the packet capture tool Burp Suite.
[0112] Step 311f: By clicking the Forward button on the packet capture interface of the proxy module of the packet capture tool Burp Suite, obtain the effective data packet information of emails at different stages of the email retrieval process.
[0113] Step 311g: For the valid data packets of emails at different stages of the email retrieval process, observe the receiving logic of the email retrieval and the valid email information corresponding to the receiving logic of the email retrieval. Click the Action button and select the Send to Repeater option to capture the corresponding valid data packets and obtain the receiving logic of the email retrieval and the valid email information corresponding to the receiving logic of the email retrieval.
[0114] Step 311h: The receiving logic for receiving emails and the corresponding valid email information are presented in code form to complete the customization of the user's email receiving logic.
[0115] Step 312: Show the customized content of the decrypted email.
[0116] Step 312a: Open any received email in the target email inbox folder, press F12, and record the DOM elements corresponding to the logical layout of the received email and the DOM elements corresponding to the plaintext information of the received email; wherein, any received email in the target email inbox folder is any email containing comprehensive extended information, including attachment information and body image information.
[0117] Step 312b: For different email vendors, when parsing emails, if it is possible to replace the content of the DOM elements corresponding to the plaintext information of the received emails, then replace the content of the child tags of the DOM elements corresponding to the plaintext information of the received emails; if not, then customize and reproduce the DOM elements corresponding to the logical layout of the received emails. The process of customizing and reproducing the DOM elements corresponding to the logical layout of the received emails is to manually implement the same layout pattern, so that users are unaware of the plugin's operation.
[0118] Step 32: Customize the decryption and display of emails in the sent folder; specifically, this includes:
[0119] Step 321: Customization of the logic for retrieving sent emails
[0120] Step 321a: Prepare the proxy plugin Proxy Switchyomega and the packet capture tool Burp Suite.
[0121] Step 321b: Add a new scenario mode under the scenario mode module in the proxy plugin proxy switchyomega, and name the new scenario mode as burpsuite; set the server IP address of the proxy plugin to 127.0.0.1, and set the proxy port to 8080.
[0122] Step 321c: Start the proxy plugin proxy switchyomega and select the custom Burp Suite mode as the proxy scenario mode.
[0123] Step 321d: Open the "Sent Items" folder in the target email address.
[0124] Step 321e: Launch the packet capture tool Burp Suite; in the sent email folder of the target email address, click on any sent email and use Burp Suite to capture the data packet information during the sending email display process; the target IP address and port number of the capture tool do not need to be changed. When clicking on any sent email in the sent email folder of the target email address, the data packet information during the sending email display process can be obtained in the proxy module of Burp Suite.
[0125] Step 321f: By clicking the Forward button on the packet capture interface of the proxy module of the packet capture tool Burp Suite, obtain the valid data packet information of emails at different stages during the display of sent emails.
[0126] Step 321g: For the valid data packets of emails at different stages of the sent email display process, observe the receiving logic of the sent email display process and the valid email information corresponding to the receiving logic of the sent emails. Click the Action button and select the Send to Repeater option to capture the corresponding valid data packets and obtain the receiving logic of the sent email display process and the valid email information corresponding to the receiving logic of the sent emails.
[0127] Step 321h: The receiving logic of the sent email display process and the corresponding valid email information of the sent email receiving logic are presented in code form to complete the customization of the user's sent email decryption logic.
[0128] Step 322: Customize the display of the decrypted content of the sent email.
[0129] Step 322a: Open any sent email in the sent folder of the target email address, press F12, and record the DOM elements corresponding to the logical layout of the sent email and the DOM elements corresponding to the plaintext information of the sent email in any sent email in the sent folder; wherein, any sent email in the sent folder of the target email address is any email containing comprehensive extended information, including attachment information and image information in the body.
[0130] Step 322b: For different email vendors, when parsing emails, if it is possible to replace the content of the DOM elements corresponding to the plaintext information of sent emails, then replace the content of the child tag information of the DOM elements corresponding to the plaintext information of sent emails; if not, then customize and reproduce the DOM elements corresponding to the logical layout of sent emails. The process of customizing and reproducing the DOM elements corresponding to the logical layout of sent emails is to manually implement the same layout pattern, so that users are unaware of the plugin's operation.
[0131] In this embodiment, by analyzing the static interfaces and email sending and receiving logic of web-based email providers from different email vendors, customizable content is obtained. Then, under the premise of good system scalability and maintainability and user experience that is no different from the initial system, various customizations are made for the plugin's running email address and the email encryption and decryption processes within the plugin. The customized development is combined with the browser-side email encryption and decryption security communication plugin to meet users' personalized adaptation needs for web-based email providers from different vendors while keeping the core technology support unchanged.
[0132] The browser-based email communication plugin customization development method and system described in this invention simplifies the adaptation issues for different email vendors, greatly reducing development and maintenance costs for developers. It also significantly improves the future compatibility and scalability for different email vendors, making it developer-friendly. Secondly, the core functional encryption / decryption module can exist independently of the upper-layer email, meaning the core functional module remains unchanged for different email vendors, significantly improving the maintainability of core functions and enabling the reuse of the same core functional code, greatly improving development efficiency. Furthermore, for users, the overall operation of the plugin is imperceptible before and after loading, ensuring a consistent user experience without imposing any additional burden on the user, resulting in a good user experience.
[0133] The above embodiments are merely one of the implementation methods for achieving the technical solution of the present invention. The scope of protection claimed by the present invention is not limited to this embodiment, but also includes any variations, substitutions and other implementation methods that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention.
Claims
1. A method for customizing browser-based email communication plugins, characterized in that, include: Add the static URL of the target email address to the browser plugin development folder; In the browser plugin development folder, add the customized functional files for the target email address; By customizing the content of predefined static elements, the static DOM element content of the target email's compose interface is replaced. Obtain the keywords of the email sending logic and the keywords of the user's personal privacy information involved in the email content, and present the keywords of the user's personal privacy information involved in the email content as parameters; Retrieve the email receiving logic and the corresponding valid email information, and present it in code form. Retrieve the DOM elements corresponding to the logical layout of any received email in the target email inbox folder, as well as the DOM elements corresponding to the plaintext information of the received email. Then, replace the sub-tag information content of the DOM elements corresponding to the plaintext information of the received email or perform customized reproduction of the DOM elements corresponding to the logical layout of the received email. Retrieve the receiving logic of sent emails and the corresponding valid email information, and present it in code form; Retrieve the DOM elements corresponding to the logical layout of sent emails and the DOM elements corresponding to the plaintext information of sent emails from any sent email in the sent folder of the target email address, and replace the sub-tag information content of the DOM elements corresponding to the plaintext information of sent emails or perform customized reproduction of the DOM elements corresponding to the logical layout of sent emails. The process of replacing the static DOM element content of the target email's compose interface using predefined static element customization is as follows: Open the target email's compose interface and record the static DOM element content of the target email's compose interface; the static DOM element content of the target email's compose interface includes the send button in the email sending interface, the link to add images to the email body, and the link to upload email attachments; Replace the text of the send button in the email sending interface with "encrypted send"; Replace adding image links in the email body with adding encrypted image links in a custom format; Replace the email attachment upload link with a custom encrypted attachment link.
2. The method for customizing a browser-based email communication plugin according to claim 1, characterized in that, The process of adding the static URL of the target email address to the browser plugin development folder is as follows: Log in to the target email address and record its static URL; the target email address is a web-based email address accessible through a browser. Add the static URL of the target email address to the `matches` keyword in the `content_scripts` module of the manifest file under the browser plugin development files.
3. The method for customizing a browser-based email communication plugin according to claim 1, characterized in that, The process of adding the customized feature files for the target email address to the browser plugin development folder is as follows: Add the plugin functionality that customizes the web interface of the target email address to the `js` keyword in the `content_scripts` module of the `manifest` file under the browser plugin development files.
4. The method for customizing a browser-based email communication plugin according to claim 1, characterized in that, The process of obtaining keywords related to email sending logic and keywords related to user personal privacy information in the email content, and presenting these keywords as parameters, is as follows: Open the target email's compose interface and add all user privacy information elements within the target email's compose interface; Click the send button on the target email's sending interface, and at the same time use a data packet capture tool to capture the effective data packet information of the email at different stages of the email sending process; The effective data packets of the email at different stages of the email sending process are screened and filtered to obtain keywords of the email sending logic and keywords of user personal privacy information involved in the email content. Keywords related to user personal privacy information in the sent email content are presented as parameters.
5. The method for customizing a browser-based email communication plugin according to claim 1, characterized in that, The process of retrieving emails and obtaining the corresponding valid email information, presented in code, is as follows: Open the target email inbox folder and locate the unread emails within it. Click on unread emails in the inbox and use a data packet capture tool to capture valid data packets at different stages of the email retrieval process. The valid data packet information at different stages of the email retrieval process is filtered and sorted to obtain the email receiving logic and the valid email information corresponding to the email receiving logic, and presented in code form.
6. The method for customizing a browser-based email communication plugin according to claim 1, characterized in that, The process of retrieving the DOM elements corresponding to the logical layout of any received email in the target email's inbox folder, as well as the DOM elements corresponding to the plaintext information of the received email, and then replacing the child tag information of the DOM elements corresponding to the plaintext information of the received email or customizing the DOM elements corresponding to the logical layout of the received email is as follows: Open any received email in the target email inbox folder and record the DOM elements corresponding to the logical layout of the received emails and the DOM elements corresponding to the plaintext information of the received emails. When parsing emails, if it is possible to replace the content of the DOM element corresponding to the plaintext information of the received email, then the content of the child tag information of the DOM element corresponding to the plaintext information of the received email will be replaced; otherwise, the DOM element corresponding to the logical layout of the received email will be customized and reproduced.
7. The method for customizing a browser-side email communication plugin according to claim 1, characterized in that, The process of retrieving the receiving logic of sent emails and the corresponding valid email information, and presenting it in code form, is as follows: Open the sent email folder in the target email address, and click on any sent email in the sent email folder interface. At the same time, use a data packet capture tool to capture the effective data packet information of the email at different stages of the sent email display process. The valid data packet information at different stages of the sent email display process is filtered and selected to obtain the receiving logic of the sent email display process and the valid email information corresponding to the receiving logic of the sent email, and then presented in code form.
8. A method for customizing a browser-based email communication plugin according to claim 1, characterized in that, The process of retrieving the DOM elements corresponding to the logical layout of sent emails and the DOM elements corresponding to the plaintext information of sent emails from any sent email in the sent folder of the target email address, and then replacing the sub-tag information content of the DOM elements corresponding to the plaintext information of sent emails or customizing the DOM elements corresponding to the logical layout of sent emails, is as follows: Open any sent email in the sent folder of the target email address, and record the DOM elements corresponding to the logical layout of the sent email and the DOM elements corresponding to the plaintext information of the sent email. When parsing emails, if it is possible to replace the content of the DOM element corresponding to the plaintext information of the sent email, then the content of the child tag information of the DOM element corresponding to the plaintext information of the sent email will be replaced; otherwise, the DOM element corresponding to the logical layout of the sent email will be customized and reproduced.
9. A browser-based email communication plugin customization development system, characterized in that, include: The browser plugin working address and functional customization unit is used to add the static URL of the target email address to the browser plugin development folder; In the browser plugin development folder, add the customized functional files for the target email address; The browser plugin encryption module's customization unit is used to replace the static DOM element content of the target email's compose interface by customizing the content using predefined static elements. Obtain the keywords of the email sending logic and the keywords of the user's personal privacy information involved in the email content, and present the keywords of the user's personal privacy information involved in the email content as parameters; The browser plugin decryption module's customization unit is used to obtain the email receiving logic and the corresponding valid email information, and present it in code form. Retrieve the DOM elements corresponding to the logical layout of any received email in the target email inbox folder, as well as the DOM elements corresponding to the plaintext information of the received email. Then, replace the sub-tag information content of the DOM elements corresponding to the plaintext information of the received email or perform customized reproduction of the DOM elements corresponding to the logical layout of the received email. Retrieve the receiving logic of sent emails and the corresponding valid email information, and present it in code form; Retrieve the DOM elements corresponding to the logical layout of sent emails and the DOM elements corresponding to the plaintext information of sent emails from any sent email in the sent folder of the target email address, and replace the sub-tag information content of the DOM elements corresponding to the plaintext information of sent emails or perform customized reproduction of the DOM elements corresponding to the logical layout of sent emails. The process of replacing the static DOM element content of the target email's compose interface using predefined static element customization is as follows: Open the target email's compose interface and record the static DOM element content of the target email's compose interface; the static DOM element content of the target email's compose interface includes the send button in the email sending interface, the link to add images to the email body, and the link to upload email attachments; Replace the text of the send button in the email sending interface with "encrypted send"; Replace adding image links in the email body with adding encrypted image links in a custom format; Replace the email attachment upload link with a custom encrypted attachment link.