✨ changelog: add version 1.1.0 details including RSA encryption support, secure key storage, and configuration updates; enhance SECURITY.md with key management practices and permissions

Author: abdorrahmani

CHANGELOG.md

@@ -5,6 +5,35 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.1.0] - 2025-05-31
+
+### Added
+- RSA encryption/decryption support
+  - RSA-2048 asymmetric encryption
+  - Public/private key pair generation
+  - Secure key storage in project directory
+  - Base64 encoded output for encrypted data
+- Secure key storage system
+  - Dedicated `keys` directory in project root
+  - Automatic directory creation
+  - Proper file permissions
+  - Cross-platform compatibility
+- Updated configuration system
+  - RSA key size configuration
+  - Key file path management
+  - Improved error handling
+
+### Changed
+- Updated menu system to include RSA encryption
+- Improved key storage security
+- Enhanced documentation
+- Updated project structure
+
+### Fixed
+- Key storage path issues
+- Cross-platform compatibility for key storage
+- File permission handling
+
 ## [1.0.0] - 2025-05-26
 
 ### Added
@@ -52,4 +81,5 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Comprehensive test coverage
 - Code linting with golangci-lint
 
+[1.1.0]: https://github.com/abdorrahmani/cryptolens/releases/tag/v1.1.0
 [1.0.0]: https://github.com/abdorrahmani/cryptolens/releases/tag/v1.0.0 

SECURITY.md

@@ -6,6 +6,7 @@ We currently support the following versions with security updates:
 
 | Version | Supported          |
 | ------- | ------------------ |
+| 1.1.x   | :white_check_mark: |
 | 1.0.x   | :white_check_mark: |
 
 ## Reporting a Vulnerability
@@ -42,12 +43,25 @@ This information will help us triage your report more quickly.
 - Secure communication protocols are used for data in transit
 - Access controls are implemented to protect sensitive information
 - Regular backups are performed with encryption
+- RSA keys are stored with proper file permissions (0600 for private keys)
+- AES keys are stored securely in binary format
+- All encryption keys are stored in a dedicated `keys` directory
+
+### Key Management
+- RSA key pairs are generated with 2048-bit minimum key size
+- Private keys are stored with restricted permissions (0600)
+- Public keys are stored with read-only permissions (0644)
+- Keys are stored in the project's `keys` directory
+- Automatic key generation with secure random number generation
+- Key files are stored in PEM format for RSA keys
+- Cross-platform key storage compatibility
 
 ### Access Control
 - Principle of least privilege is followed
 - Multi-factor authentication is required for sensitive operations
 - Regular access reviews are conducted
 - Session management and timeout policies are enforced
+- File system permissions are properly set for key storage
 
 ## Security Updates
 
@@ -69,6 +83,10 @@ We recommend following these security best practices:
 3. Enable two-factor authentication when available
 4. Regularly review access logs and permissions
 5. Report any suspicious activity immediately
+6. Keep your encryption keys secure and backed up
+7. Use the latest version of CryptoLens
+8. Regularly rotate encryption keys
+9. Monitor the `keys` directory for unauthorized changes
 
 ## Contact