apksigner fails to sign when keystore and key passwords differ and apksigner isn't explicitly told how to obtain the passwords [37134986]

Fixed

Bug

[AOSP] assigned

Status Update

No update yet.

Description

kl...@google.com

created issue #1

Feb 3, 2017 09:24PM

When apksigner is invoked without explicitly specifying how to obtain the keystore and key password, apksigner prompts for keystore password and uses that as the key password as well, making it impossible to use keystores where the keystore password differs from key password. A workaround is to explicitly tell apksigner how to obtain these two passwords. For example, --ks-pass=stdin --key-pass=stdin will force apksigner to prompt for keystore password and then prompt for key password.

STEPS TO REPRODUCE
1. Create a keystore where the keystore password is different from key password.
2. apksigner sign --ks keystore.jks some.apk

EXPECTED RESULTS
apksigner prompts for keystore password, then prompts for key password

ACTUAL RESULTS
apksigner prompts for keystore password, then fails claiming that it can't obtain the key because "Wrong password?"

Comments

kl...@google.com <kl...@google.com> #2Feb 15, 2017 08:36PM

Hi,

would you try to boot emulator with this command line flag:

-feature -Vulkan

and let us know if it fixes the issue for you? Also would you tell us what graphics card you are using and what is the graphics driver version?

kl...@google.com <kl...@google.com> #3Mar 7, 2017 05:28AM

The feature flag did solve the issue for me. Thank you very much. I don't use a dedicated graphics card. Only the internal one from the CPU.

kl...@google.com <kl...@google.com> #4Apr 24, 2017 06:23PM

Your integrated GPU is supposed to support Vulkan 1.2. I would need more work to figure out why it crashes without that flag.

cb...@google.com <cb...@google.com> Apr 24, 2017 06:24PM

Marked as fixed.

ba...@gmail.com <ba...@gmail.com> #5May 7, 2017 02:23AM

If there is more information that I can provide please let me know.

pr...@gmail.com <pr...@gmail.com> #6May 24, 2017 04:12PM

Thanks. Would you help me to try some more runs to isolate the root cause? Please try to run the emulator with this flag:

-feature -GLDirectMem,-GLDMA,-GLDMA2

I am suspecting the Vulkan direct memory access and coherent mapping is causing the issue.

82...@gmail.com <82...@gmail.com> #7Jan 4, 2019 06:15PM

+cc rkir@