v2.3.1

Patch release: fixes the broken blog-post link in the README. No code changes since v2.3.0.

v2.3.0

More robust ti.cloak key extraction (#13)

The KEY_BLOCK offset inside libti.cloak.so varies by ABI/SDK/compile flags
(arm64 0x2008, x86 0x2004, x86_64 0x2010, armeabi-v7a 0x3004/0x4004),
so hardcoding 0x2008 only worked when an arm64-v8a lib was present. It's now
resolved from the ELF's exported KEY_BLOCK symbol via a small built-in
ELF32/ELF64 parser, with the known per-ABI offsets as a fallback and every
candidate still validated by trial decryption.

This fixes recovery for armeabi-v7a / x86 / x86_64-only and ABI-split
(App Bundle) APKs.

Thanks @j4k0xb for the detailed report and offset
table (#13).

Added

• New exported helpers: extractKeyBlock, deriveKeyFromBlock,
  cloakKeyCandidates.
• Synthetic ELF32/ELF64 tests placing KEY_BLOCK at non-standard offsets.

No breaking changes — deriveCloakKey / pickCloakKey keep the same signatures.

npm: https://www.npmjs.com/package/titanium-apk-recover/v/2.3.0