Native API Security with NativeScript
summary
Shows that JavaScript can generate a crypto key, encrypt a JWT and either store it in SQLite (where a copied device container reveals it) or place it in a hardware-backed enclave gated by biometrics. Uses OS key stores, platform crypto and the community Navoccript Secure Storage plugin plus a biometric plugin to require Face/Touch ID. Demonstrates a working example on GitHub, warns that plugin audits, API levels and platform differences remain necessary to keep this secure.
AI-written summary · about
chapters (12)
- 0:00NativeScript security intro
- 1:27JavaScript security risks
- 2:54NativeScript vs browser security
- 4:03Secure storage with enclaves
- 5:25NativeScript platform access
- 6:30Secure storage plugins
- 7:13Biometric protection
- 8:18Summary
- 8:39Q&A
- 10:50Security advantages over JS
- 12:39Cross-platform trade-offs
- 14:08Closing
related talks
58mBuilding JavaScript and mobile/native Clients for Token-based Architectures
23mTopics of Interest: React Native Security. Addressing typical mistakes
45mPasswords Are So 1990
24mPasswords are so 1990
23mKeeping secrets with JavaScript
28mModern security for Android Developers
46mWhat Can Traditional Web App Security Learn From Browser Wallet Extensions?
23mProtecting Sensitive Data in Web Apps