Skip to content

Release v0.2.2

Choose a tag to compare

@blocksorg blocksorg released this 04 Nov 05:15
· 13 commits to main since this release

MigChat CLI v0.2.2

Critical Bug Fixes

πŸ”’ Fixed MAC Verification Failure (Issue with all encrypted messages)

  • Fixed critical bug where encryption used a random nonce but decryption used a zero nonce
  • This caused "MAC verification failed" errors even with newly created accounts
  • Now properly prepends nonce (12 bytes) to ciphertext and extracts it during decryption
  • MAC computation now includes nonce+ciphertext consistently on both sides
  • All users should upgrade immediately - this fixes message decryption for all encrypted conversations

πŸͺŸ Fixed Windows PowerShell Installer

  • Simplified color output functions for better compatibility when piped through `iex`
  • Replaced box-drawing characters with ASCII for better terminal compatibility
  • Added detailed error output with stack traces for debugging
  • Added `-UseBasicParsing` to API calls for better compatibility
  • Installer should now work reliably in all PowerShell environments

Installation

Quick Install (Linux/macOS):
```bash
curl -fsSL https://raw.githubusercontent.com/migchat/cli/main/install.sh | bash
```

Quick Install (Windows):
```powershell
irm https://raw.githubusercontent.com/migchat/cli/main/install.ps1 | iex
```

Manual Installation:

  1. Download the binary for your platform below
  2. Rename it to `migchat` or `migchat.exe` (remove platform suffix)
  3. (Unix only) Make it executable: `chmod +x migchat`
  4. Move it to a directory in your PATH

Supported Platforms

  • Linux x86_64 (with desktop notifications)
  • Linux aarch64/ARM64 (with desktop notifications)
  • macOS x86_64 (Intel)
  • macOS aarch64 (Apple Silicon)
  • Windows x86_64
  • Windows aarch64/ARM64

Breaking Changes

⚠️ Important: Due to the nonce handling fix, messages encrypted with v0.2.1 or earlier cannot be decrypted with v0.2.2. However, new sessions will work correctly. If you have existing encrypted conversations, both parties should upgrade to v0.2.2 and start new conversations.