WO2014000652A1 - 浏览器插件安装方法、装置及终端 - Google Patents
浏览器插件安装方法、装置及终端 Download PDFInfo
- Publication number
- WO2014000652A1 WO2014000652A1 PCT/CN2013/078056 CN2013078056W WO2014000652A1 WO 2014000652 A1 WO2014000652 A1 WO 2014000652A1 CN 2013078056 W CN2013078056 W CN 2013078056W WO 2014000652 A1 WO2014000652 A1 WO 2014000652A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- browser
- browser plug
- plug
- digital signature
- information
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 59
- 238000009434 installation Methods 0.000 title claims abstract description 48
- 238000012545 processing Methods 0.000 claims description 30
- 230000008569 process Effects 0.000 claims description 20
- 230000035945 sensitivity Effects 0.000 claims description 17
- 238000011900 installation process Methods 0.000 claims description 14
- 238000003672 processing method Methods 0.000 claims description 2
- 238000011022 operating instruction Methods 0.000 claims 3
- 230000006870 function Effects 0.000 description 19
- 238000004891 communication Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 7
- 238000001514 detection method Methods 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- SPBWHPXCWJLQRU-FITJORAGSA-N 4-amino-8-[(2r,3r,4s,5r)-3,4-dihydroxy-5-(hydroxymethyl)oxolan-2-yl]-5-oxopyrido[2,3-d]pyrimidine-6-carboxamide Chemical compound C12=NC=NC(N)=C2C(=O)C(C(=O)N)=CN1[C@@H]1O[C@H](CO)[C@@H](O)[C@H]1O SPBWHPXCWJLQRU-FITJORAGSA-N 0.000 description 2
- 102100021677 Baculoviral IAP repeat-containing protein 2 Human genes 0.000 description 2
- 102100021662 Baculoviral IAP repeat-containing protein 3 Human genes 0.000 description 2
- 102100037024 E3 ubiquitin-protein ligase XIAP Human genes 0.000 description 2
- 101000896157 Homo sapiens Baculoviral IAP repeat-containing protein 2 Proteins 0.000 description 2
- 101000896224 Homo sapiens Baculoviral IAP repeat-containing protein 3 Proteins 0.000 description 2
- 101000804865 Homo sapiens E3 ubiquitin-protein ligase XIAP Proteins 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000005484 gravity Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012827 research and development Methods 0.000 description 2
- 230000005236 sound signal Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 241000699666 Mus <mouse, genus> Species 0.000 description 1
- 241000699670 Mus sp. Species 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012905 input function Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000010079 rubber tapping Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000010897 surface acoustic wave method Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/51—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
- G06F9/45529—Embedded in an application, e.g. JavaScript in a Web browser
Definitions
- the present invention relates to the field of mobile terminals, and in particular, to a browser plug-in installation method, device, and terminal. Background technique
- the browser plug-in invokes the API of the mobile terminal during operation (Application Programming Interface , the application programming interface) to obtain the corresponding file or information, and since the browser plug-in can be regarded as an application, the installation process is consistent with the process of installing the application on the mobile terminal, and is not subject to the source of the plug-in.
- API Application Programming Interface
- an embodiment of the present invention provides a browser plug-in installation method, apparatus, and terminal.
- the technical solution is as follows:
- a browser plug-in installation method includes:
- determining whether the browser plug-in is legal according to the digital signature information of the browser plug-in and the browser information of the specified browser includes:
- the determining, according to the digital signature information of the browser plug-in and the browser information of the specified browser, whether the browser plug-in is legal, previously comprising:
- the application interface that displays the browser plugin declaration includes:
- the browser plug-in carries digital signature information, and the digital signature information is obtained by digitally signing the browser plug-in by a server of the specified browser.
- the second aspect provides a browser plug-in processing method, where the method includes:
- the browser plugin is processed according to an application interface of a specified browser invoked by the browser plugin.
- the processing according to the application interface of the specified browser invoked by the browser plug-in, processing the browser plug-in, including:
- the browser plugin is digitally signed, and the obtained digital signature information is packaged into the browser plugin;
- a browser plug-in installation device comprising:
- a first receiving module configured to receive an installation instruction for a browser plug-in, where the browser plug-in is applied to a specified browser
- a determining module configured to determine, according to the digital signature information of the browser plug-in and the browser information of the specified browser, whether the browser plug-in is legal;
- the installation module is configured to: when the determining module determines that the browser plug-in is legal, the browser plug-in is installed; the installing module is further configured to: when the determining module determines that the browser plug-in is illegal, rejecting Install the browser plugin.
- the determining module is specifically configured to verify digital signature information of the browser plug-in according to the browser information, and when the browser information matches the digital signature information, the browser plug-in is legal, otherwise, The browser plugin is not legal.
- the device further includes: a display module, configured to display an application interface of the browser plugin declaration;
- the installation module is configured to continue or not to continue the installation process according to the received operation instruction.
- the display module is specifically configured to display an application program interface declared by the browser plug-in, and display a sensitivity level of each of the application program interfaces.
- the browser plug-in carries digital signature information, and the digital signature information is obtained by digitally signing the browser plug-in by a server of the specified browser.
- a browser plug-in processing apparatus where the apparatus includes:
- a second receiving module configured to receive a browser plug-in
- a processing module configured to process the browser plug-in according to an application interface of the specified browser invoked by the browser plug-in.
- processing module includes:
- a determining unit configured to determine whether an application interface of the specified browser invoked by the browser plug-in matches an application interface declared by the browser plug-in
- a processing unit configured to: when an application interface of the specified browser invoked by the browser plug-in matches an application interface declared by the browser plug-in, digitally sign the browser plug-in, and obtain the obtained digital signature information Packaged to the browser plugin;
- the processing unit is further configured to: when the browser interface of the specified browser invoked by the browser plug-in does not match the application interface declared by the browser plug-in, the browser plug-in is not processed.
- the browser plug-in is applied to the specified browser by receiving an installation instruction to the browser plug-in; determining whether the browser plug-in is legal according to the digital signature information of the browser plug-in and the browser information of the specified browser If yes, install the browser plugin, if no, refuse to install the browser plugin.
- the browser plug-in is verified according to the digital signature information of the browser plug-in and the browser information of the corresponding browser at the beginning of the installation to determine the legality of the browser plug-in. Sexuality and traceability, avoiding the arbitrary call of the harmful browser plug-in to the mobile terminal API, and improving the security of the mobile terminal.
- FIG. 1 is a flowchart of a method for installing a browser plug-in according to an embodiment of the present invention
- FIG. 2 is a flowchart of a method for installing a browser plug-in according to an embodiment of the present invention
- FIG. 3 is a flowchart of a method for processing a browser plug-in according to an embodiment of the present invention
- FIG. 4 is a schematic structural diagram of a browser plug-in installation device according to an embodiment of the present invention.
- FIG. 5 is a schematic structural diagram of a browser plug-in processing apparatus according to an embodiment of the present invention.
- FIG. 6 is a schematic structural diagram of a terminal according to an embodiment of the present invention. detailed description
- FIG. 1 is a flowchart of a method for installing a browser plug-in according to an embodiment of the present invention.
- the executor of the embodiment is a mobile terminal. Referring to FIG. 1, the embodiment specifically includes:
- step 102 determines whether the browser plug-in is legal, if yes, go to step 103; if no, go to step 104;
- determining, according to the digital signature information of the browser plug-in and the browser information of the specified browser, whether the browser plug-in is legal including but not limited to:
- determining, according to the digital signature information of the browser plug-in and the browser information of the specified browser, whether the browser plug-in is legal, previously comprising:
- the application interface that displays the browser plugin declaration includes, but is not limited to:
- the browser plug-in carries digital signature information obtained by digitally signing the browser plug-in by a server of the specified browser.
- the browser plug-in is applied to the specified browser by receiving an installation instruction to the browser plug-in; and determining, according to the digital signature information of the browser plug-in and the browser information of the specified browser, Place Whether the browser plugin is legal, if yes, install the browser plugin, if not, refuse to install the browser plugin.
- the browser plug-in is verified according to the digital signature information of the browser plug-in and the browser information of the corresponding browser at the beginning of the installation to determine the legality of the browser plug-in. Sexuality and traceability, avoiding the arbitrary call of the harmful browser plug-in to the mobile terminal API, and improving the security of the mobile terminal.
- FIG. 2 is a flowchart of a method for processing a browser plug-in according to an embodiment of the present invention.
- the executor of the embodiment is a server. Referring to FIG. 2, the embodiment specifically includes:
- the browser plug-in is processed according to an application interface of the specified browser invoked by the browser plug-in, including but not limited to:
- the browser plugin is digitally signed, and the obtained digital signature information is packaged into the browser plugin;
- FIG. 3 is a flowchart of a method for installing a browser plug-in according to an embodiment of the present invention. This embodiment is described by taking the processing of the browser plug-in by the mobile terminal and the server as an example. Referring to FIG. 3, the embodiment specifically includes:
- the server receives a browser plugin.
- the browser plug-in in this embodiment refers to a plug-in developed by a developer that can be installed and run on a specified browser.
- the function of the browser plug-in can be various, and is not specifically limited in this embodiment.
- the specific working process may include: in the process of specifying the browser, calling the mobile terminal API specified by the browser plug-in to directly access the mobile terminal API To get the corresponding file through the mobile terminal API.
- the API is a predefined function, the purpose is to provide the ability of the application and the developer to access a set of routines based on a certain software or hardware.
- the application or plugin calls an API, the mobile terminal accesses the corresponding API.
- the browser When the browser needs to use the address book of the mobile terminal, the browser The mobile terminal sends an instruction to call the address book API, and the mobile terminal receives the call instruction and calls the address book API, and the browser accesses the address book API to obtain the corresponding file of the address book.
- the developer or the mobile terminal user uploads the developed browser plug-in to the server of the specified browser, so that the server receives the browser plug-in.
- the upload may be a pressure of uploading the browser plug-in.
- the package plug-in itself can also be uploaded, and is not specifically limited herein.
- the server determines whether the API of the specified browser invoked by the browser plug-in matches the API declared by the browser plug-in;
- step 303 If yes, go to step 303;
- each browser plug-in includes a technical developer's declaration of the plug-in, the statement including the API name to be called by the browser plug-in, and the declaration may be in the form of a list.
- browser plug-in A's declaration includes API1, API2, and API3, which means that browser plug-in A needs to call API1, API2, and API3 at runtime.
- the server In order to confirm whether the browser plug-in is secure, after receiving the browser plug-in, the server detects the API of the specified browser that the browser plug-in actually calls, if the browser plug-in invokes the specified browser API and the browser plug-in statement. If the API matches, step 303 is performed; if it does not match, no processing is performed on the browser plugin.
- the server digitally signs the browser plugin, and packages the obtained digital signature information into the browser plugin.
- step 303 when digital signature is performed, it can be divided into the following two according to different encryption methods: (1) When the encryption method is symmetric key encryption, that is, both sides transmitting and receiving data must use the same/ The symmetric key encrypts and decrypts the plaintext, the server digitally signs the browser plug-in using the server's key, and packages the obtained digital signature information into the browser plug-in; (2) when the encryption method is non- Symmetric key encryption, the server has a corresponding public key and private key with the specified browser client, the server uses the private key to digitally sign the browser plugin, and the specified browser client holds the corresponding public key, then when browsing When the plugin is installed on the specified browser, the browser plugin can be verified with the corresponding public key to determine the security of the browser plugin.
- the encryption method is symmetric key encryption, that is, both sides transmitting and receiving data must use the same/ The symmetric key encrypts and decrypts the plaintext
- the server digitally signs the browser plug-in using the server's key, and packages the obtained digital signature
- the process of digitally signing the browser plug-in by the server is: generating a message digest from the message text of the browser plug-in by using a hash function, and the server encrypts the message digest using the private key corresponding to the public key of the server.
- the encrypted abstract is the digital signature information of the browser plug-in, thus completing the digital signature process.
- the above steps 301-303 are processes for the server to verify and digitally sign the browser plug-in.
- the digital signature process indicates that the server recognizes the browser plug-in, and provides the mobile terminal with a basis for verifying the legality of the browser plug-in.
- the mobile terminal downloads a browser plug-in; It should be noted that after the server digitally signs the browser plug-in, the browser plug-in carrying the digital signature information can be saved and opened for download.
- the mobile terminal can download the browser plug-in directly from the server, and can also download the browser plug-in from the network.
- the source of the browser plug-in is not limited in the embodiment of the present invention.
- the mobile terminal receives an installation instruction for a browser plug-in.
- the installation instruction of the browser plug-in is triggered by a keyboard or a sliding gesture, and the mobile terminal starts the installation process when receiving the installation instruction.
- the mobile terminal interface displays a sensitivity level of an API and an API declared by the browser plugin.
- the sensitivity level of the API is set in the browser plug-in development process, and is set by the technical research and development personnel according to the specific functions of the API.
- the sensitivity level of the API can be divided into two levels, such as: The numbers "1" and "0" are used. Among them, the sensitive level API is represented by “1", and the non-sensitive level API is represented by "0".
- the called API and its sensitivity level are displayed on the mobile terminal interface, according to the preset settings of the technology developer, it is displayed as an API+ sensitive level, such as: Address Book API+ "1", system file API+”0", indicating the communication
- the API is a sensitive API
- the system file API is a non-sensitive API.
- the sensitivity level of the API can be further divided into other levels according to the settings of the technical research and development personnel. This embodiment is not specifically limited herein.
- the mobile terminal user can be facilitated to have a preliminary understanding of the API invoked by the browser plug-in.
- the API invoked by the browser plug-in is a sensitive API
- the mobile terminal user can The security requirements continue or do not continue with the current installation.
- the mobile terminal receives the operation instruction for continuing to install, determining, according to the digital signature information of the browser plug-in and the browser information of the specified browser, whether the browser plug-in is legal;
- an operation command is also displayed on the mobile terminal interface for prompting the user whether to install the browser plug-in.
- the left and right function keys on the mobile terminal respectively control these two operations, and the mobile terminal user determines whether according to the declaration API and its sensitivity level displayed on the interface.
- Install the browser plugin When the mobile terminal receives an operation instruction to continue the installation, the installation process is not continued.
- the browser information is specifically a public key of the specified browser, and the public key corresponds to a private key used by the server to digitally sign the browser plug-in, and the mobile terminal is configured according to the designated browser.
- the key verification information of the browser plug-in is verified. When the browser information matches the digital signature information, the browser plug-in is legal. Otherwise, the browser plug-in is invalid.
- the specific verification process is known in the prior art and will not be described here.
- the process of installing the browser plug-in in the mobile terminal is similar to the application installation process, and will not be described here. 309. Refuse to install the browser plugin.
- the browser plug-in is applied to the specified browser by receiving an installation instruction to the browser plug-in; and determining, according to the digital signature information of the browser plug-in and the browser information of the specified browser, Whether the browser plugin is legal, if yes, the browser plugin is installed, and if not, the browser plugin is refused to be installed.
- the browser plug-in is verified according to the digital signature information of the browser plug-in and the browser information of the corresponding browser at the beginning of the installation to determine the legality of the browser plug-in. Sexuality and traceability, avoiding the arbitrary call of the harmful browser plug-in to the mobile terminal API, and improving the security of the mobile terminal.
- the device may be a terminal device, and the terminal device may be a mobile terminal or a fixed terminal.
- the mobile terminal may specifically be a smart phone, a notebook computer or other mobile device, and the fixed terminal may be a personal computer or the like.
- the device includes:
- the first receiving module 401 is configured to receive an installation instruction for the browser plug-in, where the browser plug-in is applied to the specified browsing determining module 402, configured to perform, according to the digital signature information of the browser plug-in, and the browsing of the specified browser.
- Device information determining whether the browser plugin is legal;
- the installation module 403 is configured to: when the determining module determines that the browser plug-in is legal, install the browser plug-in; the installing module 403 is further configured to: when the determining module determines that the browser plug-in is illegal , refuse to install the browser plugin.
- the determining module 402 is specifically configured to verify, according to the browser information, digital signature information of the browser plug-in.
- the browser plug-in is legal, otherwise The browser plugin is not legal.
- the device further includes:
- a display module 404 configured to display an application interface of the browser plugin declaration
- the installation module 403 is configured to continue or not to continue the installation process according to the received operation instruction.
- the installation module 403 is configured to continue or not to continue the installation process according to the received operation instruction.
- the display module 404 is specifically configured to display an application interface declared by the browser plug-in, and display a sensitivity level of each of the application interfaces.
- the browser plug-in carries digital signature information obtained by digitally signing the browser plug-in by a server of the specified browser.
- the device for installing the browser plug-in only uses the browser plug-in when installing the browser plug-in.
- the division of each of the above functional modules is illustrated.
- the above-mentioned function assignments may be completed by different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.
- the method for installing the browser plug-in provided by the foregoing embodiment and the device embodiment for installing the browser plug-in are the same concept, and the specific implementation process is described in detail in the method embodiment, and details are not described herein again.
- FIG. 5 is a schematic structural diagram of a browser plug-in processing apparatus according to an embodiment of the present invention.
- the device is located on the server side that serves the specified browser. Referring to Figure 5, the device includes:
- a second receiving module 501 configured to receive a browser plug-in
- the processing module 502 is configured to process the browser plug-in according to an application interface of the specified browser invoked by the browser plug-in.
- processing module 502 includes:
- a determining unit configured to determine whether an application interface of the specified browser invoked by the browser plug-in matches an application interface declared by the browser plug-in
- a processing unit configured to: when an application interface of the specified browser invoked by the browser plug-in matches an application interface declared by the browser plug-in, digitally sign the browser plug-in, and obtain the obtained digital signature information Packaged to the browser plugin;
- the processing unit is further configured to: when the browser interface of the specified browser invoked by the browser plug-in does not match the application interface declared by the browser plug-in, the browser plug-in is not processed.
- FIG. 6 is a schematic structural diagram of a terminal according to an embodiment of the present invention, which is a schematic structural diagram of a touch sensitive surface according to an embodiment of the present invention.
- the terminal can be used to implement the browser plug-in provided in the foregoing embodiment. Installed Method. Specifically:
- the terminal 600 may include an RF (Radio Frequency) circuit 110, a memory 120 including one or more computer readable storage media, an input unit 130, a display unit 140, a sensor 150, an audio circuit 160, a transmission module 170, including One or more processing core processor 180, and power supply 190 and the like.
- RF Radio Frequency
- the RF circuit 110 can be used for receiving and transmitting signals during and after receiving or transmitting information, in particular, after receiving downlink information of the base station, and processing it by one or more processors 180; in addition, transmitting uplink data to the base station .
- the RF circuit 110 includes, but is not limited to, an antenna, at least one amplifier, a tuner, one or more oscillators, a Subscriber Identity Module (SIM) card, a transceiver, a coupler, and an LNA (Low Noise). Amplifier), duplexer, etc.
- RF circuitry 110 can also communicate with the network and other devices via wireless communication.
- the wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System of Mobility Communication System), GPRS (General Packet Radio Service) CDMA (Code Divi) s ion Mult iple Access, code division multiple access) WCDMA (Wideband Code Divi s ion Mult iple Access), LTE (Long Term Evolut ion), e-mail, SMS (Short Messaging Service, short) Message service) and so on.
- GSM Global System of Mobility Communication System
- GPRS General Packet Radio Service
- CDMA Code Divi) s ion Mult iple Access
- code division multiple access code division multiple access
- WCDMA Wideband Code Divi s ion Mult iple Access
- LTE Long Term Evolut ion
- e-mail Short Messaging Service, short
- the memory 120 can be used to store software programs and modules, such as software programs and modules corresponding to the devices for improving the running speed of the application in the third embodiment, and the processor 180 executes various functions by running software programs and modules stored in the memory 120.
- Application and data processing such as improving the running speed of the application.
- the memory 120 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may be stored according to The data created by the use of the terminal 600 (such as audio data, phone book, etc.) and the like.
- memory 120 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, memory 120 may also include a memory controller to provide access to memory 120 by processor 180 and input unit 130.
- the input unit 130 can be configured to receive input numeric or character information and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls.
- input unit 130 may include touch-sensitive surface 131 as well as other input devices 132.
- Touch-sensitive surface 131 also referred to as a touch display or trackpad, can collect touch operations on or near the user (eg, the user uses a finger, stylus, etc., on any touch-sensitive surface 131 or on the touch-sensitive surface 131 The operation near the touch-sensitive surface 131) and driving the corresponding connecting device according to a preset program.
- the touch-sensitive surface 131 may include two parts of a touch detection device and a touch controller.
- the touch detection device Detecting a user's touch orientation, detecting a signal brought by the touch operation, and transmitting a signal to the touch controller; the touch controller receives the touch information from the touch detection device, and converts it into contact coordinates, and sends the signal to the processor 180, And can receive the command sent by the processor 180 and execute it.
- the touch-sensitive surface 131 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves.
- the input unit 130 can also include other input devices 132.
- other input devices 132 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackballs, mice, joysticks, and the like.
- Display unit 140 can be used to display information entered by the user or information provided to the user, as well as various graphical user interfaces of terminal 600, which can be constructed from graphics, text, icons, video, and any combination thereof.
- the display unit 140 may include a display panel 141.
- the display panel 141 may be configured in the form of an LCD (Liquid Crystal Display), an OLED (Organic Light-Emitting Diode), or the like.
- the touch-sensitive surface 131 may cover the display panel 141, and when the touch-sensitive surface 131 detects a touch operation thereon or nearby, it is transmitted to the processor 180 to determine the type of the touch event, and then the processor 180 according to the touch event The type provides a corresponding visual output on display panel 141.
- touch-sensitive surface 131 and display panel 141 are implemented as two separate components to implement input and input functions, in some embodiments, touch-sensitive surface 131 can be integrated with display panel 141 for input. And output function.
- Terminal 600 can also include at least one type of sensor 150, such as a light sensor, motion sensor, and other sensors.
- the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 141 according to the brightness of the ambient light, and the proximity sensor may close the display panel 141 when the terminal 600 moves to the ear. / or backlight.
- the gravity acceleration sensor can detect the acceleration of each direction (usually three axes), and the magnitude and direction of gravity can be detected at rest.
- the gesture of the mobile phone such as horizontal and vertical screen switching, related Game, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for the terminal 600 can also be configured with gyroscopes, barometers, hygrometers, thermometers, infrared sensors and other sensors, here Let me repeat.
- the audio circuit 160, the speaker 161, and the microphone 162 provide an audio interface between the user and the terminal 600.
- the audio circuit 160 can transmit the converted electrical data of the received audio data to the speaker 161 for conversion to the sound signal output by the speaker 161; on the other hand, the microphone 162 converts the collected sound signal into an electrical signal by the audio circuit 160. After receiving, it is converted into audio data, and then processed by the audio data output processor 180, transmitted to the terminal, for example, by the RF circuit 110, or outputted to the memory 120 for further processing.
- the audio circuit 160 may also include an earbud jack to provide communication between the peripheral earphone and the terminal 600.
- the terminal 600 can help the user to send and receive emails, browse web pages, access streaming media, etc. through the transmission module 170, which provides the user with wireless or wired broadband Internet access.
- FIG. 6 shows the transmission module 170, it can be rationalized. It is understood that it does not belong to the essential configuration of the terminal 600, and can be omitted as needed within the scope of not changing the essence of the invention.
- the processor 180 is the control center of the terminal 600, which connects various portions of the entire handset using various interfaces and lines, by running or executing software programs and/or modules stored in the memory 120, and recalling data stored in the memory 120, The various functions and processing data of the terminal 600 are performed to perform overall monitoring of the mobile phone.
- the processor 180 may include one or more processing cores.
- the processor 180 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, an application, and the like.
- the modem processor primarily handles wireless communications. It will be appreciated that the above described modem processor may also not be integrated into the processor 180.
- the terminal 600 also includes a power source 190 (such as a battery) for powering various components.
- the power source can be logically coupled to the processor 180 through the power management system to manage functions such as charging, discharging, and power management through the power management system.
- Power supply 190 may also include any one or more of a DC or AC power source, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and the like.
- the terminal 600 may further include a camera, a Bluetooth module, and the like, and details are not described herein.
- the display unit of the terminal is a touch screen display
- the terminal further includes a memory, and one or more programs, wherein one or more programs are stored in the memory and configured to be processed by one or more
- the execution of one or more programs includes instructions for performing the following operations:
- the memory of the terminal further includes an instruction for performing the following operations. :
- the memory of the terminal further includes an instruction for performing the following operations:
- the memory of the terminal further includes an instruction for performing the following operations:
- the memory of the terminal further includes an instruction for performing the following operations:
- the browser plug-in carries digital signature information obtained by digitally signing the browser plug-in by a server of the specified browser.
- the terminal determines whether the browser plug-in is legally determined by determining whether the API of the received browser plug-in declaration and the actually called API match, and determining whether the browser plug-in is legal. Sexuality and traceability, avoiding the arbitrary call of the harmful browser plug-in to the mobile terminal API, and improving the security of the mobile terminal.
- the embodiment of the present invention provides a computer readable storage medium, which may be a computer readable storage medium included in the memory in the above embodiment, or may exist separately and not assembled into the terminal. Computer readable storage medium.
- the computer readable storage medium stores one or more programs, the one or more programs being used by one or more processors to perform a sliding control method, the method comprising:
- the digital signature information according to the browser plug-in and the specified browser are Browser information, determining whether the browser plugin is legal, including:
- the application interface that displays the browser plug-in declaration includes:
- the browser plug-in carries digital signature information, and the digital signature information is used by the specified browser Server pair
- the browser plugin is digitally signed.
- the computer readable storage medium determines whether the browser plug-in is legally determined by determining whether the API of the received browser plug-in declaration and the actually called API match, and determining whether the browser plug-in is legal. Sexuality and traceability, avoiding the arbitrary call of the harmful browser plug-in to the mobile terminal API, and improving the security of the mobile terminal.
- a graphical user interface is provided in an embodiment of the present invention, where the graphical user interface is used on a terminal, where the terminal includes a touch screen display, a memory, and one or more processors for executing one or more programs;
- the graphical user interface includes:
- the graphical user interface provided by the embodiment of the present invention determines whether the browser plug-in has a potential threat by determining whether the API of the received browser plug-in declaration and the actually called API match, and determining the legality of the browser plug-in. Traceability avoids the random call of the harmful browser plug-in to the mobile terminal API, which improves the security of the mobile terminal.
- the device installed by the browser plug-in provided by the foregoing embodiment is only illustrated by the division of each functional module in the installation of the plug-in. In actual applications, the function may be assigned to different functional modules according to requirements. Upon completion, the internal structure of the device is divided into different functional modules to perform all or part of the functions described above.
- the apparatus for installing the browser plug-in provided in the above embodiment is the same as the embodiment of the method for installing the browser plug-in. The specific implementation process is described in detail in the method embodiment, and details are not described herein again.
- a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
- the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Stored Programmes (AREA)
- Telephonic Communication Services (AREA)
Abstract
本发明公开了一种浏览器插件安装方法、装置及终端,属于移动终端领域。所述方法包括:通过接收对浏览器插件的安装指令,所述浏览器插件应用于指定浏览器;根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器信息,判断所述浏览器插件是否合法,如果是,则安装所述浏览器插件,如果否,则拒绝安装所述浏览器插件。采用本发明提供的技术方案,通过在安装起始时,根据浏览器插件的数字签名信息和其对应的指定浏览器的浏览器信息对该浏览器插件进行验证,以确定该浏览器插件的合法性和可追溯性,避免了有害浏览器插件对移动终端API的随意调用,提高了移动终端的安全性。
Description
浏览器插件安装方法、 装置及终端 本申请要求于 2012年 06月 26日提交中国专利局、 申请号为 201210214155. 6、发明名 称为 "浏览器插件安装方法及装置" 的中国专利申请的优先权, 其全部内容通过引用结合 在本申请中。 技术领域
本发明涉及移动终端领域, 特别涉及一种浏览器插件安装方法、 装置及终端。 背景技术
随着移动终端的迅速发展, 用户可以使用移动终端上安装的浏览器访问网络, 而移动 终端浏览器支持浏览器插件的扩展, 浏览器插件在运行过程中通过调用移动终端的 API (Application Programming Interface, 应用程序编程接口) 以获取相应文件或信息, 而由于 浏览器插件可以视为一种应用程序, 其安装过程与在移动终端上安装应用程序的过程一致, 并不受插件来源的约束。
在现有技术安装浏览器插件的过程中, 对该浏览器插件的来源及其合法性未加以控制, 使得当移动终端安装了该浏览器插件后, 该浏览器插件能够随意访问移动终端的 API,无法 对其运行过程中进行控制, 而一旦该浏览器插件为有害浏览器插件, 则无法避免其对移动 终端 API的随意调用, 无法保障移动终端用户的利益及隐私。 发明内容
为了解决现有技术的问题, 本发明实施例提供了一种浏览器插件安装方法、 装置及终 端。 所述技术方案如下:
第一方面, 提供了一种浏览器插件安装方法, 所述方法包括:
接收对浏览器插件的安装指令, 所述浏览器插件应用于指定浏览器;
根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器信息, 判断所述浏览 器插件是否合法, 如果是, 则安装所述浏览器插件, 如果否, 则拒绝安装所述浏览器插件。
进一步地, 所述根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器信息, 判断所述浏览器插件是否合法, 包括:
根据所述浏览器信息验证所述浏览器插件的数字签名信息, 当所述浏览器信息与数字
签名信息匹配, 则所述浏览器插件合法, 否则, 所述浏览器插件不合法。
进一步地, 所述根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器信息, 判断所述浏览器插件是否合法, 之前包括:
显示所述浏览器插件声明的应用程序接口;
根据接收到的操作指令继续或不继续安装过程。
进一步地, 所述显示所述浏览器插件声明的应用程序接口, 包括:
显示所述浏览器插件声明的应用程序接口, 并显示各个所述应用程序接口的敏感级别。 进一步地, 所述浏览器插件携带数字签名信息, 所述数字签名信息由所述指定浏览器 的服务器对所述浏览器插件进行数字签名获得。
第二方面, 提供了一种浏览器插件处理方法, 所述方法包括:
接收浏览器插件;
根据所述浏览器插件调用的指定浏览器的应用程序接口对所述浏览器插件进行处理。 所述根据所述浏览器插件调用的指定浏览器的应用程序接口对所述浏览器插件进行处 理, 包括:
判断所述浏览器插件调用的指定浏览器的应用程序接口与所述浏览器插件声明的应用 程序接口是否相符,
如果是, 则对所述浏览器插件进行数字签名, 并将得到的数字签名信息打包至所述浏 览器插件;
如果否, 不对所述浏览器插件进行处理。
第三方面, 提供了一种浏览器插件安装装置, 所述装置包括:
第一接收模块, 用于接收对浏览器插件的安装指令, 所述浏览器插件应用于指定浏览 器;
判断模块, 用于根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器信息, 判断所述浏览器插件是否合法;
安装模块, 用于当所述判断模块确定所述浏览器插件合法时, 安装所述浏览器插件; 所述安装模块, 还用于当所述判断模块确定所述浏览器插件不合法时, 拒绝安装所述 浏览器插件。
进一步地, 所述判断模块具体用于根据所述浏览器信息验证所述浏览器插件的数字签 名信息, 当所述浏览器信息与数字签名信息匹配, 则所述浏览器插件合法, 否则, 所述浏 览器插件不合法。
进一步地, 所述装置还包括:
显示模块, 用于显示所述浏览器插件声明的应用程序接口;
相应地, 所述安装模块, 用于根据接收到的操作指令继续或不继续安装过程。
进一步地, 所述显示模块具体用于显示所述浏览器插件声明的应用程序接口, 并显示 各个所述应用程序接口的敏感级别。
进一步地, 所述浏览器插件携带数字签名信息, 所述数字签名信息由所述指定浏览器 的服务器对所述浏览器插件进行数字签名获得。
第四方面, 提供了一种浏览器插件处理装置, 所述装置包括:
第二接收模块, 用于接收浏览器插件;
处理模块, 用于根据所述浏览器插件调用的指定浏览器的应用程序接口对所述浏览器 插件进行处理。
进一步地, 所述处理模块包括:
判断单元, 用于判断所述浏览器插件调用的指定浏览器的应用程序接口与所述浏览器 插件声明的应用程序接口是否相符,
处理单元, 用于当所述浏览器插件调用的指定浏览器的应用程序接口与所述浏览器插 件声明的应用程序接口相符, 对所述浏览器插件进行数字签名, 并将得到的数字签名信息 打包至所述浏览器插件;
所述处理单元, 还用于当所述浏览器插件调用的指定浏览器的应用程序接口与所述浏 览器插件声明的应用程序接口不相符, 不对所述浏览器插件进行处理。
本发明实施例提供的技术方案带来的有益效果是:
通过接收对浏览器插件的安装指令, 所述浏览器插件应用于指定浏览器; 根据所述浏 览器插件的数字签名信息和所述指定浏览器的浏览器信息, 判断所述浏览器插件是否合法, 如果是, 则安装所述浏览器插件, 如果否, 则拒绝安装所述浏览器插件。 采用本发明提供 的技术方案, 通过在安装起始时, 根据浏览器插件的数字签名信息和其对应的指定浏览器 的浏览器信息对该浏览器插件进行验证, 以确定该浏览器插件的合法性和可追溯性, 避免 了有害浏览器插件对移动终端 API的随意调用, 提高了移动终端的安全性。 附图说明
为了更清楚地说明本发明实施例中的技术方案, 下面将对实施例描述中所需要使用的 附图作简单地介绍, 显而易见地, 下面描述中的附图仅仅是本发明的一些实施例, 对于本 领域普通技术人员来讲, 在不付出创造性劳动的前提下, 还可以根据这些附图获得其他的 附图。
图 1是本发明实施例提供的一种浏览器插件安装方法的流程图;
图 2是本发明实施例提供的一种浏览器插件安装方法的流程图;
图 3是本发明实施例提供的一种浏览器插件处理方法的流程图;
图 4是本发明实施例提供的一种浏览器插件安装装置的结构示意图;
图 5是本发明实施例提供的一种浏览器插件处理装置的结构示意图;
图 6是本发明实施例提供的一种终端的结构示意图。 具体实施方式
为使本发明的目的、 技术方案和优点更加清楚, 下面将结合附图对本发明实施方式作 进一步地详细描述。
图 1 是本发明实施例提供的一种浏览器插件安装方法的流程图。 该实施例的执行主体 为移动终端, 参见图 1, 该实施例具体包括:
101、 接收对浏览器插件的安装指令, 所述浏览器插件应用于指定浏览器;
102、 根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器信息, 判断所述 浏览器插件是否合法, 如果是, 执行步骤 103; 如果否, 执行步骤 104;
103、 安装所述浏览器插件;
104、 拒绝安装所述浏览器插件。
可选地, 根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器信息, 判断 所述浏览器插件是否合法, 包括但不限于:
根据所述浏览器信息验证所述浏览器插件的数字签名信息, 当所述浏览器信息与数字 签名信息匹配, 则所述浏览器插件合法, 否则, 所述浏览器插件不合法。
可选地, 根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器信息, 判断 所述浏览器插件是否合法, 之前包括:
显示所述浏览器插件声明的应用程序接口;
根据接收到的操作指令继续或不继续安装过程。
可选地, 显示所述浏览器插件声明的应用程序接口, 包括但不限于:
显示所述浏览器插件声明的应用程序接口, 并显示各个所述应用程序接口的敏感级别。 可选地, 浏览器插件携带数字签名信息, 所述数字签名信息由所述指定浏览器的服务 器对所述浏览器插件进行数字签名获得。
本实施例提供的方法, 通过接收对浏览器插件的安装指令, 所述浏览器插件应用于指 定浏览器; 根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器信息, 判断所
述浏览器插件是否合法, 如果是, 则安装所述浏览器插件, 如果否, 则拒绝安装所述浏览 器插件。 采用本发明提供的技术方案, 通过在安装起始时, 根据浏览器插件的数字签名信 息和其对应的指定浏览器的浏览器信息对该浏览器插件进行验证, 以确定该浏览器插件的 合法性和可追溯性, 避免了有害浏览器插件对移动终端 API的随意调用, 提高了移动终端 的安全性。 图 2是本发明实施例提供的一种浏览器插件处理方法的流程图。 该实施例的执行主体 为服务器, 参见图 2, 该实施例具体包括:
201、 接收浏览器插件;
202、 根据所述浏览器插件调用的指定浏览器的应用程序接口对所述浏览器插件进行处 理。
可选的, 根据所述浏览器插件调用的指定浏览器的应用程序接口对所述浏览器插件进 行处理, 包括但不限于:
判断所述浏览器插件调用的指定浏览器的应用程序接口与所述浏览器插件声明的应用 程序接口是否相符,
如果是, 则对所述浏览器插件进行数字签名, 并将得到的数字签名信息打包至所述浏 览器插件;
如果否, 不对所述浏览器插件进行处理。
本实施例提供的方法, 通过判断接收到的浏览器插件声明的 API 以及实际调用的 API 是否相符, 以判断该浏览器插件是否有潜在的威胁, 确定该浏览器插件的合法性和可追溯 性, 避免了有害浏览器插件对移动终端 API的随意调用, 提高了移动终端的安全性。 图 3 是本发明实施例提供的一种浏览器插件安装方法的流程图。 该实施例仅以移动终 端和服务器对浏览器插件进行的处理为例进行说明, 参见图 3, 该实施例具体包括:
301、 服务器接收浏览器插件;
本实施例中的浏览器插件是指开发人员开发出的能够安装并运行于指定浏览器上的插 件。 该浏览器插件的功能可以有多种, 本实施例不做具体限定, 其具体工作过程可以包括: 在指定浏览器运行过程中,调用浏览器插件所指定的移动终端 API,直接访问移动终端 API, 以通过移动终端 API获取相应文件。 其中, API是预先定义的一些函数, 目的是提供应用 程序与开发人员基于某软件或硬件的以访问一组例程的能力, 当应用程序或插件调用某个 API时, 移动终端访问相应 API, 例如: 当浏览器需要使用移动终端的通讯录时, 浏览器向
移动终端发送调用通讯录 API指令, 移动终端接收该调用指令并调用通讯录 API, 则浏览 器访问通讯录 API, 以获取通讯录相应文件。
在该步骤中, 开发人员或者移动终端用户将开发的该浏览器插件上传至指定浏览器的 服务器, 从而该服务器接收该浏览器插件, 需要说明的是, 该上传可以是上传浏览器插件 的压縮包, 也可以上传浏览器插件本身, 在此不做具体限定。
302、服务器判断浏览器插件调用的指定浏览器的 API与浏览器插件声明的 API是否相 符;
如果是, 执行步骤 303;
如果否, 结束。
在该实施例中, 对于各个浏览器插件来说, 每个浏览器插件均包括技术研发人员对插 件的声明, 该声明包括该浏览器插件所要调用的 API名称, 声明可以为列表形式。 如, 浏 览器插件 A的声明中包括 API1、 API2和 API3, 则可以理解为该浏览器插件 A在运行时需 调用 API1、 API2和 API3。
而为了确认该浏览器插件是否安全, 服务器接收到该浏览器插件后, 检测该浏览器插 件实际调用的指定浏览器的 API, 若该浏览器插件调用的指定浏览器的 API与浏览器插件 声明的 API相符, 则执行步骤 303; 若不相符, 则不对该浏览器插件进行任何处理。
303、 当浏览器插件调用的指定浏览器的 API与浏览器插件声明的 API相符, 则服务器 对所述浏览器插件进行数字签名, 并将得到的数字签名信息打包至所述浏览器插件;
在该步骤 303 中, 在进行数字签名时, 可根据加密方法不同分为以下两种: (1 ) 当加 密方法为对称密钥加密时, 也即是发送和接收数据的双方必须使用相同的 /对称的密钥对明 文进行加密和解密运算, 则服务器使用服务器的密钥对浏览器插件进行数字签名, 并将得 到的数字签名信息打包至所述浏览器插件; (2) 当加密方法为非对称密钥加密, 服务器与 该指定浏览器客户端具有相应的公钥和私钥, 服务器使用私钥对浏览器插件进行数字签名, 而指定浏览器客户端持有相应的公钥, 则当浏览器插件在指定浏览器上进行安装时, 可用 相应的公钥对该浏览器插件进行验证, 以确定该浏览器插件的安全性。
服务器对浏览器插件进行数字签名的过程为: 用一个哈希函数从该浏览器插件的报 文文本中生成报文摘要, 服务器使用自身公钥所对应的私钥对该报文摘要进行加密处理, 加密的摘要即为浏览器插件的数字签名信息, 从而完成数字签名过程。上述步骤 301-303 是服务器对浏览器插件进行验证并进行数字签名的过程, 数字签名过程表明了服务器对该 浏览器插件的认可, 为移动终端提供了用于验证浏览器插件合法性的依据。
304、 移动终端下载浏览器插件;
需要说明的是, 服务器在对浏览器插件进行数字签名后, 可将携带数字签名信息的浏 览器插件保存, 并开放给用户进行下载。 移动终端可以从服务器直接下载浏览器插件, 还 可以从网络上下载浏览器插件, 本发明实施例对浏览器插件的来源不做限定。
305、 移动终端接收对浏览器插件的安装指令;
当移动终端用户需要安装该浏览器插件时, 通过键盘或滑屏手势等触发对浏览器插件 的安装指令, 移动终端接收到该安装指令时, 开始安装过程。
306、 移动终端界面显示浏览器插件声明的 API及 API的敏感级别;
其中, API的敏感级别是在浏览器插件开发过程中, 由技术研发人员根据 API的具体 功能设定的。 API的敏感级别可以分为两级, 如: 用数字 " 1 "和 "0"表示。 其中, 敏感级 别的 API用 " 1 "表示, 非敏感级别的 API用 "0"表示。 当被调用的 API及其敏感级别在 移动终端界面显示时, 根据技术研发人员的预先设定, 显示为 API+敏感级别, 如: 通讯录 API+ " 1 ", 系统文件 API+ "0", 表明该通讯录 API为敏感 API, 系统文件 API为非敏感 API。 API的敏感级别根据技术研发人员的设定还可以分为其他等级, 本实施例在此不做具 体限定。
通过在显示 API的同时, 显示其敏感级别, 可以便于移动终端用户对该浏览器插件所 调用的 API有初步的认识, 当该浏览器插件调用的 API为敏感 API时, 移动终端用户可根 据自身的安全性需求继续或不继续当前安装。
307、 当移动终端接收到继续安装的操作指令时, 根据浏览器插件的数字签名信息和指 定浏览器的浏览器信息, 判断所述浏览器插件是否合法;
如果是, 执行步骤 308;
如果否, 执行步骤 309;
相应地, 在移动终端界面还会显示操作指令, 该操作指令用于提示用户是否安装该浏 览器插件。 如: 在显示界面左下方和右下方显示: "安装"和 "取消", 移动终端上的左右 功能键分别控制这两个操作, 移动终端用户根据界面显示的声明 API及其敏感级别, 确定 是否安装该浏览器插件。 当移动终端接收到继续安装的操作指令时, 不继续安装过程。
在本实施例中, 浏览器信息具体为该指定浏览器的公钥, 该公钥与服务器对浏览器插 件进行数字签名时所使用的私钥相对应, 则移动终端根据该指定浏览器的公钥验证浏览器 插件的数字签名信息, 当所述浏览器信息与数字签名信息匹配, 则所述浏览器插件合法, 否则, 所述浏览器插件不合法。 其具体验证过程有为现有技术, 在此不再赘述。
308、 安装浏览器插件;
在移动终端中安装该浏览器插件的过程与应用程序安装过程类似, 在此不再赘述。
309、 拒绝安装浏览器插件。
本实施例提供的方法, 通过接收对浏览器插件的安装指令, 所述浏览器插件应用于指 定浏览器; 根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器信息, 判断所 述浏览器插件是否合法, 如果是, 则安装所述浏览器插件, 如果否, 则拒绝安装所述浏览 器插件。 采用本发明提供的技术方案, 通过在安装起始时, 根据浏览器插件的数字签名信 息和其对应的指定浏览器的浏览器信息对该浏览器插件进行验证, 以确定该浏览器插件的 合法性和可追溯性, 避免了有害浏览器插件对移动终端 API的随意调用, 提高了移动终端 的安全性。 图 4是本发明实施例提供的一种浏览器插件安装装置的结构示意图。 该装置可位于终 端设备, 该终端设备可以为移动终端或固定终端, 移动终端具体可以为智能手机、 笔记本 电脑或其他移动设备, 固定终端可以为个人计算机等。 参见图 4, 该装置包括:
第一接收模块 401, 用于接收对浏览器插件的安装指令, 所述浏览器插件应用于指定浏 判断模块 402,用于根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器信 息, 判断所述浏览器插件是否合法;
安装模块 403,用于当所述判断模块确定所述浏览器插件合法时,安装所述浏览器插件; 所述安装模块 403, 还用于当所述判断模块确定所述浏览器插件不合法时, 拒绝安装所 述浏览器插件。
可选地, 所述判断模块 402具体用于根据所述浏览器信息验证所述浏览器插件的数字 签名信息, 当所述浏览器信息与数字签名信息匹配, 则所述浏览器插件合法, 否则, 所述 浏览器插件不合法。
可选地, 所述装置还包括:
显示模块 404, 用于显示所述浏览器插件声明的应用程序接口;
相应地, 所述安装模块 403, 用于根据接收到的操作指令继续或不继续安装过程。 可选地,
所述显示模块 404具体用于显示所述浏览器插件声明的应用程序接口, 并显示各个所 述应用程序接口的敏感级别。
可选地, 浏览器插件携带数字签名信息, 所述数字签名信息由所述指定浏览器的服务 器对所述浏览器插件进行数字签名获得。
需要说明的是: 上述实施例提供的安装浏览器插件的装置在安装浏览器插件时, 仅以
上述各功能模块的划分进行举例说明, 实际应用中, 可以根据需要而将上述功能分配由不 同的功能模块完成, 即将装置的内部结构划分成不同的功能模块, 以完成以上描述的全部 或者部分功能。 另外, 上述实施例提供的安装浏览器插件的方法和安装浏览器插件的装置 实施例属于同一构思, 其具体实现过程详见方法实施例, 这里不再赘述。
本实施例提供的装置, 通过接收对浏览器插件的安装指令, 所述浏览器插件应用于指 定浏览器; 根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器信息, 判断所 述浏览器插件是否合法, 如果是, 则安装所述浏览器插件, 如果否, 则拒绝安装所述浏览 器插件。 采用本发明提供的技术方案, 通过在安装起始时, 根据浏览器插件的数字签名信 息和其对应的指定浏览器的浏览器信息对该浏览器插件进行验证, 以确定该浏览器插件的 合法性和可追溯性, 避免了有害浏览器插件对移动终端 API的随意调用, 提高了移动终端 的安全性。 图 5 是本发明实施例提供的一种浏览器插件处理装置的结构示意图。 该装置位于服务 于指定浏览器的服务器端, 参见图 5, 该装置包括:
第二接收模块 501, 用于接收浏览器插件;
处理模块 502,用于根据所述浏览器插件调用的指定浏览器的应用程序接口对所述浏览 器插件进行处理。
可选地, 所述处理模块 502包括:
判断单元, 用于判断所述浏览器插件调用的指定浏览器的应用程序接口与所述浏览器 插件声明的应用程序接口是否相符,
处理单元, 用于当所述浏览器插件调用的指定浏览器的应用程序接口与所述浏览器插 件声明的应用程序接口相符, 对所述浏览器插件进行数字签名, 并将得到的数字签名信息 打包至所述浏览器插件;
所述处理单元, 还用于当所述浏览器插件调用的指定浏览器的应用程序接口与所述浏 览器插件声明的应用程序接口不相符, 不对所述浏览器插件进行处理。
本实施例提供的装置, 通过判断接收到的浏览器插件声明的 API 以及实际调用的 API 是否相符, 以判断该浏览器插件是否有潜在的威胁, 确定该浏览器插件的合法性和可追溯 性, 避免了有害浏览器插件对移动终端 API的随意调用, 提高了移动终端的安全性。 图 6 是本发明实施例提供的一种终端的结构示意图, 其示出了本发明实施例所涉及的 具有触敏表面的结构示意图, 该终端可以用于实施上述实施例中提供的浏览器插件安装的
方法。 具体来讲:
终端 600可以包括 RF ( Radio Frequency, 射频) 电路 110、 包括有一个或一个以上计 算机可读存储介质的存储器 120、输入单元 130、显示单元 140、传感器 150、音频电路 160、 传输模块 170、 包括有一个或者一个以上处理核心的处理器 180、 以及电源 190等部件。 本 领域技术人员可以理解, 图 6 中示出的终端结构并不构成对终端的限定, 可以包括比图示 更多或更少的部件, 或者组合某些部件, 或者不同的部件布置。 其中:
RF电路 110可用于收发信息或通话过程中, 信号的接收和发送, 特别地, 将基站的下 行信息接收后, 交由一个或者一个以上处理器 180 处理; 另外, 将涉及上行的数据发送给 基站。 通常, RF电路 110包括但不限于天线、 至少一个放大器、 调谐器、 一个或多个振荡 器、 用户身份模块 (SIM) 卡、 收发信机、 耦合器、 LNA ( Low Noi se Ampl ifier, 低噪声放 大器)、 双工器等。 此外, RF电路 110还可以通过无线通信与网络和其他设备通信。 所述无 线通信可以使用任一通信标准或协议, 包括但不限于 GSM (Global System of Mob i le communicat ion, 全球移动通讯系统)、 GPRS (General Packet Radio Service , 通用分组无 线服务) CDMA (Code Divi s ion Mult iple Access ,码分多址) WCDMA (Wideband Code Divi s ion Mult iple Access, 宽带码分多址)、 LTE (Long Term Evolut ion,长期演进)、 电子邮件、 SMS (Short Messaging Service , 短消息服务)等。
存储器 120 可用于存储软件程序以及模块, 如实施例三中提高应用程序运行速度的装 置所对应的软件程序以及模块, 处理器 180通过运行存储在存储器 120的软件程序以及模 块, 从而执行各种功能应用以及数据处理, 如实现应用程序运行速度的提高等。 存储器 120 可主要包括存储程序区和存储数据区, 其中, 存储程序区可存储操作系统、 至少一个功能 所需的应用程序 (比如声音播放功能、 图像播放功能等) 等; 存储数据区可存储根据终端 600的使用所创建的数据 (比如音频数据、 电话本等)等。 此外, 存储器 120可以包括高速 随机存取存储器, 还可以包括非易失性存储器, 例如至少一个磁盘存储器件、 闪存器件、 或其他易失性固态存储器件。 相应地, 存储器 120还可以包括存储器控制器, 以提供处理 器 180和输入单元 130对存储器 120的访问。
输入单元 130 可用于接收输入的数字或字符信息, 以及产生与用户设置以及功能控制 有关的键盘、 鼠标、 操作杆、 光学或者轨迹球信号输入。 具体地, 输入单元 130 可包括触 敏表面 131以及其他输入设备 132。 触敏表面 131, 也称为触摸显示屏或者触控板, 可收集 用户在其上或附近的触摸操作 (比如用户使用手指、 触笔等任何适合的物体或附件在触敏 表面 131上或在触敏表面 131附近的操作), 并根据预先设定的程式驱动相应的连接装置。 可选的, 触敏表面 131 可包括触摸检测装置和触摸控制器两个部分。 其中, 触摸检测装置
检测用户的触摸方位, 并检测触摸操作带来的信号, 将信号传送给触摸控制器; 触摸控制 器从触摸检测装置上接收触摸信息, 并将它转换成触点坐标, 再送给处理器 180, 并能接收 处理器 180发来的命令并加以执行。 此外, 可以采用电阻式、 电容式、 红外线以及表面声 波等多种类型实现触敏表面 131。 除了触敏表面 131, 输入单元 130还可以包括其他输入设 备 132。 具体地, 其他输入设备 132可以包括但不限于物理键盘、 功能键(比如音量控制按 键、 开关按键等)、 轨迹球、 鼠标、 操作杆等中的一种或多种。
显示单元 140可用于显示由用户输入的信息或提供给用户的信息以及终端 600的各种 图形用户接口, 这些图形用户接口可以由图形、 文本、 图标、 视频和其任意组合来构成。 显示单元 140可包括显示面板 141, 可选的, 可以采用 LCD (Liquid Crystal Display, 液 晶显示器)、 OLED (Organic Light-Emitting Diode,有机发光二极管)等形式来配置显示面 板 141。 进一步的, 触敏表面 131可覆盖显示面板 141, 当触敏表面 131检测到在其上或附 近的触摸操作后, 传送给处理器 180以确定触摸事件的类型, 随后处理器 180根据触摸事 件的类型在显示面板 141上提供相应的视觉输出。 虽然在图 6中, 触敏表面 131与显示面 板 141 是作为两个独立的部件来实现输入和输入功能, 但是在某些实施例中, 可以将触敏 表面 131与显示面板 141集成而实现输入和输出功能。
终端 600还可包括至少一种传感器 150, 比如光传感器、 运动传感器以及其他传感器。 具体地, 光传感器可包括环境光传感器及接近传感器, 其中, 环境光传感器可根据环境光 线的明暗来调节显示面板 141 的亮度, 接近传感器可在终端 600移动到耳边时, 关闭显示 面板 141和 /或背光。 作为运动传感器的一种, 重力加速度传感器可检测各个方向上 (一般 为三轴) 加速度的大小, 静止时可检测出重力的大小及方向, 可用于识别手机姿态的应用 (比如横竖屏切换、 相关游戏、磁力计姿态校准)、 振动识别相关功能(比如计步器、 敲击) 等; 至于终端 600还可配置的陀螺仪、 气压计、 湿度计、 温度计、 红外线传感器等其他传 感器, 在此不再赘述。
音频电路 160、 扬声器 161, 传声器 162可提供用户与终端 600之间的音频接口。 音频 电路 160可将接收到的音频数据转换后的电信号, 传输到扬声器 161, 由扬声器 161转换为 声音信号输出; 另一方面, 传声器 162 将收集的声音信号转换为电信号, 由音频电路 160 接收后转换为音频数据, 再将音频数据输出处理器 180处理后, 经 RF电路 110以发送给比 如另一终端, 或者将音频数据输出至存储器 120以便进一步处理。 音频电路 160还可能包 括耳塞插孔, 以提供外设耳机与终端 600的通信。
终端 600通过传输模块 170可以帮助用户收发电子邮件、 浏览网页和访问流式媒体等, 它为用户提供了无线或有线的宽带互联网访问。虽然图 6示出了传输模块 170, 但是可以理
解的是, 其并不属于终端 600 的必须构成, 完全可以根据需要在不改变发明的本质的范围 内而省略。
处理器 180是终端 600的控制中心, 利用各种接口和线路连接整个手机的各个部分, 通过运行或执行存储在存储器 120内的软件程序和 /或模块, 以及调用存储在存储器 120内 的数据, 执行终端 600 的各种功能和处理数据, 从而对手机进行整体监控。 可选的, 处理 器 180可包括一个或多个处理核心; 优选的, 处理器 180可集成应用处理器和调制解调处 理器, 其中, 应用处理器主要处理操作系统、 用户界面和应用程序等, 调制解调处理器主 要处理无线通信。 可以理解的是, 上述调制解调处理器也可以不集成到处理器 180中。
终端 600还包括给各个部件供电的电源 190 (比如电池), 优选的, 电源可以通过电源 管理系统与处理器 180逻辑相连, 从而通过电源管理系统实现管理充电、 放电、 以及功耗 管理等功能。 电源 190还可以包括一个或一个以上的直流或交流电源、 再充电系统、 电源 故障检测电路、 电源转换器或者逆变器、 电源状态指示器等任意组件。
尽管未示出, 终端 600还可以包括摄像头、 蓝牙模块等, 在此不再赘述。 具体在本实 施例中, 终端的显示单元是触摸屏显示器, 终端还包括有存储器, 以及一个或者一个以上 的程序, 其中一个或者一个以上程序存储于存储器中, 且经配置以由一个或者一个以上处 理器执行述一个或者一个以上程序包含用于进行以下操作的指令:
接收对浏览器插件的安装指令, 所述浏览器插件应用于指定浏览器;
根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器信息, 判断所述浏览 器插件是否合法, 如果是, 则安装所述浏览器插件, 如果否, 则拒绝安装所述浏览器插件。
假设上述为第一种可能的实施方式, 则在第一种可能的实施方式作为基础而提供的第 二种可能的实施方式中, 所述终端的存储器中, 还包含用于执行以下操作的指令:
根据所述浏览器信息验证所述浏览器插件的数字签名信息, 当所述浏览器信息与数字 签名信息匹配, 则所述浏览器插件合法, 否则, 所述浏览器插件不合法。
在第一种可能的实施方式作为基础而提供的第三种可能的实施方式中, 所述终端的存 储器中, 还包含用于执行以下操作的指令:
显示所述浏览器插件声明的应用程序接口;
根据接收到的操作指令继续或不继续安装过程。
在第三种可能的实施方式作为基础而提供的第四种可能的实施方式中, 所述终端的存 储器中, 还包含用于执行以下操作的指令:
显示所述浏览器插件声明的应用程序接口, 并显示各个所述应用程序接口的敏感级别。 在第一、 第二、 第三或者第四种可能的实施方式作为基础而提供的第五种可能的实施
方式中, 所述终端的存储器中, 还包含用于执行以下操作的指令:
浏览器插件携带数字签名信息, 所述数字签名信息由所述指定浏览器的服务器对所述 浏览器插件进行数字签名获得。
综上所述, 本实施例提供的终端, 通过判断接收到的浏览器插件声明的 API 以及实际 调用的 API是否相符, 以判断该浏览器插件是否有潜在的威胁, 确定该浏览器插件的合法 性和可追溯性, 避免了有害浏览器插件对移动终端 API的随意调用, 提高了移动终端的安 全性。 本发明实施例提供了一种计算机可读存储介质, 该计算机可读存储介质可以是上述实 施例中的存储器中所包含的计算机可读存储介质; 也可以是单独存在, 未装配入终端中的 计算机可读存储介质。 所述计算机可读存储介质存储有一个或者一个以上程序, 所述一个 或者一个以上程序被一个或者一个以上的处理器用来执行一个滑动控制方法, 所述方法包 括:
接收对浏览器插件的安装指令, 所述浏览器插件应用于指定浏览器;
根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器信息, 判断所述浏览 器插件是否合法, 如果是, 则安装所述浏览器插件, 如果否, 则拒绝安装所述浏览器插件。
假设上述为第一种可能的实施方式, 则在第一种可能的实施方式作为基础而提供的第 二种可能的实施方式中, 根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器 信息, 判断所述浏览器插件是否合法, 包括:
根据所述浏览器信息验证所述浏览器插件的数字签名信息, 当所述浏览器信息与数字 签名信息匹配, 则所述浏览器插件合法, 否则, 所述浏览器插件不合法。
在第一种可能的实施方式作为基础而提供的第三种可能的实施方式中, 根据所述浏览 器插件的数字签名信息和所述指定浏览器的浏览器信息, 判断所述浏览器插件是否合法, 之前包括:
显示所述浏览器插件声明的应用程序接口;
根据接收到的操作指令继续或不继续安装过程。
在第三种可能的实施方式作为基础而提供的第四种可能的实施方式中, 显示所述浏览 器插件声明的应用程序接口, 包括:
显示所述浏览器插件声明的应用程序接口, 并显示各个所述应用程序接口的敏感级别。 在第一、 第二、 第三或者第四种可能的实施方式作为基础而提供的第五种可能的实施 方式中, 浏览器插件携带数字签名信息, 所述数字签名信息由所述指定浏览器的服务器对
所述浏览器插件进行数字签名获得。
本发明实施例提供的计算机可读存储介质, 通过判断接收到的浏览器插件声明的 API 以及实际调用的 API是否相符, 以判断该浏览器插件是否有潜在的威胁, 确定该浏览器插 件的合法性和可追溯性, 避免了有害浏览器插件对移动终端 API的随意调用, 提高了移动 终端的安全性。 本发明实施例中提供了一种图形用户接口, 所述图形用户接口用在终端上, 所述终端 包括触摸屏显示器、 存储器和用于执行一个或者一个以上的程序的一个或者一个以上的处 理器; 所述图形用户接口包括:
在所述触摸屏显示器上显示浏览器插件的安装指令, 所述浏览器插件应用于指定浏览 器;
根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器信息, 判断所述浏览 器插件是否合法, 如果是, 则安装所述浏览器插件, 如果否, 则拒绝安装所述浏览器插件。
本发明实施例提供的图形用户接口, 通过判断接收到的浏览器插件声明的 API 以及实 际调用的 API是否相符, 以判断该浏览器插件是否有潜在的威胁, 确定该浏览器插件的合 法性和可追溯性, 避免了有害浏览器插件对移动终端 API的随意调用, 提高了移动终端的 安全性。 需要说明的是: 上述实施例提供的浏览器插件安装的装置在安装插件时, 仅以上述各 功能模块的划分进行举例说明, 实际应用中, 可以根据需要而将上述功能分配由不同的功 能模块完成, 即将装置的内部结构划分成不同的功能模块, 以完成以上描述的全部或者部 分功能。 另外, 上述实施例提供的浏览器插件安装的装置与浏览器插件安装的方法实施例 属于同一构思, 其具体实现过程详见方法实施例, 这里不再赘述。
上述本发明实施例序号仅仅为了描述, 不代表实施例的优劣。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完 成, 也可以通过程序来指令相关的硬件完成, 所述的程序可以存储于一种计算机可读存储 介质中, 上述提到的存储介质可以是只读存储器, 磁盘或光盘等。
以上所述仅为本发明的较佳实施例, 并不用以限制本发明, 凡在本发明的精神和原则 之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明的保护范围之内。
Claims
1、 一种浏览器插件安装方法, 其特征在于, 所述方法包括:
接收对浏览器插件的安装指令, 所述浏览器插件应用于指定浏览器;
根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器信息, 判断所述浏览器 插件是否合法, 如果是, 则安装所述浏览器插件, 如果否, 则拒绝安装所述浏览器插件。
2、根据权利要求 1所述的方法, 其特征在于, 所述根据所述浏览器插件的数字签名信息 和所述指定浏览器的浏览器信息, 判断所述浏览器插件是否合法, 包括:
根据所述浏览器信息验证所述浏览器插件的数字签名信息, 当所述浏览器信息与数字签 名信息匹配, 则所述浏览器插件合法, 否则, 所述浏览器插件不合法。
3、根据权利要求 1所述的方法, 其特征在于, 所述根据所述浏览器插件的数字签名信息 和所述指定浏览器的浏览器信息, 判断所述浏览器插件是否合法, 之前包括:
显示所述浏览器插件声明的应用程序接口;
根据接收到的操作指令继续或不继续安装过程。
4、根据权利要求 3所述的方法, 其特征在于, 所述显示所述浏览器插件声明的应用程序 接口, 包括:
显示所述浏览器插件声明的应用程序接口, 并显示各个所述应用程序接口的敏感级别。
5、 根据权利要求 1-4任一项所述的方法, 其特征在于, 所述浏览器插件携带数字签名信 息, 所述数字签名信息由所述指定浏览器的服务器对所述浏览器插件进行数字签名获得。
6、 一种浏览器插件处理方法, 其特征在于, 包括:
接收浏览器插件;
根据所述浏览器插件调用的指定浏览器的应用程序接口对所述浏览器插件进行处理。
7、根据权利要求 6所述的方法, 其特征在于, 根据所述浏览器插件调用的指定浏览器的 应用程序接口对所述浏览器插件进行处理, 包括:
判断所述浏览器插件调用的指定浏览器的应用程序接口与所述浏览器插件声明的应用程
序接口是否相符,
如果是, 则对所述浏览器插件进行数字签名, 并将得到的数字签名信息打包至所述浏览 器插件;
如果否, 不对所述浏览器插件进行处理。
8、 一种浏览器插件安装装置, 其特征在于, 所述装置包括:
第一接收模块, 用于接收对浏览器插件的安装指令, 所述浏览器插件应用于指定浏览器; 判断模块, 用于根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器信息, 判断所述浏览器插件是否合法;
安装模块, 用于当所述判断模块确定所述浏览器插件合法时, 安装所述浏览器插件; 所述安装模块, 还用于当所述判断模块确定所述浏览器插件不合法时, 拒绝安装所述浏 览器插件。
9、根据权利要求 8所述的装置, 其特征在于, 所述判断模块具体用于根据所述浏览器信 息验证所述浏览器插件的数字签名信息, 当所述浏览器信息与数字签名信息匹配, 则所述浏 览器插件合法, 否则, 所述浏览器插件不合法。
10、 根据权利要求 8所述的装置, 其特征在于, 所述装置还包括:
显示模块, 用于显示所述浏览器插件声明的应用程序接口;
相应地, 所述安装模块, 用于根据接收到的操作指令继续或不继续安装过程。
11、 根据权利要求 8所述的装置, 其特征在于,
所述显示模块具体用于显示所述浏览器插件声明的应用程序接口, 并显示各个所述应用 程序接口的敏感级别。
12、 根据权利要求 8-11任一项所述的装置, 其特征在于, 所述浏览器插件携带数字签名 信息, 所述数字签名信息由所述指定浏览器的服务器对所述浏览器插件进行数字签名获得。
13、 一种浏览器插件处理装置, 其特征在于, 所述装置包括:
第二接收模块, 用于接收浏览器插件;
处理模块, 用于根据所述浏览器插件调用的指定浏览器的应用程序接口对所述浏览器插
件进行处理。
14、 根据权利要求 13所述的装置, 其特征在于, 所述处理模块包括:
判断单元, 用于判断所述浏览器插件调用的指定浏览器的应用程序接口与所述浏览器插 件声明的应用程序接口是否相符,
处理单元, 用于当所述浏览器插件调用的指定浏览器的应用程序接口与所述浏览器插件 声明的应用程序接口相符, 对所述浏览器插件进行数字签名, 并将得到的数字签名信息打包 至所述浏览器插件;
所述处理单元, 还用于当所述浏览器插件调用的指定浏览器的应用程序接口与所述浏览 器插件声明的应用程序接口不相符, 不对所述浏览器插件进行处理。
15、 一种终端, 其特征在于, 所述终端包括: 触摸屏显示器、 一个或者一个以上的处理 器; 存储器; 以及一个或者一个以上的程序, 其中所述一个或者一个以上程序存储于所述存 储器中, 且经配置以由所述一个或者一个以上处理器执行, 所述一个或者一个以上程序包含 用于进行以下操作的指令:
接收对浏览器插件的安装指令, 所述浏览器插件应用于指定浏览器;
根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器信息, 判断所述浏览器 插件是否合法, 如果是, 则安装所述浏览器插件, 如果否, 则拒绝安装所述浏览器插件。
16、 根据权利要求 15所述的终端, 其特征在于, 包含用于执行以下操作的指令: 根据所述浏览器信息验证所述浏览器插件的数字签名信息, 当所述浏览器信息与数字签 名信息匹配, 则所述浏览器插件合法, 否则, 所述浏览器插件不合法。
17、 根据权利要求 15所述的终端, 其特征在于, 包含用于执行以下操作的指令: 显示所述浏览器插件声明的应用程序接口;
根据接收到的操作指令继续或不继续安装过程。
18、 根据权利要求 17所述的终端, 其特征在于, 包含用于执行以下操作的指令: 显示所述浏览器插件声明的应用程序接口, 并显示各个所述应用程序接口的敏感级别。
19、 根据权利要求 15至 18中任一权利要求所述的终端, 其特征在于, 包含用于执行以
下操作的指令:
浏览器插件携带数字签名信息, 所述数字签名信息由所述指定浏览器的服务器对所述浏 览器插件进行数字签名获得。
20、 一种计算机可读存储介质, 其特征在于, 所述计算机可读存储介质存储有一个或者 一个以上程序, 所述一个或者一个以上程序被一个或者一个以上的处理器用来执行一个滑动 控制方法, 所述方法包括:
接收对浏览器插件的安装指令, 所述浏览器插件应用于指定浏览器;
根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器信息, 判断所述浏览器 插件是否合法, 如果是, 则安装所述浏览器插件, 如果否, 则拒绝安装所述浏览器插件。
21、根据权利要求 20所述的计算机可读存储介质, 其特征在于, 所述根据所述浏览器插 件的数字签名信息和所述指定浏览器的浏览器信息, 判断所述浏览器插件是否合法, 包括: 根据所述浏览器信息验证所述浏览器插件的数字签名信息, 当所述浏览器信息与数字签 名信息匹配, 则所述浏览器插件合法, 否则, 所述浏览器插件不合法。
22、根据权利要求 20所述的计算机可读存储介质, 所述根据所述浏览器插件的数字签名 信息和所述指定浏览器的浏览器信息, 判断所述浏览器插件是否合法, 之前包括:
显示所述浏览器插件声明的应用程序接口;
根据接收到的操作指令继续或不继续安装过程。
23、根据权利要求 22所述的计算机可读存储介质, 其特征在于, 所述显示所述浏览器插 件声明的应用程序接口, 包括:
显示所述浏览器插件声明的应用程序接口, 并显示各个所述应用程序接口的敏感级别。
24、 根据权利要求 20至 23中任一权利要求所述的计算机可读存储介质, 其特征在于, 所述浏览器插件携带数字签名信息, 所述数字签名信息由所述指定浏览器的服务器对所述浏 览器插件进行数字签名获得。
25、 一种图形用户接口, 其特征在于, 所述图形用户接口用在终端上, 所述终端包括触 摸屏显示器、 存储器和用于执行一个或者一个以上的程序的一个或者一个以上的处理器; 所
述图形用户接口包括:
在所述触摸屏显示器上显示浏览器插件的安装指令,所述浏览器插件应用于指定浏览器; 根据所述浏览器插件的数字签名信息和所述指定浏览器的浏览器信息, 判断所述浏览器 插件是否合法, 如果是, 则安装所述浏览器插件, 如果否, 则拒绝安装所述浏览器插件。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/583,133 US20150121083A1 (en) | 2012-06-26 | 2014-12-25 | Method, device, and terminal for installing browser plug-in |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201210214155.6 | 2012-06-26 | ||
CN201210214155.6A CN103514000B (zh) | 2012-06-26 | 2012-06-26 | 浏览器插件安装方法和装置 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/583,133 Continuation US20150121083A1 (en) | 2012-06-26 | 2014-12-25 | Method, device, and terminal for installing browser plug-in |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014000652A1 true WO2014000652A1 (zh) | 2014-01-03 |
Family
ID=49782253
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2013/078056 WO2014000652A1 (zh) | 2012-06-26 | 2013-06-26 | 浏览器插件安装方法、装置及终端 |
Country Status (3)
Country | Link |
---|---|
US (1) | US20150121083A1 (zh) |
CN (1) | CN103514000B (zh) |
WO (1) | WO2014000652A1 (zh) |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9256755B2 (en) * | 2013-12-31 | 2016-02-09 | Google Inc. | Notification of application permissions |
US9280679B2 (en) * | 2013-12-31 | 2016-03-08 | Google Inc. | Tiered application permissions |
CN104965827A (zh) * | 2014-04-25 | 2015-10-07 | 腾讯科技(深圳)有限公司 | 一种插件处理的方法、装置及终端 |
CN104883384B (zh) * | 2015-03-25 | 2018-09-07 | 百度在线网络技术(北京)有限公司 | 一种为轻应用提供客户端的端能力的方法与装置 |
CN105407130A (zh) * | 2015-09-25 | 2016-03-16 | 成都趣点科技有限公司 | 一种移动端插件系统及移动端插件处理方法 |
CN105550276A (zh) * | 2015-12-10 | 2016-05-04 | 广东欧珀移动通信有限公司 | 一种判断网络中音频升级文件完整性的方法及装置 |
US10627988B2 (en) * | 2016-01-14 | 2020-04-21 | Keithley Instruments, Llc | Visually identifiable features for applications installed on electronic devices |
CN105930183A (zh) * | 2016-04-13 | 2016-09-07 | 乐视控股(北京)有限公司 | 一种视频应用程序升级方法和装置 |
CN108243054B (zh) * | 2016-12-27 | 2020-07-07 | 中国移动通信有限公司研究院 | 网关的应用编程接口调用控制方法及装置 |
KR102303665B1 (ko) * | 2017-03-29 | 2021-09-17 | 삼성전자주식회사 | 플러그인 서비스를 포함하는 결제 서비스 제공 방법 및 그 전자장치 |
RU2697951C2 (ru) | 2018-02-06 | 2019-08-21 | Акционерное общество "Лаборатория Касперского" | Система и способ прекращения работы функционально ограниченного приложения, взаимосвязанного с веб-сайтом, запускаемого без установки |
CN108959937A (zh) * | 2018-06-29 | 2018-12-07 | 北京奇虎科技有限公司 | 插件处理方法、装置和设备 |
CN112966269B (zh) * | 2021-03-16 | 2024-05-24 | 北京安天网络安全技术有限公司 | 一种基于浏览器插件的查杀方法和装置 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050240798A1 (en) * | 2004-03-31 | 2005-10-27 | Microsoft Corporation | System and method of preventing a web browser plug-in module from generating a failure |
CN101369930A (zh) * | 2008-09-01 | 2009-02-18 | 深圳市深信服电子科技有限公司 | 一种网络插件的安全检查方法、系统及安全检查设备 |
US20110239288A1 (en) * | 2010-03-24 | 2011-09-29 | Microsoft Corporation | Executable code validation in a web browser |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4727278B2 (ja) * | 2005-04-05 | 2011-07-20 | 株式会社エヌ・ティ・ティ・ドコモ | アプリケーションプログラム検証システム、アプリケーションプログラム検証方法およびコンピュータプログラム |
CN101551753B (zh) * | 2009-04-08 | 2012-04-25 | 腾讯科技(北京)有限公司 | 控制加载插件的装置及方法 |
US8600803B1 (en) * | 2010-05-18 | 2013-12-03 | Google Inc. | Incentivizing behavior to address pricing, tax, and currency issues in an online marketplace for digital goods |
US20120222024A1 (en) * | 2011-02-24 | 2012-08-30 | Kushal Das | Mechanism for Managing Support Criteria-Based Application Binary Interface/Application Programming Interface Differences |
US8898629B2 (en) * | 2011-04-06 | 2014-11-25 | Media Direct, Inc. | Systems and methods for a mobile application development and deployment platform |
US8650550B2 (en) * | 2011-06-07 | 2014-02-11 | Blackberry Limited | Methods and devices for controlling access to computing resources |
US8763080B2 (en) * | 2011-06-07 | 2014-06-24 | Blackberry Limited | Method and devices for managing permission requests to allow access to a computing resource |
-
2012
- 2012-06-26 CN CN201210214155.6A patent/CN103514000B/zh active Active
-
2013
- 2013-06-26 WO PCT/CN2013/078056 patent/WO2014000652A1/zh active Application Filing
-
2014
- 2014-12-25 US US14/583,133 patent/US20150121083A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050240798A1 (en) * | 2004-03-31 | 2005-10-27 | Microsoft Corporation | System and method of preventing a web browser plug-in module from generating a failure |
CN101369930A (zh) * | 2008-09-01 | 2009-02-18 | 深圳市深信服电子科技有限公司 | 一种网络插件的安全检查方法、系统及安全检查设备 |
US20110239288A1 (en) * | 2010-03-24 | 2011-09-29 | Microsoft Corporation | Executable code validation in a web browser |
Also Published As
Publication number | Publication date |
---|---|
CN103514000A (zh) | 2014-01-15 |
CN103514000B (zh) | 2015-09-16 |
US20150121083A1 (en) | 2015-04-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US12041165B2 (en) | Key updating method, apparatus, and system | |
WO2014000652A1 (zh) | 浏览器插件安装方法、装置及终端 | |
JP6576555B2 (ja) | サービス処理方法、デバイス及びシステム | |
CN109600223B (zh) | 验证方法、激活方法、装置、设备及存储介质 | |
TWI606360B (zh) | 一種網頁檢測方法、裝置和系統 | |
WO2017041599A1 (zh) | 业务处理方法及电子设备 | |
WO2015101273A1 (zh) | 一种安全验证方法、相关设备和系统 | |
WO2017185711A1 (zh) | 控制智能设备的方法、装置、系统和存储介质 | |
US20150319173A1 (en) | Co-verification method, two dimensional code generation method, and device and system therefor | |
WO2017020630A1 (zh) | 一种处理订单信息的方法、装置和系统 | |
CN110198301B (zh) | 一种服务数据获取方法、装置及设备 | |
WO2017084288A1 (zh) | 身份验证方法及装置 | |
WO2015027712A1 (zh) | 移动终端连接网络的方法、移动终端与终端设备 | |
WO2014075566A1 (zh) | 敏感操作验证方法、终端设备、服务器和验证系统 | |
WO2019010863A1 (zh) | 控制可信应用访问的方法和终端 | |
WO2013159632A1 (zh) | 实现安全防护的方法、防火墙、终端及可读存储介质 | |
US10454905B2 (en) | Method and apparatus for encrypting and decrypting picture, and device | |
CN106709282B (zh) | 资源文件解密方法及装置 | |
WO2016192511A1 (zh) | 远程删除信息的方法和装置 | |
US10764038B2 (en) | Method and apparatus for generating terminal key | |
WO2015062234A1 (zh) | 移动终端资源处理方法、装置和设备 | |
CN106713319B (zh) | 终端间的远程控制方法、装置、系统及移动终端 | |
WO2015062240A1 (zh) | 一种应用安装的方法、装置和设备 | |
WO2019024882A1 (zh) | 一种自动加密短信的方法、存储设备及移动终端 | |
CN111444539B (zh) | 一种权限处理方法、装置、存储介质及终端 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 13808481 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205N DATED 15/06/2015) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 13808481 Country of ref document: EP Kind code of ref document: A1 |