Skip to content

Release v0.2.0 - CRITICAL SECURITY FIX: Per-Account Encryption

Choose a tag to compare

View all tags
@blocksorg blocksorg released this 04 Nov 00:57
· 20 commits to main since this release
v0.2.0
b4db547

MigChat CLI v0.2.0 - CRITICAL SECURITY FIX

🔴 CRITICAL: Per-Account Encryption Keys

This is a major security release that fixes a critical vulnerability where all accounts shared the same encryption keys.

Security Issue Fixed

Severity: CRITICAL 🔴
CVE: N/A (internal discovery)
Affects: v0.1.8, v0.1.9

All user accounts on the same machine were sharing identical encryption keys, meaning:

  • ❌ All accounts had the same fingerprint
  • ❌ Any account could decrypt messages meant for other accounts
  • ❌ Key verification was meaningless (all verified the same key)
  • ❌ If one account was compromised, ALL accounts were compromised

Solution

Each account now has unique encryption keys stored separately:

Before (INSECURE):

~/.config/migchat/keys/           # ❌ Shared by ALL accounts
  ├── identity_key.enc
  └── signed_prekey.enc

After (SECURE):

~/.config/migchat/keys/
  ├── alice/                      # ✅ Alice's unique keys
  │   ├── identity_key.enc
  │   └── signed_prekey.enc
  └── bob/                        # ✅ Bob's unique keys
      ├── identity_key.enc
      └── signed_prekey.enc

🔒 What's Fixed

Per-Account Encryption

  • ✅ Each account has unique encryption keys
  • ✅ Keys stored in ~/.config/migchat/keys/{username}/
  • ✅ Sessions isolated per account: ~/.config/migchat/sessions/{username}/
  • ✅ Different accounts have different fingerprints
  • ✅ Account isolation enforced
  • ✅ Multi-account setup is now secure

Architecture Changes

Core Crypto Modules:

  • Added EncryptionManager::for_account(username) method
  • Added KeyManager::for_account(username) method
  • Added SessionManager::for_account(username) method

UI Updates:

  • Changed encryption: EncryptionManager → Option<EncryptionManager>
  • Encryption manager switches when switching accounts
  • Account-specific initialization on login/creation
  • Safe access via ensure_encryption() helpers

📝 Changes

Security Fixes

  • [CRITICAL] Per-account encryption keys (#9, #10)
  • [CRITICAL] Account isolation for encryption sessions

Bug Fixes

  • Fixed compilation errors in encryption implementation
  • Fixed borrow checker issues with token handling
  • Fixed type mismatches in API method calls

Commits Since v0.1.9

  • 21bf295: Complete per-account encryption implementation
  • 3aa5543: Fix compilation errors in per-account encryption
  • f8b271a: Fix all remaining compilation errors
  • b4db547: Bump version to 0.2.0

Full Changelog: v0.1.9...v0.2.0

🚨 Action Required for Existing Users

Single-Account Users

  • ✅ No action needed - Your setup will continue to work
  • Your keys will remain in the default location

Multi-Account Users

  • ⚠️ Important: Your old accounts may have been using shared keys
  • Recommended Actions:
    1. Download the new v0.2.0 binary
    2. Log into each account
    3. Generate new keys (log out and log back in)
    4. Verify your new fingerprints with contacts
    5. Consider rotating keys if you suspect compromise

Migration Details

First account to log in:

  • May retain old global keys (backward compatible)

Subsequent accounts:

  • Will generate new unique keys automatically

Best Practice:

  • Regenerate keys for all accounts to ensure proper isolation
  • Verify fingerprints with all contacts after upgrade

🔐 Security Best Practices

After upgrading:

  1. ✅ Log out and log back into each account to ensure keys are per-account
  2. ✅ View your fingerprint (Security → View My Fingerprint)
  3. ✅ Verify it's different for each account
  4. ✅ Share new fingerprints with your contacts
  5. ✅ Have contacts verify your new fingerprints

📊 Testing

Verified functionality:

  • ✅ Each account generates unique keys
  • ✅ Different accounts have different fingerprints
  • ✅ Account isolation enforced
  • ✅ Multi-account encryption works securely
  • ✅ Backward compatibility with single-account setups
  • ✅ All builds passing on all platforms

🛡️ Security Properties

Before v0.2.0

  • 🔴 Shared keys across all accounts
  • 🔴 No account isolation
  • 🔴 Compromised security model

v0.2.0 and Later

  • ✅ Unique keys per account
  • ✅ Full account isolation
  • ✅ Secure multi-account support
  • ✅ Proper fingerprint verification
  • ✅ Forward secrecy maintained

📦 Installation

Upgrading from v0.1.x:

  1. Download the new binary for your platform
  2. Replace your existing binary
  3. Important: Log out and log back in to each account

Quick Install (Linux/macOS):

curl -fsSL https://raw.githubusercontent.com/migchat/cli/main/install.sh | bash

Quick Install (Windows):

irm https://raw.githubusercontent.com/migchat/cli/main/install.ps1 | iex

🔗 Related Issues

  • Closes #9: CRITICAL: All accounts share the same encryption keys
  • PR #10: Per-account encryption implementation

Priority: P0 - Critical Security Fix
Type: Security, Breaking Change (internal)
Impact: All users with multiple accounts
Recommendation: Upgrade immediately if using multiple accounts

Assets 8
Loading