ClipWizard 0.5.0

ClipWizard Changelog

Version 0.5.0

Improvements

• Storage System Simplification:

  • Removed JSON to SQLite migration path
  • Made SQLite the sole storage backend for all users
  • Fixed various storage-related bugs and crashes
  • Improved database access to prevent deadlocks

• UI Refinements:

  • Enhanced Storage settings layout to match other settings tabs
  • Improved spacing and padding consistency across the interface
  • Better visual organization of storage statistics
  • Added welcome information for new users

Technical Improvements

• Fixed critical database operations deadlock that caused crashes
• Corrected memory management issues related to notification handling
• Enhanced clipboard monitor implementation with more robust memory handling
• Improved thread safety for database operations
• Implemented queue detection to prevent recursive deadlocks

Benefits

• Significantly improved application stability
• Eliminated JSON storage-related migration issues
• Enhanced user experience with consistent UI styling
• More reliable clipboard operations

Sanitization New Features

• Enhanced Sanitization System:
  • Priority-based rule processing system to ensure most specific rules run first
  • Support for detecting and sanitizing additional sensitive data formats:
    • JWT tokens
    • GitHub personal access tokens
    • AWS-style access keys
    • Generic secret keys with varied formats
  • New connection string detection for URI-style database connections (user:password@host format)
  • Conversational format detection for passwords and API keys
  • Minimum length checks to prevent false positives on short strings

Improvements

• Enhanced sanitization patterns and algorithm:
  • Improved regex patterns for all rule types to catch more variations and formats
  • Password detection now recognizes phrases like "account password is" and variants
  • API key detection now captures references like "My API key is..."
  • Connection string detection now supports both parameter-style and URI-style formats
  • Sanitization algorithm now targets specific sensitive data portions rather than entire matches
  • Better capture group handling to focus on the sensitive parts of matches
  • More comprehensive rule set with improved coverage for edge cases

Fixes

• MongoDB and PostgreSQL connection strings with user:password format now properly sanitized
• Mixed context references to passwords and API keys now detected
• Quoted strings containing sensitive data now properly identified
• Various edge cases where sensitive data wasn't being properly identified