fix(android): declare KeySpec so the native PBKDF2 call resolves, and report why it fails
generateSecret takes a KeySpec; passing a JObject made the bridge emit a signature no method matches, and the call failed at runtime. Swallowed as 'unavailable', which hid my own mistake for a full test round - the failure now carries its exception message. Measured on device: the Pascal PBKDF2 takes 6651 ms, unusable per unlock. AES-GCM through JNI works, plaintext and hash match the vector, so the container format is validated end to end.
This commit is contained in:
@@ -0,0 +1,14 @@
|
||||
<vector xmlns:android="http://schemas.android.com/apk/res/android"
|
||||
android:width="24dp"
|
||||
android:height="24dp"
|
||||
android:viewportWidth="24"
|
||||
android:viewportHeight="24">
|
||||
<group>
|
||||
<path
|
||||
android:fillColor="#BF311A"
|
||||
android:pathData="M4.86 16.35C4.2 6.8 16.68 5.5 16.36 0c2.91 5.67-8.1 9.4-5.02 12.95 1.88 2.19 8.26-3.4 7.12-8.42 4.21 10.04-11.98 15.71-2.74 19.27-5.84 1.14-10.57-3.12-10.86-7.45Z"/>
|
||||
<path
|
||||
android:fillColor="#F3901D"
|
||||
android:pathData="M4.84 16.38c-0.23-5.25 2.43-7.45 6.78-10.55-5.67 4.53-5.34 9.23-4.37 12 0.97 2.76 3.88 6.3 8.42 5.98-5.82 1.15-10.42-3.06-10.83-7.43Z"/>
|
||||
</group>
|
||||
</vector>
|
||||
Reference in New Issue
Block a user