Ubuntu
android-platform-tools-apksig package

android-platform-tools-apksig 0.8-1 source package in Ubuntu

Changelog

android-platform-tools-apksig (0.8-1) unstable; urgency=medium

  * New upstream release from tag android-8.1.0_r14

 -- Hans-Christoph Steiner <email address hidden>  Wed, 21 Feb 2018 21:28:29 +0100

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
Bionic release universe misc

Builds

Bionic: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
android-platform-tools-apksig_0.8-1.dsc 2.0 KiB 7d7fe8e5d67fdaf89e6019b9c6c82fac4ba6651f066e844d7358c98565c3923b
android-platform-tools-apksig_0.8.orig.tar.gz 576.1 KiB 98a40d680caf0fdd1aa7ca15c837e59d8c76376f65dade5843fbc3727c8afc09
android-platform-tools-apksig_0.8-1.debian.tar.xz 7.0 KiB 6eae06b54336be6e62684b2de858768b05177f08ec0ebfef813c3b24522cfedf

Available diffs

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.