Ubuntu
android-platform-tools-apksig package

android-platform-tools-apksig 0.5+git168~g10c9d71-1 source package in Ubuntu

Changelog

android-platform-tools-apksig (0.5+git168~g10c9d71-1) unstable; urgency=medium

  * New upstream release (Closes: #859541)

 -- Hans-Christoph Steiner <email address hidden>  Tue, 04 Apr 2017 21:25:56 +0200

Upload details

Uploaded by:
Android tools Maintainer
Uploaded to:
Sid
Original maintainer:
Android tools Maintainer
Architectures:
all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Builds

Artful: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
android-platform-tools-apksig_0.5+git168~g10c9d71-1.dsc 2.1 KiB 9548f75388e462bb280b44145eea80e575fb812c05ccd4acf27030e332280fff
android-platform-tools-apksig_0.5+git168~g10c9d71.orig.tar.gz 109.5 KiB 08da6206ee593643e06d70443b774b4923c7ef84af1485b84d3a3eb139d29788
android-platform-tools-apksig_0.5+git168~g10c9d71-1.debian.tar.xz 6.4 KiB dee72cb6b33c98e310d0563f4fcdf775206b0bda58012c194f0e0bd5a4d9183e

No changes file available.

Binary packages built by this source

apksigner: command line tool to sign and verify Android APKs

 apksig is a project which aims to simplify APK signing and checking
 whether APK's signatures should verify on Android. apksig supports
 JAR signing (used by Android since day one) and APK Signature Scheme
 v2 (supported since Android Nougat, API Level 24).
 .
 The key feature of apksig is that it knows about differences in APK
 signature verification logic between different versions of the
 Android platform. apksig can thus check whether a signed APK is
 expected to verify on all Android platform versions supported by the
 APK. When signing an APK, apksig will choose the most appropriate
 cryptographic algorithms based on the Android platform versions
 supported by the APK being signed.
 .
 apksigner command-line tool offers two operations:
 .
  * sign the provided APK so that it verifies on all Android platforms
 supported by the APK. Run apksigner sign for usage information.
 .
  * check whether the provided APK's signatures are expected to verify
 on all Android platforms supported by the APK. Run apksigner verify
 for usage information.
 .
 The tool determines the range of Android platform versions (API
 Levels) supported by the APK by inspecting the APK's
 AndroidManifest.xml. This behavior can be overridden by specifying
 the range of platform versions on the command-line.

libapksig-java: library to sign and verify Android APKs

 apksig is a project which aims to simplify APK signing and checking
 whether APK's signatures should verify on Android. apksig supports
 JAR signing (used by Android since day one) and APK Signature Scheme
 v2 (supported since Android Nougat, API Level 24).
 .
 The key feature of apksig is that it knows about differences in APK
 signature verification logic between different versions of the
 Android platform. apksig can thus check whether a signed APK is
 expected to verify on all Android platform versions supported by the
 APK. When signing an APK, apksig will choose the most appropriate
 cryptographic algorithms based on the Android platform versions
 supported by the APK being signed.
 .
 apksig library offers three primitives:
 .
  * ApkSigner which signs the provided APK so that it verifies on all
 Android platform versions supported by the APK. The range of platform
 versions can be customized if necessary.
 .
  * ApkVerifier which checks whether the provided APK is expected to
 verify on all Android platform versions supported by the APK. The
 range of platform versions can be customized if necessary.
 .
  * (Default)ApkSignerEngine which abstracts away signing an APK from
 parsing and building an APK file. This is useful in optimized APK
 building pipelines, such as in Android Plugin for Gradle, which need
 to perform signing while building an APK, instead of after. For
 simpler use cases where the APK to be signed is available upfront,
 the ApkSigner above is easier to use.
 .
 NOTE: Some public classes of the library are in packages having the
 word “internal” in their name. These are not public API of the
 library. Do not use *.internal.* classes directly.