Service signature method and device compatible with Android applications

Abstract

The present invention relates to a service signature method compatible with Android applications, including: S1: list all data files of the application software package except for the signature of the developer, and complete the service signature operation compatible with Android applications; S2: use the service The self-identity certificate or identity public key is used to verify the service signature of compatible Android applications. In the present invention, the digital signature of the same Android application package will not conflict with the signature of the developer of the application, and the Android applications of different release versions obtained by multi-party re-signature can retain user data when updating and installing; and the service party signature The data is stored in directories related to the domain name of the service party and the business name, and the signature data of different service parties do not interfere with each other, and different business signatures do not affect each other, which fundamentally solves the problem that the signature file names of the traditional application signature mechanism are prone to collision. The invention also discloses a service signature device compatible with Android applications.

Description

technical field [0001] The present invention relates to the field of computer technology, in particular to a service signature method and device compatible with Android applications. Background technique [0002] Digital signature is an information security technology based on message digest operation and asymmetric encryption operation to ensure the integrity, authentication and non-repudiation of information transmission. Digital signature technology has been widely used in social life, and the digital signature of Android applications is a typical application scenario of the above technology. [0003] Specifically, the operation process of Android application digital signature at this stage is: use the digest algorithm to calculate each information file in the Android application package except the META-INF directory into a fixed-length hash value, and combine the hash value and the corresponding The file names are sequentially stored in the META-INF / MANIFEST.MF file; co...

AI Technical Summary

Problems solved by technology

[0004] (1) For the same Android application package, the dual-signature and single-signature packages will be considered by the Android operating system to be released by different developers, which will cause two release versions of the same program to be unable to share Preserve user data when updates are installed;

[0005] (2) Using the traditional application package developer signature mechanism, if multiple signers use the default key alias name, such as CERT, the digital signature of the original signer will be replaced during the second signature

In addition, due to the naming rules of .SF files and .RSA files when signing traditional Android applications, the first eight characters of the key alias are capitalized, resulting in a relatively small namespace for signature file names, which is prone to collisions

[0006] Furthermore, the same Android application is often released in multiple different channels, but the above-mentioned defects of the traditional application package developer’s signature mechanism will cause the multi-channel and different versions of the same application to be unable to retain user data on the user’s mobile phone It is also easy to cause the developer or channel provider's digital signature to be unintentionally stripped, which will eventually lead to confusion in Android application management and a decline in user experience.

Images