get_secure_storage_plus 2.0.0

A fast, extra-light, synchronous key-value storage with production-grade AES-GCM-256 encryption. A highly secure alternative to get_storage.

2.0.0

• Security Upgrade (AES-GCM-256): Replaced AES-CTR-128 and HMAC-SHA256 with natively authenticated AES-GCM-256.
• Security Upgrade (Embedded Salt): Removed separate .salt files. A 32-byte cryptographically secure salt is now generated once and embedded natively into the encrypted JSON payload, making storage files fully portable.
• Security Upgrade (PBKDF2-SHA256): Strengthened key derivation using PBKDF2-SHA256. Default platform-optimized iteration counts are divided by 10 (10k Web, 20k Mobile, 30k Desktop) to drastically reduce application initialization latency. For maximum security, developers can manually pass passwordIterations: 600000 to meet strict OWASP 2025 standards.
• Security Upgrade (Nonce): A fresh 12-byte nonce is automatically generated on every single disk write to prevent nonce-reuse vulnerabilities.
• Security Upgrade (Memory Protection): GetSecureStorage.dispose() now explicitly zero-fills AES secret keys from memory before Garbage Collection to stop RAM-dump sniffing.
• Fix (Platform Native Flushes): flush() writes are now bounded by a 5-second timeout to prevent permanent blocking in the microtask queue, and native OS locks are safely released via closeFile().
• Fix (Data Racing): Rewrote clear() to safely await disk flushes.
• Fix (Migration): Added __v to payload schema for future-proofing format upgrades. Old v1 payloads are now seamlessly decrypted and reliably migrated to the v2 format without any data loss!

1.0.2

• Incremental updates and fixes.

1.0.1

• Initial release