Android Question Signature algorithm version

asubias

Member
Licensed User
Hello all.
Recently my app made with B4A passed a penetration test and one of the issues discovered was:
Signature algorithm v1 used (Janus CVE-2017-13156)
Reference: https://www.guardsquare.com/blog/ne...ithout-affecting-their-signatures-guardsquare

Is it possible to use a newer signature algorithm in B4A?

Kind regards,
Alberto
 

Erel

B4X founder
Staff member
Licensed User
Longtime User
Is this a Google Play app? When you distribute AAB packages the APK is generated on demand and is signed by Google (using your key).

B4A uses the apksigner tool from Android SDK to sign the APK file. It disables v3 and v4 signing features due to compatibility with older devices. You can use the command line builder to build an APK without signing it and then sign it yourself with apksigner.
 
Upvote 0

asubias

Member
Licensed User
Yes, it's a Google Play app.

The company that made the test requested the APK, but as far as I remember, I went to Google Play Console and downloaded the "APK signed and universal" from App Blundles Explorer so it should be signed with the proper signature.

It disables v3 and v4 signing features due to compatibility with older devices
That means that if I want to use the lastest signature algorithm should I use the command line?
 
Upvote 0

asubias

Member
Licensed User
Or package your app as an AAB.
I'm already doing this. That's why I downloaded the APK from the Google Console.
Maybe the issue is that, despite it decode the AAB and provides you with the "signed and universal" APK, it generates the same APK as B4A.
 
Upvote 0
Cookies are required to use this site. You must accept them to continue using the site. Learn more…