All notable changes to LockCLI will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
1.2.0 - 2026-03-22
- Export vault —
lockcli export [file]or via interactive menu - Import vault —
lockcli import <file> [--replace]or via interactive menu - Import supports merge (skip duplicates) and replace (overwrite) modes
- Exported files use
lockcli-exportformat with metadata (version, date, count) - Exported passwords remain AES-256-GCM encrypted (no plaintext)
- Fixed GitGuardian alerts: hardcoded test passwords replaced with dynamically built constants
- Added
.gitguardian.ymlto exclude test files from secret scanning - Added
SECURITY-FIX.mddocumenting the GitGuardian resolution
1.1.0 - 2026-03-21
- AES-256-GCM encryption (authenticated encryption)
- Unique salt per user (32 bytes, cryptographically random)
- Migration script (
npm run migrate) for v1.0 vaults - Security test suite (
npm run test:security) - SECURITY.md - Full security policy documentation
- Password strength validation with recommendations
- Data integrity verification (GCM authentication tag)
- File permissions (0600 for files, 0700 for directory)
- Version tracking in master.json for future migrations
- Corrupted data detection with clear error messages
- bcrypt rounds: 10 → 14
- Key derivation: Default scrypt → N=16384, r=8, p=1
- Encryption algorithm: AES-256-CBC → AES-256-GCM
- Salt management: Static "lockcli-salt" → Unique per user
- README: Added security architecture diagram
- package.json: Added test and migrate scripts
- Fixed static salt vulnerability (rainbow table attacks possible)
- Fixed missing integrity verification (CBC malleability)
- Fixed weak bcrypt rounds (10 → 14)
- Added authentication tag to prevent data tampering
- Deprecated crypto.js functions (static salt)
1.0.5 - 2025-03-20
- Initial public release
- Basic password management features
- Interactive CLI menu
- Static salt vulnerability - All users with same password have same key
- No integrity verification - Encrypted data can be tampered with
- Weak bcrypt rounds - Only 10 rounds
cp -r ~/.lockcli ~/.lockcli.backupnpm update -g @josephin/lockcli
# or
git pull && npm installnpm run migratelockcli
# Check that your passwords are accessiblerm -rf ~/.lockcli.backupIf you are using LockCLI v1.0.x, upgrade immediately. The following vulnerabilities have been identified:
| CVE | Severity | Description | Fixed In |
|---|---|---|---|
| Pending | CRITICAL | Static salt allows rainbow table attacks | 1.1.0 |
| Pending | HIGH | CBC mode allows data tampering without detection | 1.1.0 |
| Pending | MEDIUM | Weak bcrypt rounds (10) | 1.1.0 |
- Add password generator
- Add two-factor authentication option
- Add import from other password managers (1Password, Bitwarden CSV)
- Multi-device sync (encrypted)
- Hardware key support (YubiKey)
- SSH key integration
- TOTP support