WO2017197869A1 - 版本文件校验方法及装置、加密方法及装置和存储介质 - Google Patents

版本文件校验方法及装置、加密方法及装置和存储介质 Download PDF

Info

Publication number
WO2017197869A1
WO2017197869A1 PCT/CN2016/108214 CN2016108214W WO2017197869A1 WO 2017197869 A1 WO2017197869 A1 WO 2017197869A1 CN 2016108214 W CN2016108214 W CN 2016108214W WO 2017197869 A1 WO2017197869 A1 WO 2017197869A1
Authority
WO
WIPO (PCT)
Prior art keywords
version file
verification
version
download
verified
Prior art date
Application number
PCT/CN2016/108214
Other languages
English (en)
French (fr)
Inventor
王磊
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2017197869A1 publication Critical patent/WO2017197869A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0859—Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions
    • 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/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • 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

Definitions

  • the present invention relates to the field of communication security technologies, and in particular, to a version file verification method and apparatus, an encryption method and apparatus, and a storage medium.
  • the download protection feature is a feature proposed by some project operators for security reasons. The purpose is to restrict users from illegally downloading versions and destroying the software system in the prototype. In order to implement the download protection function, the usual method is to sign a specific algorithm for the version. Such a version is called a security version, and the user will fail if downloading an illegal unsigned version.
  • the download plug-in in order to ensure the security of the download process, the download plug-in is usually verified. However, once the user cracks the download plug-in, the illegal version file can be downloaded privately, which causes a huge security risk.
  • the main purpose of the embodiment of the present invention is to provide a version file verification method and device, an encryption method and device, and a computer storage medium, which provide effective download protection for the version file, and avoid the situation that the illegal version file is downloaded.
  • a version file verification method provided by an embodiment of the present invention includes: verifying the download plug-in when the download plug-in with encrypted data is running; and verifying when the download plug-in verification is passed The verified version file; when the verification of the version file to be verified passes, the verification succeeds.
  • the verifying the downloading plugin includes: presetting a preset location in the downloading plugin
  • the encrypted data is decrypted to generate a security version number and summary data; the security version number and the summary data are verified.
  • the verification needs to verify the version file, including: performing a calculation on the version file to be verified, generating the to-be-checked summary data; determining whether the to-be-checked summary data is the same as the preset summary data, If yes, the version file is successfully verified. If not, the version file verification fails.
  • an embodiment of the present invention further provides an encryption method, where the method includes: signing, by a signature tool, each version file to be protected, and generating encrypted data corresponding to the version file to be protected; Data is added to the preset location of the download plugin.
  • the signature file is used to sign each version file to be protected, and the encrypted data corresponding to the version file to be protected is generated, including: generating a preset summary corresponding to each version file to be protected. Data; encrypting the security version number in the signature tool and the preset summary data to generate encrypted data.
  • an embodiment of the present invention further provides a version file verification apparatus, where the apparatus includes: a download plug-in verification module configured to verify the download when downloading a plug-in with encrypted data The plug-in; the version file verification module is configured to verify the version file to be verified when the download plug-in verification passes, and the verification succeeds when the verification of the version file to be verified is passed.
  • the downloading plug-in verification module includes: a decrypting unit configured to decrypt the encrypted data at the preset location in the downloading plug-in to generate a security version number and summary data; the first verification unit is configured to Verifying the security version number and the summary data.
  • the version file verification module includes: a first calculating unit configured to perform operation on the version file to be verified to generate summary data to be verified; and a second verification unit, configured to determine the to-be-checked Check whether the summary data is the same as the default summary data. If yes, the version file is successfully verified. If not, the version file verification fails.
  • the embodiment of the present invention further provides an encryption device, the device includes: a signature module, configured to sign each version file to be protected by a signature tool, and generate encrypted data corresponding to the version file to be protected; The encrypted data is added to the module, configured to add the encrypted data to a preset location of the download plugin.
  • a signature module configured to sign each version file to be protected by a signature tool, and generate encrypted data corresponding to the version file to be protected.
  • the encrypted data is added to the module, configured to add the encrypted data to a preset location of the download plugin.
  • the signing module includes: a second calculating unit configured to generate preset summary data corresponding to each version file to be protected; an encryption computing unit configured to use a security version number in the signature tool and the The preset summary data is subjected to an encryption operation to generate encrypted data.
  • the embodiment of the present invention provides a computer storage medium, where the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute the version file verification method according to any one of the foregoing.
  • the embodiment of the invention provides a calculation scheme, and when the download plug-in with encrypted data is running, the download plug-in is verified.
  • the download plug-in verification is passed, the version file to be verified is verified, and the version file verification to be verified is performed.
  • the verification is successful. Therefore, the version security is effectively protected.
  • the download process of the present invention can effectively detect the illegal version file and report an error, and immediately exit the download.
  • FIG. 1 is a schematic flowchart of a method for verifying a version file according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of an encryption method according to a preferred embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a sub-flow of the encryption method in FIG. 2;
  • FIG. 4 is a schematic diagram showing the data structure of the array in FIG. 3;
  • FIG. 5 is a schematic flowchart of a method for verifying a version file according to an embodiment of the present invention
  • FIG. 6 is a schematic flowchart of a version file verification method according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic diagram of a module of a version file verification apparatus according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a module of a signature module in an encryption device according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic diagram of a module of a version file verification apparatus according to an embodiment of the present invention.
  • FIG. 10 is a schematic block diagram of a version file verification apparatus according to an embodiment of the present invention.
  • FIG. 1 is a schematic flowchart of a method for verifying a version file according to an embodiment of the present invention, where the method includes:
  • Step 110 When the download plug-in with the encrypted data is run, determine whether the download plug-in is verified.
  • the plug-in is downloaded by the Bootloader and the download plug-in is verified.
  • the download plug-in includes preset encrypted data, which is preset by the terminal (eg, mobile phone) manufacturer.
  • the process proceeds to step 130.
  • the download plug-in verification fails, the process proceeds to step 170 and the download is exited.
  • step 130 it is determined whether the version file is verified or not.
  • step 150 when the verification of the version file that needs to be verified is passed, the process proceeds to step 150; when the verification of the version file that needs to be verified fails, the process proceeds to step 170.
  • step 150 the verification is successful.
  • step 170 the verification fails, and the version file to be verified is an illegal version file.
  • Step 150 Write the verification version file to the solid state memory and animation editor (Flash).
  • the version file verification method provided in this embodiment is applied to a terminal such as a mobile phone, and the download plug-in is verified by running the download plug-in with encrypted data, and the version file to be verified is verified when the download plug-in verification is passed.
  • the download process of the embodiment of the present invention can effectively detect the illegal version file and report an error, and immediately exit the download.
  • the signed security version it can be successfully downloaded through the verification of each stage in the download process.
  • an embodiment of the present invention further provides an encryption method, where the encryption method includes:
  • Step 210 Sign each version file to be protected by a signature tool, and generate encrypted data corresponding to the version file to be protected.
  • step 210 specifically includes:
  • Step 310 Enter a security version number in the signature tool.
  • step 310 may be omitted if the signature tool has a security version number.
  • Step 320 Generate preset summary data corresponding to each version file to be protected
  • SHA1 Secure Hash Algorithm
  • DSA Digital Signature Algorithm
  • DSS Digital Signature Standard
  • the message digest of each version file to be protected is extracted, so that each version file to be protected generates a hash value of 20 bytes as the preset digest data.
  • Step 330 Put the security version number and the preset summary data into one of an array, a heap, a stack, or any combination;
  • the security version number and each of the version files that need to be protected are hashed by the SHA1 algorithm into one of an array, a heap, a stack, or any combination.
  • FIG. 4 it is a data structure diagram of an array, including a security version number, a download plug-in hash value, a version file 1 hash value, a version file 2 hash value, ..., a version.
  • File n hash value is a data structure diagram of an array, including a security version number, a download plug-in hash value, a version file 1 hash value, a version file 2 hash value, ..., a version.
  • Step 340 Perform an encryption operation on one of the array, the heap, the stack, or any combination to generate encrypted data.
  • the RSA encryption operation is performed on the security version number and the at least one preset summary data in one of the array, the heap, the stack, or any combination, and the 256-byte RSA encrypted data is generated.
  • Step 230 Add the encrypted data to a preset location of the download plugin.
  • 256 bytes of RSA encrypted data is added to the preset location of the download plugin.
  • the encrypted data is added to the end of the download plugin.
  • each version file to be protected is signed by the signature tool, and the encrypted data corresponding to the version file to be protected is generated, and the encrypted data is added to the preset position of the download plug-in. This makes the download plug-in with encrypted data, which improves the security of the download plug-in.
  • an embodiment of the present invention further provides a version file verification method.
  • the version file verification method is a further improvement of the first embodiment, and the specific difference is that the verification of the download plug-in in the embodiment specifically includes:
  • Step 510 Decrypt the encrypted data at the preset location in the download plug-in to generate a security version number and summary data.
  • the encrypted data at the end of the download plug-in is decrypted to generate a secure version number and summary data.
  • the Bootloader downloads, and the Bootloader extracts the 256-byte RSA encrypted data at the end of the download plug-in, and then performs RSA decryption to generate one or any combination of an array, a heap, a stack, the array, the heap, One or any combination of the stack includes a security version number and summary data, and preferably, the summary data is a hash value.
  • Step 530 Verify the security version number and the summary data.
  • the bootloader extracts the security version number from the array, the heap, the stack, or any combination, and compares the security version number with the security version number defined in the bootloader. If the comparison result is the same, the security is safe. The version number is verified, otherwise the verification fails and the download is exited.
  • the bootloader extracts the summary data of the downloaded plug-in from one of the array, the heap, the stack, or any combination.
  • the summary data is a 20-byte hash value (represented by A) and is made to the in-memory download plug-in.
  • SHA1 generates a 20-byte hash value (indicated by B); compares the generated 20-byte hash value (B) with the extracted 20-byte hash value (A), if the comparison result is the same, Download the plugin verification pass, otherwise the download plugin verification fails and exits the download.
  • the version file verification method provided in this embodiment decrypts the encrypted data of the preset location of the download plug-in, generates a security version number and summary data, and separately verifies the security version number and the summary data, so as to implement the downloading plug-in. check. Thereby effectively ensuring the verification process and improving version security.
  • an embodiment of the present invention further provides a version file verification method.
  • the version file verification method is a further improvement of the first embodiment, and the specific difference is that the version file that needs to be verified in the verification in the first embodiment specifically includes:
  • Step 610 Perform a calculation on the version file to be verified, and generate summary data to be verified.
  • the Bootloader verifies that the download plugin passes, it jumps to the plugin execution and downloads the plugin download.
  • the download plugin puts the version files that need to be verified into memory in turn.
  • the version file that needs to be verified in the memory is calculated to generate summary data to be verified.
  • Step 630 Determine whether the to-be-checked summary data is the same as the preset summary data, and if yes, go to step 650; if no, go to step 670.
  • step 650 determining whether the to-be-checked summary data (preferably a hash value to be verified) is the same as the preset summary data (preferably a preset hash value) of the signed version file to be protected, if the same, then Proceed to step 650, if not, proceed to step 670.
  • the preset summary data preferably a preset hash value
  • step 650 the version file is successfully verified.
  • step 670 the version file verification fails.
  • the version file that failed to download the verification is exited, and the version file is not written to Flash.
  • the version file verification method in this embodiment performs a secure hash operation on the version file to be verified, generates a hash value to be verified, and determines whether the hash value to be verified is the same as the hash value of the version file. If yes, the version file is successfully verified. If not, the version file verification fails. Thereby verifying the various stages in the download process, implementing various functions of the download protection, and effectively protecting the version security.
  • the embodiment of the invention further provides a version file verification device.
  • FIG. 7 is a block diagram of a version file verification apparatus according to a fourth embodiment of the present invention. schematic diagram.
  • This embodiment is a version file verification device, and the device includes:
  • the plug-in verification module 710 is configured to determine whether the download plug-in passes the verification when the download plug-in with the encrypted data is run.
  • the download plug-in verification module 710 downloads the plug-in through the Bootloader and verifies the download plug-in, and the download plug-in includes preset encrypted data, which is preset by the terminal (eg, mobile phone) manufacturer.
  • the download plug-in verification passes, the version file verification module 730 is triggered, and when the download plug-in verification fails, the download is exited.
  • the version file verification module 730 is configured to: when the verification of the downloading plug-in is passed, determine whether the version file to be verified is verified, and when the verification of the version file to be verified is passed, the verification succeeds. Otherwise, the verification fails, and the version file to be verified is an illegal version file.
  • the version file verification module 730 verifies the version file that needs to be verified, the version file is successfully verified, and the other version files that need to be verified are further verified.
  • the version file verification module 730 fails to verify the version file that needs to be verified, the verification fails, and the version file to be verified is an illegal version file.
  • the device further includes a writing module, configured to write the verified version file to the solid state memory and the animation editor (Flash).
  • a writing module configured to write the verified version file to the solid state memory and the animation editor (Flash).
  • the version file verification apparatus is applied to a terminal such as a mobile phone, and the download plug-in verification module 710 verifies the download plug-in when the download plug-in is running, and the version file verification module 730, when the download plug-in verification passes, Verify the version file to be verified.
  • the downloading process of the present invention can effectively detect the illegal version file and report an error, and immediately exit the download.
  • the signed security version it can be successfully downloaded through the verification of each stage in the download process.
  • An embodiment of the present invention further provides an encryption device, where the device includes a signature module and an encrypted data adding module, where:
  • the signature module is configured to sign each version file to be protected by using a signature tool to generate encrypted data corresponding to the version file to be protected.
  • the signature module includes:
  • the security version number input unit 810 is configured to input a security version number in the signature tool.
  • the security version number input unit 810 inputs a security version number in the signature tool, and the input security version number is consistent with the security version number defined in the current version of the bootloader. In other embodiments, if the signature version has a security version number, the security version number input unit 810 may not be triggered.
  • the calculating unit 820 is configured to generate preset summary data corresponding to each version file that needs to be protected.
  • the calculating unit 820 performs a SHA1 operation on each version file that needs to be protected.
  • SHA1 is mainly applicable to DSAs defined in DSS. For messages less than 2 ⁇ 64 bits in length, SHA1 will generate a 160-bit message digest, which is a 20-byte message digest.
  • the computing unit 820 extracts a message digest of each version file that needs to be protected, so that each version file to be protected generates a hash value of 20 bytes as the default digest data.
  • the array unit 830 is configured to put the security version number and the preset summary data into one of an array, a heap, a stack, or any combination.
  • the array unit 830 sequentially puts the security version number and the hash value generated by the SHA1 algorithm for each version file to be protected (such as a total of n version files) into one array, heap, stack, or any combination.
  • each version file to be protected such as a total of n version files
  • FIG 4 is an array A schematic diagram of the data structure, including the security version number, the download plug-in hash value, the version file 1 hash value, the version file 2 hash value, ..., the version file n hash value.
  • the encryption calculation unit 840 is configured to perform an encryption operation on one of the array, the heap, and the stack, or generate an encrypted data.
  • the encryption calculation unit 840 performs an RSA encryption operation on the security version number and the at least one preset summary data in one of the array, the heap, the stack, or any combination, and generates 256-byte RSA-encrypted data.
  • the encrypted data is added to the module, configured to add the encrypted data to a preset location of the download plugin.
  • 256 bytes of RSA encrypted data is added to the preset location of the download plugin.
  • the encrypted data is added to the end of the download plugin.
  • the signature module signs each version file to be protected by using a signature tool, generates encrypted data corresponding to the version file to be protected, and adds the encrypted data to the encrypted data adding module. Download the preset location of the plugin. This makes the download plug-in with encrypted data, which improves the security of the download plug-in.
  • an embodiment of the present invention further provides a version file verification apparatus.
  • the version file verification device is a further improvement of the fourth embodiment, and the specific difference is that the download plug-in verification module includes:
  • the decryption unit 910 is configured to decrypt the encrypted data at the preset location in the download plug-in to generate a security version number and summary data.
  • the decryption unit 910 decrypts the encrypted data at the end of the download plug-in to generate a secure version number and summary data.
  • the bootloader will download 256 at the end of the plugin.
  • the RSA encrypted data of the byte is extracted, and then the decryption unit 910 performs RSA decryption to generate one or any combination of an array, a heap, a stack, and one or any combination of the array, the heap, the stack, and the security version number and the summary data.
  • the summary data is a hash value.
  • the first verification unit 930 is configured to verify the security version number and the summary data.
  • the bootloader extracts the security version number from the array, the heap, the stack, or any combination, and the first verification unit 930 compares the security version number with the security version number defined in the bootloader, if the comparison is performed. The result is the same, the security version number is verified, otherwise the verification fails and the download is exited.
  • the bootloader extracts the summary data of the downloaded plug-in from one of the array, the heap, the stack, or any combination.
  • the summary data is a 20-byte hash value (represented by A) and is made to the in-memory download plug-in.
  • SHA1 generating a 20-byte hash value (represented by B);
  • the first check unit 930 compares the generated 20-byte hash value (B) with the extracted 20-byte hash value (A), if If the comparison result is the same, the download plug-in verification is passed, otherwise the download plug-in verification fails and the download is exited.
  • the decryption unit 910 decrypts the encrypted data of the preset position of the download plug-in, generates a security version number and summary data, and verifies the security version number and the first verification unit 930 respectively. Summary data to verify the download plugin. Thereby effectively ensuring the verification process and improving version security.
  • an embodiment of the present invention further provides a version file verification apparatus.
  • the version file verification device is a further improvement of the fourth embodiment, and the specific difference is that the version file verification module includes:
  • the calculating unit 1010 is configured to perform calculation on the version file that needs to be verified, and generate summary data to be verified.
  • the Bootloader when the Bootloader verifies that the download plugin passes, it jumps to the plugin execution and downloads the plugin download.
  • the download plugin puts the version files that need to be verified into memory in turn.
  • the calculating unit 1010 performs a calculation on the version file in the memory that needs to be verified, and generates summary data to be verified.
  • the version file SHA1 that needs to be verified is calculated, and the to-be-checked hash value of each version file that needs to be verified is calculated.
  • the second check unit 1030 is configured to determine whether the to-be-checked summary data is the same as the preset summary data. If yes, the version file verification succeeds. If not, the version file verification fails.
  • the second check unit 1030 determines whether the summary data to be checked (preferably a hash value to be verified) and the preset summary data (preferably a preset hash value) of the signed version file to be protected are The same, if the same, the version file is successfully verified, the version file that has been verified in memory is written to Flash, and the above steps are repeated to download other version files. If it is not the same, the version file verification fails, and the version file that failed the verification verification is exited, and the version file is not written to Flash.
  • the summary data to be checked preferably a hash value to be verified
  • the preset summary data preferably a preset hash value
  • the version file verification apparatus performs a secure hash operation on the version file to be verified by the calculation unit 1010 to generate a hash value to be verified, and the second verification unit 1030 determines the hash to be verified. Whether the value is the same as the hash value of the version file. If yes, the version file is successfully verified. If not, the version file verification fails. Thereby verifying the various stages in the download process, implementing various functions of the download protection, and effectively protecting the version security.
  • the embodiment of the present invention further provides a computer storage medium, where the computer storage medium stores computer executable instructions, and the computer executable instructions are used to execute one or more of the version file verification methods provided by any of the foregoing embodiments. For example, the method shown in FIG. 1, FIG. 2, FIG. 3, FIG. 5 or FIG. 6 can be performed.
  • the computer storage medium may be a random storage medium RAM, Read-only storage media ROM, flash memory or various storage media such as optical disks, magnetic tapes, etc., preferably non-transitory storage media.
  • the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better.
  • Implementation Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Storage Device Security (AREA)
  • Stored Programmes (AREA)

Abstract

本发明提供的一种版本文件校验方法及装置。该方法包括：在带有加密数据的下载插件运行时，校验下载插件；当下载插件校验通过时，校验需要校验的版本文件；当需要校验的版本文件校验通过时，则校验成功。从而本发明的版本文件校验方法及装置能够有效地保护版本安全，对于替换下载插件或者需要校验的版本文件，本发明的下载过程可以有效的检测到是非法版本文件并报错，即时退出下载。本发明还提供一种计算机存储介质。

Description

版本文件校验方法及装置、加密方法及装置和存储介质 技术领域
本发明涉及通讯安全技术领域，尤其涉及一种版本文件校验方法及装置、加密方法及装置和存储介质。
背景技术
下载保护功能是某些项目运营商出于安全考虑提出的一项功能，目的是限制用户非法进行版本下载，破坏样机中的软件系统。为了实现下载保护功能，通常采用的手段是通过对版本进行特定的算法签名，这样的版本称为安全版本，用户如果下载非法的未经签名的版本就会失败。
现有技术中，为了保证下载过程的安全性，通常采用对下载插件进行校验，然而，一旦用户破解了下载插件就可以私自下载非法的版本文件，这就导致存在巨大的安全隐患。
发明内容
本发明实施例的主要目的在于提出一种版本文件校验方法及装置、加密方法及装置和计算机存储介质，为版本文件提供有效地下载保护，避免下载非法版本文件的情况发生。
本发明实施例提供的一种版本文件校验方法，所述方法包括：在带有加密数据的下载插件运行时，校验所述下载插件；当所述下载插件校验通过时，校验需要校验的版本文件；当所述需要校验的版本文件校验通过时，则校验成功。
可选地，所述校验所述下载插件，包括：将所述下载插件中预设位置 处的加密数据进行解密，生成安全版本号和摘要数据；校验所述安全版本号和所述摘要数据。
可选地，所述校验需要校验的版本文件，包括：对需要校验的版本文件进行运算，生成待校验摘要数据；判断所述待校验摘要数据是否与预设摘要数据相同，若是，则版本文件校验成功，若否，则版本文件校验失败。
此外，本发明实施例还提出一种加密方法，所述方法包括：通过签名工具对每个需要保护的版本文件进行签名，生成与所述需要保护的版本文件对应的加密数据；将所述加密数据加入到所述下载插件的预设位置。
可选地，所述通过签名工具对每个需要保护的版本文件进行签名，生成与所述需要保护的版本文件对应的加密数据，包括：生成与每个需要保护的版本文件对应的预设摘要数据；对签名工具中的安全版本号和所述预设摘要数据进行加密运算，生成加密数据。
此外，为实现上述目的，本发明实施例还提出一种版本文件校验装置，所述装置包括：下载插件校验模块，配置为在下载带有加密数据的插件运行时，校验所述下载插件；版本文件校验模块，配置为当所述下载插件校验通过时，校验需要校验的版本文件，当所述需要校验的版本文件校验通过时，则校验成功。
可选地，所述下载插件校验模块包括：解密单元，配置为将所述下载插件中预设位置处的加密数据进行解密，生成安全版本号和摘要数据；第一校验单元，配置为校验所述安全版本号和所述摘要数据。
可选地，所述版本文件校验模块，包括：第一计算单元，配置为对需要校验的版本文件进行运算，生成待校验摘要数据；第二校验单元，用于判断所述待校验摘要数据是否与预设摘要数据相同，若是，则版本文件校验成功，若否，则版本文件校验失败。
此外，本发明实施例还提出一种加密装置所述装置包括：签名模块，配置为通过签名工具对每个需要保护的版本文件进行签名，生成与所述需要保护的版本文件对应的加密数据；加密数据加入模块，配置为将所述加密数据加入到所述下载插件的预设位置。
可选地，所述签名模块包括：第二计算单元，配置为生成与每个需要保护的版本文件对应的预设摘要数据；加密计算单元，配置为对签名工具中的安全版本号和所述预设摘要数据进行加密运算，生成加密数据。
本发明实施例提供一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于执行前述任一项所述版本文件校验方法。
本发明实施例提出计算方案，在带有加密数据的下载插件运行时，校验下载插件，当下载插件校验通过时，校验需要校验的版本文件，当需要校验的版本文件校验通过时，则校验成功。从而有效地保护版本安全，对于替换下载插件或者需要校验的版本文件，本发明的下载过程可以有效的检测到是非法版本文件并报错，即时退出下载。
附图说明
图1为本发明实施例提供的版本文件校验方法的流程示意图；
图2为本发明较佳实施例提供的加密方法的流程示意图；
图3为图2中加密方法的子流程示意图；
图4为图3中数组的数据结构示意图；
图5为本发明实施例提供的版本文件校验方法的流程示意图；
图6为本发明实施例提供的版本文件校验方法的流程示意图；
图7为本发明实施例提供的版本文件校验装置的模块示意图；
图8为本发明实施例提供的加密装置中签名模块的模块示意图；
图9为本发明实施例提供的版本文件校验装置的模块示意图；
图10为本发明实施例提供的版本文件校验装置的模块示意图。
具体实施方式
以下结合附图对本发明的优选实施例进行详细说明，应当理解，此处所描述的具体实施例仅仅用以解释本发明，并不用于限定本发明。在后续的描述中，使用用于表示元件的诸如“模块”或“单元”的后缀仅为了有利于本发明的说明，其本身并没有特定的意义。
请参照图1，为本发明实施例提供一种版本文件校验方法的流程示意图，所述方法包括：
步骤110，在带有加密数据的下载插件运行时，判断所述下载插件是否校验通过。
可选地，用Bootloader下载插件并校验该下载插件，该下载插件中包括预设的加密数据，该加密数据为终端(例如手机)制造商预设的。当下载插件校验通过时，则进入步骤130，当下载插件校验失败时，则进入步骤170并退出下载。
步骤130，判断版本文件是否校验通过。
可选地，当所述需要校验的版本文件校验通过时，则进入步骤150；所述需要校验的版本文件校验未通过时，则进入步骤170。
步骤150，校验成功。
可选地，重复上述步骤校验其他需要校验的版本文件。
步骤170，校验失败，所述需要校验的版本文件为非法版本文件。
可选地，作为对第一实施例的进一步改进，在步骤150之后，还包括 步骤：将校验通过的版本文件写入固态存储器与动画编辑器(Flash)。
本实施例提供的版本文件校验方法，应用于手机等终端，通过在带有加密数据的下载插件运行时，校验下载插件，当下载插件校验通过时，校验需要校验的版本文件，当需要校验的版本文件校验通过时，则校验成功，否则校验失败。从而有效地保护版本安全，对于替换下载插件或者需要校验的版本文件，本发明实施例的下载过程可以有效的检测到是非法版本文件并报错，即时退出下载。对于已签名的安全版本，能够通过下载过程中各个阶段的校验，成功下载。
请参照图2，本发明一个实施例还提供一种加密方法，所述加密方法包括：
步骤210，通过签名工具对每个需要保护的版本文件进行签名，生成与所述需要保护的版本文件对应的加密数据。
可选地，请参照图3，步骤210具体包括：
步骤310，在签名工具中输入安全版本号；
可选地，在签名工具中输入一个安全版本号，输入的安全版本号与当前版本Bootloader中定义的安全版本号保持一致。在其他实施例中，若签名工具中带有安全版本号，则可以省略步骤310。
步骤320，生成与每个需要保护的版本文件对应的预设摘要数据；
可选地，在本发明一优选实施例中，对每个需要保护的各个版本文件做安全哈希算法(Secure Hash Algorithm，SHA1)。SHA1主要适用于数字签名标准(Digital Signature Standard，DSS)里面定义的数字签名算法(Digital Signature Algorithm，DSA)。对于长度小于2^64位的消息，SHA1会产生一个160位的消息摘要，也就是20字节的消息摘要。
可选地地，提取每个需要保护的版本文件的消息摘要，使每个需要保护的版本文件生成20字节的哈希值作为预设摘要数据。
步骤330，将所述安全版本号与所述预设摘要数据放入数组、堆、栈之一或者任意组合；
可选地，将安全版本号与每个需要保护的版本文件(如共有n个版本文件)做SHA1算法生成的哈希值依次放入一个数组、堆、栈之一或者任意组合。在本发明的优选实施例中，如图4所示，为数组的数据结构示意图，包括安全版本号、下载插件哈希值、版本文件1哈希值、版本文件2哈希值、…、版本文件n哈希值。步骤340，对所述数组、堆、栈之一或者任意组合进行加密运算，生成加密数据。
可选地，对数组、堆、栈之一或者任意组合中安全版本号和至少一个预设摘要数据采用RSA加密运算，并生成256字节的RSA加密数据。
步骤230，将所述加密数据加入到所述下载插件的预设位置。
可选地，将256字节的RSA加密数据加入到下载插件的预设位置。
可选地，将加密数据加入到下载插件的尾部。
本发明实施例提出的加密方法，通过签名工具对每个需要保护的版本文件进行签名，生成与所述需要保护的版本文件对应的加密数据，并将加密数据加入到下载插件的预设位置。从而使下载插件中带有加密数据，提高了下载插件的安全性。
请参照图5，本发明实施例进一步提供一种版本文件校验方法。在第二实施例中，所述版本文件校验方法是对第一实施例的进一步改进，具体区别在于，本实施例中的校验所述下载插件具体包括：
步骤510，将下载插件中预设位置处的加密数据进行解密，生成安全版本号和摘要数据。
可选地，将下载插件尾部的加密数据进行解密，生成安全版本号和摘要数据。
更可选地，通过Bootloader下载，且Bootloader将下载插件尾部的256字节的RSA加密数据提取出来，然后对其进行RSA解密，生成数组、堆、栈之一或者任意组合，该数组、堆、栈之一或者任意组合包括安全版本号和摘要数据，作为优选，所述摘要数据为哈希值。
步骤530，校验所述安全版本号和所述摘要数据。
可选地，Bootloader从该数组、堆、栈之一或者任意组合中提取出安全版本号，并将该安全版本号与Bootloader中定义的安全版本号进行比对，如果比对结果相同，则安全版本号校验通过，否则校验失败并退出下载。
Bootloader从数组、堆、栈之一或者任意组合中提取出下载插件的摘要数据，作为可选地，该摘要数据为20字节哈希值(以A表示)，并对内存中的下载插件做SHA1，生成20字节哈希值(以B表示)；将生成的20字节哈希值(B)与提取的20字节哈希值(A)进行比对，如果比对结果相同，则下载插件校验通过，否则下载插件校验失败并退出下载。
本实施例提供的版本文件校验方法，通过将下载插件预设位置的加密数据进行解密，生成包括安全版本号和摘要数据，并分别校验安全版本号和摘要数据，以实现对下载插件的校验。从而有效地保障了校验过程，提高了版本安全性。
请参照图6，本发明实施例进一步提供一种版本文件校验方法。在第三实施例中，所述版本文件校验方法是对第一实施例的进一步改进，具体区别在于，第一实施例中的校验需要校验的版本文件具体包括：
步骤610，对需要校验的版本文件进行运算，生成待校验摘要数据。
可选地，当Bootloader校验下载插件通过时，则跳转至插件执行，进行下载插件下载。下载插件将需要校验的版本文件依次放入内存中。对内存中需要校验的版本文件进行运算，生成待校验摘要数据。
可选地，对需要校验的版本文件进行SHA1运算，算出每个需要校验的版本文件的待校验哈希值。
步骤630，判断待校验摘要数据是否与预设摘要数据相同，若是，则进入步骤650；若否，则进入步骤670。
可选地，判断待校验摘要数据(优选为待校验哈希值)与已签名的需要保护的版本文件的预设摘要数据(优选为预设哈希值)是否相同，若相同，则进入步骤650，若不相同，则进入步骤670。
步骤650，版本文件校验成功。
可选地，将内存中已经校验成功的版本文件写入Flash，并重复上述步骤下载其他版本文件。
步骤670，版本文件校验失败。
可选地，退出下载校验失败的版本文件，且该版本文件不会写入Flash。
需要说明的是，在需要待校验的版本文件中，只要有一个版本文件校验失败，就退出下载。
本实施例提出的版本文件校验方法，通过对需要校验的版本文件进行安全哈希运算，生成待校验哈希值，判断该待校验哈希值是否与版本文件的哈希值相同，若是，则版本文件校验成功，若否，则版本文件校验失败。从而对下载过程中的各个阶段进行校验，实现了下载保护的各个功能，有效地保护版本安全。
本发明实施例进一步提供一种版本文件校验装置。
请参照图7，图7为本发明第四实施例提供的版本文件校验装置的模块 示意图。
本实施例一种版本文件校验装置，所述装置包括：
下载插件校验模块710，配置为在带有加密数据的下载插件运行时，判断下载插件是否校验通过。
可选地，下载插件校验模块710通过Bootloader下载插件并校验该下载插件，，该下载插件中包括预设的加密数据，该加密数据为终端(例如手机)制造商预设的。当下载插件校验通过时，则触发版本文件校验模块730，当下载插件校验失败时，则退出下载。
版本文件校验模块730，配置为当所述下载插件校验通过时，判断需要校验的版本文件是否校验通过，当所述需要校验的版本文件校验通过时，则校验成功，否则校验失败，所述需要校验的版本文件为非法版本文件。
可选地，当版本文件校验模块730对所述需要校验的版本文件校验通过时，则版本文件校验成功，并进一步校验其他需要校验的版本文件。当版本文件校验模块730对所述需要校验的版本文件校验未通过时，则校验失败，所述需要校验的版本文件为非法版本文件。
可选地，所述装置还包括写入模块，用于将校验通过的版本文件写入固态存储器与动画编辑器(Flash)。
本实施例提供的版本文件校验装置，应用于手机等终端，通过下载插件校验模块710在下载插件运行时，校验下载插件，以及版本文件校验模块730当下载插件校验通过时，校验需要校验的版本文件，当需要校验的版本文件校验通过时，则校验成功，否则校验失败。从而有效地保护版本安全，对于替换下载插件或者需要校验的版本文件，本发明的下载过程中可以有效的检测到是非法版本文件并报错，即时退出下载。对于已签名的安全版本，能够通过下载过程中各个阶段的校验，成功下载。
本发明实施例还提供一种加密装置，所述装置包括签名模块和加密数据加入模块，其中：
签名模块，配置为通过签名工具对每个需要保护的版本文件进行签名，生成与所述需要保护的版本文件对应的加密数据。
请参照图8，签名模块包括：
安全版本号输入单元810，配置为在签名工具中输入安全版本号。
可选地，安全版本号输入单元810在签名工具中输入一个安全版本号，输入的安全版本号与当前版本Bootloader中定义的安全版本号保持一致。在其他实施例中，若签名工具中带有安全版本号，则可以无需触发安全版本号输入单元810。
计算单元820，用于生成与每个需要保护的版本文件对应的预设摘要数据。
可选地，在本发明实施例中，计算单元820对每个需要保护的各个版本文件做SHA1运算。SHA1主要适用于DSS里面定义的DSA。对于长度小于2^64位的消息，SHA1会产生一个160位的消息摘要，也就是20字节的消息摘要。
更可选地，计算单元820提取每个需要保护的版本文件的消息摘要，使每个需要保护的版本文件生成20字节的哈希值作为预设摘要数据。
数组单元830，配置为将所述安全版本号与所述预设摘要数据放入数组、堆、栈之一或者任意组合。
可选地，数组单元830将安全版本号与每个需要保护的版本文件(如共有n个版本文件)做SHA1算法生成的哈希值依次放入一个数组、堆、栈之一或者任意组合。在本发明的优选实施例中，如图4所示，为数组的 数据结构示意图，包括安全版本号、下载插件哈希值、版本文件1哈希值、版本文件2哈希值、…、版本文件n哈希值。
加密计算单元840，用于对所述数组、堆、栈之一或者任意组合进行加密运算，生成加密数据。
可选地，加密计算单元840对该数组、堆、栈之一或者任意组合中安全版本号和至少一个预设摘要数据采用RSA加密运算，并生成256字节的RSA加密数据。
加密数据加入模块，配置为将所述加密数据加入到所述下载插件的预设位置。
可选地，将256字节的RSA加密数据加入到下载插件的预设位置。
可选地，将加密数据加入到下载插件的尾部。
本发明实施例提出的加密装置，签名模块通过签名工具对每个需要保护的版本文件进行签名，生成与所述需要保护的版本文件对应的加密数据，并通过加密数据加入模块将加密数据加入到下载插件的预设位置。从而使下载插件中带有加密数据，提高了下载插件的安全性。
请参照图9，本发明实施例还提供一种版本文件校验装置。在第五实施例中，所述版本文件校验装置是对第四实施例的进一步改进，具体区别在于，下载插件校验模块包括：
解密单元910，配置为将所述下载插件中预设位置处的加密数据进行解密，生成安全版本号和摘要数据。
可选地，解密单元910将下载插件尾部的加密数据进行解密，生成安全版本号和摘要数据。
更可选地，通过Bootloader下载，且Bootloader将下载插件尾部的256 字节的RSA加密数据提取出来，然后解密单元910对其进行RSA解密，生成数组、堆、栈之一或者任意组合，该数组、堆、栈之一或者任意组合包括安全版本号和摘要数据，作为优选，所述摘要数据为哈希值。
第一校验单元930，配置为校验所述安全版本号和所述摘要数据。
可选地，Bootloader从该数组、堆、栈之一或者任意组合中提取出安全版本号，第一校验单元930将该安全版本号与Bootloader中定义的安全版本号进行比对，如果比对结果相同，则安全版本号校验通过，否则校验失败并退出下载。
Bootloader从数组、堆、栈之一或者任意组合中提取出下载插件的摘要数据，作为可选地，该摘要数据为20字节哈希值(以A表示)，并对内存中的下载插件做SHA1，生成20字节哈希值(以B表示)；第一校验单元930将生成的20字节哈希值(B)与提取的20字节哈希值(A)进行比对，如果比对结果相同，则下载插件校验通过，否则下载插件校验失败并退出下载。
本实施例提供的版本文件校验装置，解密单元910将下载插件预设位置的加密数据进行解密，生成包括安全版本号和摘要数据，并通过第一校验单元930分别校验安全版本号和摘要数据，以实现对下载插件的校验。从而有效地保障了校验过程，提高了版本安全性。
请参照图10，本发明实施例进一步提供一种版本文件校验装置。在第六实施例中，所述版本文件校验装置是对第四实施例的进一步改进，具体区别在于，版本文件校验模块包括：
计算单元1010，配置为对需要校验的版本文件进行运算，生成待校验摘要数据。
可选地，当Bootloader校验下载插件通过时，则跳转至插件执行，进行下载插件下载。下载插件将需要校验的版本文件依次放入内存中。计算单元1010对内存中需要校验的版本文件进行进行运算，生成待校验摘要数据。
可选地，对需要校验的版本文件SHA1运算，算出每个需要校验的版本文件的待校验哈希值。
第二校验单元1030，配置为判断所述待校验摘要数据是否与预设摘要数据相同，若是，则版本文件校验成功，若否，则版本文件校验失败。
可选地，第二校验单元1030判断待校验摘要数据(优选为待校验哈希值)与已签名的需要保护的版本文件的预设摘要数据(优选为预设哈希值)是否相同，若相同，则版本文件校验成功，将内存中已经校验成功的版本文件写入Flash，并重复上述步骤下载其他版本文件。若不相同，则版本文件校验失败，并退出下载校验失败的版本文件，且该版本文件不会写入Flash。
需要说明的是，在需要待校验的版本文件中，只要有一个版本文件校验失败，就退出下载。
本实施例提出的版本文件校验装置，通过计算单元1010对需要校验的版本文件进行安全哈希运算，生成待校验哈希值，以及第二校验单元1030判断该待校验哈希值是否与版本文件的哈希值相同，若是，则版本文件校验成功，若否，则版本文件校验失败。从而对下载过程中的各个阶段进行校验，实现了下载保护的各个功能，有效地保护版本安全。
本发明实施例还提供一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于执行前述任意实施例提供的版本文件校验方法中的一个或多个，例如可以执行如图1、图2、图3、图5或图6所示的方法。所述计算机存储介质可为随机存储介质RAM、 只读存储介质ROM，闪存flash或光盘、磁带等各种存储介质，优选为非瞬间存储介质。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
上述本发明实施例序号仅仅为了描述，不代表实施例的优劣。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本发明各个实施例所述的方法。
以上仅为本发明的优选实施例，并非因此限制本发明的专利范围，凡按照本发明原理所作的修改，都应当理解为落入本发明的保护范围。

Claims (11)

  1. 一种版本文件校验方法，所述方法包括：
    在带有加密数据的下载插件运行时，校验所述下载插件；
    当所述下载插件校验通过时，校验需要校验的版本文件；
    当所述需要校验的版本文件校验通过时，则校验成功。
  2. 根据权利要求1所述的版本文件校验方法，其中，所述校验所述下载插件，包括：
    将所述下载插件中预设位置处的加密数据进行解密，生成安全版本号和摘要数据；
    校验所述安全版本号和所述摘要数据。
  3. 根据权利要求1或2所述的版本文件校验方法，其中，所述校验需要校验的版本文件，包括：
    对需要校验的版本文件进行运算，生成待校验摘要数据；
    判断所述待校验摘要数据是否与预设摘要数据相同，若是，则版本文件校验成功，若否，则版本文件校验失败。
  4. 一种加密方法，所述方法包括：
    通过签名工具对每个需要保护的版本文件进行签名，生成与所述需要保护的版本文件对应的加密数据；
    将所述加密数据加入到所述下载插件的预设位置。
  5. 根据权利要求4所述的加密方法，其中，所述通过签名工具对每个需要保护的版本文件进行签名，生成与所述需要保护的版本文件对应的加密数据，包括：
    生成与每个需要保护的版本文件对应的预设摘要数据；
    对签名工具中的安全版本号和所述预设摘要数据进行加密运算，生成加密数据。
  6. 一种版本文件校验装置，所述装置包括：
    下载插件校验模块，配置为在带有加密数据的下载插件运行时，校验所述下载插件；
    版本文件校验模块，配置为当所述下载插件校验通过时，校验需要校验的版本文件，当所述需要校验的版本文件校验通过时，则校验成功。
  7. 根据权利要求6所述的版本文件校验装置，其中，所述下载插件校验模块包括：
    解密单元，配置为将所述下载插件中预设位置处的加密数据进行解密，生成安全版本号和摘要数据；
    第一校验单元，配置为校验所述安全版本号和所述摘要数据。
  8. 根据权利要求6或7所述的版本文件校验装置，其中，所述版本文件校验模块，包括：
    第一计算单元，配置为对需要校验的版本文件进行运算，生成待校验摘要数据；
    第二校验单元，配置为判断所述待校验摘要数据是否与预设摘要数据相同，若是，则版本文件校验成功，若否，则版本文件校验失败。
  9. 一种加密装置，所述装置包括：
    签名模块，配置为通过签名工具对每个需要保护的版本文件进行签名，生成与所述需要保护的版本文件对应的加密数据；
    加密数据加入模块，配置为将所述加密数据加入到所述下载插件的预 设位置。
  10. 根据权利要求9所述的加密装置，其中，所述签名模块包括：
    第二计算单元，配置为生成与每个需要保护的版本文件对应的预设摘要数据；
    加密计算单元，配置为签名工具中的安全版本号和所述预设摘要数据进行加密运算，生成加密数据。
  11. 一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1至5任一项所述版本文件校验方法。
PCT/CN2016/108214 2016-05-19 2016-12-01 版本文件校验方法及装置、加密方法及装置和存储介质 WO2017197869A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610338768.9 2016-05-19
CN201610338768.9A CN107404391A (zh) 2016-05-19 2016-05-19 版本文件校验方法及装置和加密方法及装置

Publications (1)

Publication Number Publication Date
WO2017197869A1 true WO2017197869A1 (zh) 2017-11-23

Family

ID=60325726

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/108214 WO2017197869A1 (zh) 2016-05-19 2016-12-01 版本文件校验方法及装置、加密方法及装置和存储介质

Country Status (2)

Country Link
CN (1) CN107404391A (zh)
WO (1) WO2017197869A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110221972A (zh) * 2019-05-21 2019-09-10 深圳壹账通智能科技有限公司 一种应用程序的插件校验方法、设备、服务器及存储介质
CN112115517A (zh) * 2020-09-24 2020-12-22 北京人大金仓信息技术股份有限公司 一种数据库插件的检验方法、装置、设备及介质
CN113448855A (zh) * 2021-07-07 2021-09-28 中国工商银行股份有限公司 数据库版本包检测方法及装置

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111814140B (zh) * 2020-07-02 2024-06-21 杭州万为科技有限责任公司 一种插件发布与离线安全认证方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104102499A (zh) * 2013-04-02 2014-10-15 中兴通讯股份有限公司 移动终端及其软件升级的方法
CN105224874A (zh) * 2014-06-24 2016-01-06 深圳市茁壮网络股份有限公司 基于中间件插件框架的插件安全控制方法及客户端
CN105391763A (zh) * 2015-10-13 2016-03-09 北京奇虎科技有限公司 对多个apk文件进行加固的方法和服务器

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102043649A (zh) * 2009-10-23 2011-05-04 阿里巴巴集团控股有限公司 插件下载控制方法及插件下载控制系统
CN102572595A (zh) * 2012-02-03 2012-07-11 深圳市同洲电子股份有限公司 Iptv的升级包结构、升级方法以及开机校验方法
CN103455358A (zh) * 2013-09-18 2013-12-18 杭州海兴电力科技股份有限公司 电能表程序升级方法
CN104539432B (zh) * 2014-12-31 2016-09-28 深圳市奇付通科技有限公司 一种对文件进行签名的方法和装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104102499A (zh) * 2013-04-02 2014-10-15 中兴通讯股份有限公司 移动终端及其软件升级的方法
CN105224874A (zh) * 2014-06-24 2016-01-06 深圳市茁壮网络股份有限公司 基于中间件插件框架的插件安全控制方法及客户端
CN105391763A (zh) * 2015-10-13 2016-03-09 北京奇虎科技有限公司 对多个apk文件进行加固的方法和服务器

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110221972A (zh) * 2019-05-21 2019-09-10 深圳壹账通智能科技有限公司 一种应用程序的插件校验方法、设备、服务器及存储介质
CN112115517A (zh) * 2020-09-24 2020-12-22 北京人大金仓信息技术股份有限公司 一种数据库插件的检验方法、装置、设备及介质
CN113448855A (zh) * 2021-07-07 2021-09-28 中国工商银行股份有限公司 数据库版本包检测方法及装置

Also Published As

Publication number Publication date
CN107404391A (zh) 2017-11-28

Similar Documents

Publication Publication Date Title
JP6332970B2 (ja) 安全なソフトウェアの更新のためのシステム及び方法
US7694139B2 (en) Securing executable content using a trusted computing platform
TWI557589B (zh) 用於產品驗證和啟動的安全軟體產品識別器
KR101740256B1 (ko) 모바일 앱 무결성 보증 장치 및 방법
US8874922B2 (en) Systems and methods for multi-layered authentication/verification of trusted platform updates
CN101308538B (zh) 检查固件完整性的方法和设备
US9489520B2 (en) Decryption and encryption of application data
CN112507328B (zh) 一种文件签名方法、计算设备及存储介质
EP3316160A1 (en) Authentication method and apparatus for reinforced software
US20090327733A1 (en) Data Security Method and System
WO2017197869A1 (zh) 版本文件校验方法及装置、加密方法及装置和存储介质
CN109388961B (zh) 存储设备的安全控制方法及存储设备
EP2885737B1 (en) Storing and accessing data
CN106789075B (zh) Pos数字签名防切机系统
US7353386B2 (en) Method and device for authenticating digital data by means of an authentication extension module
CN116561734A (zh) 一种验证方法、装置、计算机及计算机配置系统
US8775822B2 (en) Computer-implemented method and system for protecting a software installation after certification
CN111522555B (zh) apk文件的加固方法、解密方法及相关装置
CN112597456A (zh) 数据库的水印添加与验证方法及装置
CN112463184A (zh) 一种基板管理控制器固件安全升级方法及系统
JP2011013428A (ja) 情報処理装置、コード生成方法、コード検証方法およびプログラム
KR101290818B1 (ko) 보안 패치 시스템
CN114327657B (zh) 一种基于Fastboot的大镜像分割下载验签方法及其存储介质
CN115174079B (zh) 基于量子密钥的用户登录认证方法及系统
US20230315865A1 (en) Storage data deletion management system and apparatus

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16902248

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16902248

Country of ref document: EP

Kind code of ref document: A1