That was exactly what I was asking, thanks for the testing. My guess is that
upstream has fixed this in newer releases. There is work underway to update
this package. Plus there is a newer version available in bullseye-backports:
31.0.2-1~bpo11+1: all
For the record, Debian's apksigner works without issues after installing Java 8
and marking it as default with update-alternatives. This is definitely a
compatibility issue that might need to be fixed either upstream or as a patch.
Danilo
With upstream I assume you mean the apksigner binary shipped with the Android
build-tools? I tried with build-tools 30.0.2:
$ /opt/android/cmdline-tools/tools/bin/sdkmanager --install
"build-tools;30.0.2"
Followed by:
$ /opt/android/build-tools/30.0.2/apksigner sign \
--ks NONE
Thanks for the detailed bug report. Have you tried using the Google binaries?
Does this also happen there? IIRC upstream fixed some bugs related to
smartcards in recent releases.
Package: apksigner
Version: 30.0.3-4
Severity: important
When trying to use apksigner on Debian 11 in combination with a
hardware HSM (YubiHSM 2 in my case) through SunPKCS11, signing fails
with an error message:
$ apksigner sign \
--ks NONE --ks-type PKCS11 \
--ks-pass
5 matches
Mail list logo
