v1.1.0

📰 RELEASE NOTES (v1.1.0)

Release Notes – v1.1.0

🔐 AES-256 Encryption for User Preferences

This release brings first-class support for encrypted user preferences. Use this to securely store sensitive user-specific settings such as API tokens, passwords, or any personal data.

Highlights

• ✅ Encrypt preferences by setting Encrypted: true in your PreferenceDefinition.
• 🔐 AES-256-GCM used with secure nonce handling and base64 output.
• 🌍 Use USERPREFS_ENCRYPTION_KEY environment variable for production configuration.
• 🧪 Secure test harness with NewEncryptionAdapterWithKey() for key injection.
• 🧠 Transparent encryption/decryption logic at Manager layer.
• ⚡ Works seamlessly with memory or persistent storage and caching.

Example Usage

// Define a secure preference
err := mgr.DefinePreference(userprefs.PreferenceDefinition{
    Key:       "api_token",
    Type:      userprefs.StringType,
    Encrypted: true,
})

# Environment setup
```shell
export USERPREFS_ENCRYPTION_KEY="your-secure-32-byte-key-here"

New Components
• encryption.Manager: AES-256-GCM with nonce generation and base64 wrapping.
• EncryptionManager interface: Plug custom encryptors if needed.
• EncryptionAdapter: Bridge between encryption package and preference manager.

Examples Updated
• examples/encryption: CLI example of defining and using encrypted preferences.
• examples/webapp: Realistic web settings including encrypted credentials (GitHub, Slack, personal info).

Security Considerations
• 🔐 Use only cryptographically secure, random keys.
• 🧊 Rotate keys periodically (requires re-encryption).
• 🔍 Decrypted values are cached for performance – memory access controls are recommended in high-security environments.

⸻

TL;DR: With v1.1.0, encrypting user preferences is just a single flag away. You define it, and UserPrefs takes care of secure storage and retrieval for you.