talsec
16kb page size support
Dears,
Google is progressively enforcing apps to support devices with 16kb page size:
https://developer.android.com/guide/practices/page-sizes
Following the instructions in the above link I have seen that there are some libraries that are used by Talsec that are not compliant with 16kb page size:
/lib/arm64-v8a/libsecurity.so: \e[31mUNALIGNED\e[0m (212) /lib/arm64-v8a/libpolarssl.so: \e[31mUNALIGNED\e[0m (212) /lib/arm64-v8a/libclib.so: \e[31mUNALIGNED\e[0m (212) /lib/arm64-v8a/libpbkdf2_native.so: \e[31mUNALIGNED\e[0m (212)
The test I passed is described in this section:
https://developer.android.com/guide/practices/page-sizes
Is there any plan to make your libraries support 16kb page size?
Thanks,
Hello @xavierserrai ,
we are currently working on this support.
Kind regards, Talsec team
Dears,
Is 16kb issue fixed on version 7.0.0? I cannot see it in changelog.
Thanks,
Hi @xavierserrai , Not yet. Did you register any 16kb enabled devices already? Transition to 16kb-only devices may take a little bit longer as enforcing this too soon would break almost every mobile app today. Thank you, Tomas
Hi @SirionRazzer , I have not seen any physical 16kb device but as soon as they appear and 16kb is enabled any piece of code that is not ready for that will blow up the app when executed. We have almost completed our transition to 16kb support.
Thanks,
Hello @xavierserrai ,
status: we are still working on the support of the 16kb devices.
Kind regards, Talsec team
May I check what is the estimated date for the next release? @SirionRazzer
Hi guys,
This is becoming more and more urgent as Android will start enforcing this soon and I still see the error message with the following libs:
lib/arm64-v8a/libclib.so lib/arm64-v8a/libpbkdf2_native.so lib/arm64-v8a/libpolarssl.so lib/arm64-v8a/libsecurity.so lib/arm64-v8a/libtmlib.so
Do we have an ETA yet on when this update will happen?
Thanks
