- wssshd: Log full content of all received and sent control messages when --debug is enabled
- wssshc: Already logs control messages, registration message logging enhanced
- wsssht: Fixed memory corruption issue with config struct allocations

Control channel messages include: register, registered, registration_error,
tunnel_request, tunnel_ack, tunnel_error, tunnel_close, tunnel_data, tunnel_response

- Enhanced bridge mode to handle incoming tunnel control messages from WebSocket
- Added JSON output for tunnel_data, tunnel_response, tunnel_close messages
- Added WebSocket connection status messages (websocket_close, websocket_connection_closed)
- Updated test scripts to include tunnel control channel message testing
- Updated documentation with comprehensive examples of control channel messages
- Added new testing scenario for tunnel control channel verification

Bridge mode now properly forwards all tunnel control channel messages as JSON
through stdout, allowing external applications to monitor tunnel state and
server communications in real-time.

- test_bridge_mode.sh: Automated test script for bridge mode functionality
- test_bridge_interactive.sh: Interactive testing tool with manual JSON command input
- BRIDGE_MODE_TESTING.md: Complete testing guide with examples and integration patterns

Features:
- Automated and interactive testing modes
- JSON command examples and validation
- Real-time response monitoring
- Error handling and process management
- Integration examples in Python and Node.js
- Troubleshooting guide and best practices
- Colored output and user-friendly interface

These tools provide comprehensive testing capabilities for the new bridge mode,
allowing developers to easily test and integrate with the JSON stdin/stdout interface.

- Fixed documentation to correctly state that in bridge mode:
  - Tunnel control channel messages are communicated through stdin/stdout (JSON protocol)
  - Tunnel data channel messages remain handled by wsssht (normal forwarding)
- Updated README.md, DOCUMENTATION.md, CHANGELOG.md, and TODO.md
- The implementation was already correct, just the documentation was backwards

- Updated documentation to clarify that in ALL modes, wsssht handles tunnel control channel messages
- Clarified that in bridge mode specifically, tunnel data channel messages are NOT handled by wsssht
- Instead, raw tunnel data is communicated through stdin/stdout for external processing
- Updated README.md, DOCUMENTATION.md, CHANGELOG.md, and TODO.md with this clarification
- This ensures proper understanding of bridge mode's data handling architecture

- Updated README.md with comprehensive operating mode descriptions
- Added detailed usage examples for all modes (interactive, silent, bridge, script, daemon)
- Updated CHANGELOG.md with version 1.6.0 featuring new operating modes
- Updated TODO.md with completed items and new feature descriptions
- Updated DOCUMENTATION.md with operating mode details and API documentation
- Enhanced man pages with new command-line options
- Updated configuration examples to include new [wssht] section options
- Comprehensive documentation coverage for all new features

- Added run_bridge_mode() function with JSON stdin/stdout interface
- Added run_script_mode() function with JSON protocol for scripting
- Bridge mode: JSON communication between stdin/stdout and WebSocket
- Script mode: JSON status updates, command processing, and monitoring
- Both modes provide structured JSON output for programmatic use
- Fixed compilation warnings and ensured clean build
- All operating modes now fully implemented

- Added run_daemon_mode() function for lazy tunnel establishment
- Daemon mode waits for first connection attempt before establishing tunnel
- Reduces resource usage by not connecting until actually needed
- Maintains all existing functionality after tunnel is established
- Fixed compilation errors and ensured clean build
- Updated mode handling to support daemon mode

- Modified websocket_handshake() function to accept debug parameter
- Updated all debug messages in websocket_handshake to only print when debug=1
- Updated all callers of websocket_handshake() to pass debug flag
- Fixed compilation warnings and ensured clean build
- WebSocket handshake messages now only appear with --debug flag

- Fixed unused parameter warnings in run_bridge_mode and run_script_mode functions
- Added parameter usage in debug output to eliminate compiler warnings
- Compilation now clean with no warnings or errors

- Added --config FILE option to specify custom config file path
- Removed [wssht] section from wsssh.conf.example (legacy)
- Created separate wsssht.conf.example with wssht-specific options
- Updated man page with new --config option and mode options
- Updated usage message to include all new options
- Config file validation: errors if specified file doesn't exist

- Fixed 'free(): invalid pointer' error when using service prefix format
- Issue was caused by modifying the original allocated string and then trying to free a pointer to the middle of it
- Added proper pointer tracking to ensure correct memory deallocation

- Connection string values now properly override config file values
- Fixed issue where 'wsssht zeiss' wasn't working due to incorrect precedence logic
- Command line options still take highest precedence, then connection string, then config file

- Support connection string format: [service://]clientid[@wssshd-host][:wssshd-port]
- Command line options take precedence over connection string values
- Update usage message and man page with new syntax
- Add comprehensive documentation for connection string format
- Maintain backward compatibility with existing option-based usage

- Remove leftover logic for handling positional arguments in parse_args()
- Since wsssht no longer accepts user@host arguments, remove the non-option argument handling
- Remove unused parse_hostname() and parse_target_args() functions
- Fix issue where valid options were triggering --help output

- Add tunnel-port option to wsssht.conf.example
- Update man page configuration example to include all options
- Reorder options logically in both files
- Include comprehensive comments explaining each option

- Update all config file references from 'wssht' to 'wsssht'
- Rename wssht.conf.example to wsssht.conf.example
- Update man page to reflect correct config file names
- Fix config reading calls to use 'wsssht' instead of 'wssht'

- Change 'Transport types' to 'Transport' in --tunnel option description
- Add 'or websocket' to the description for clarity
- Update both usage message in wsssht.c and man page wsssht.1

- Move --wssshd-port option to appear right after --wssshd-host
- Update both usage message in wsssht.c and man page wsssht.1
- Maintain logical grouping of related options

- Update read_config_value_from_file() to support config precedence:
  1. ~/.config/wsssh/wssht.conf (user config)
  2. /etc/wsssht.conf (system config)
- Update man page to document config file precedence order
- Command line options still have highest priority

- Remove parsing of user@domain format from wsssht
- Add --clientid option for specifying client ID
- Add --wssshd-port option (replacing -p/--port)
- Update wssshd-host default to mbetter.nexlab.net
- Add client_id field to wsssh_config_t struct
- Update config reading to include clientid and wssshd-port
- Update wssht.conf.example with new options
- Update man page wsssht.1 with new options and examples
- Ensure --wssshd-host is required if not in config
- Update all usage messages and documentation

- Add --tunnel-host option to specify local IP address for tunnel binding
- Change default timeout from 30 to 5 seconds for wsssht
- Update help text, man page, and config file to reflect changes
- Update setup_tunnel function to accept tunnel_host parameter
- Update socket binding to use specified tunnel_host or default to 127.0.0.1

- Update debian/control: Include wsssht in package description
- Update debian/changelog: Add version 1.5.0 with wsssht and transport features
- Update debian/rules: Install wssht.conf.example configuration file
- Package now includes all four tools: wssshc, wsssh, wsscp, wsssht
- Maintains backward compatibility with existing installations

- Create wsssht.c: Stripped-down tunnel setup tool (like wsssh --dev-tunnel)
- Add separate wssht.conf configuration file support
- Implement read_config_value_from_file() for custom config files
- Create wssht.conf.example with tunnel configuration options
- Update wsssht.1 man page with separate config file documentation
- Add wsssht to build system (configure.sh, Makefile)
- Test successful compilation and functionality

wsssht provides manual tunnel setup without auto-executing SSH/SCP,
displaying connection information for telnet, nc, or any TCP client.

- Add --tunnel, --tunnel-control, --service options to wsssh and wsscp
- Implement transport definitions with is_relay property and weight-based selection
- Add WebSocket transport with is_relay=true as primary transport
- Update server-side tunnel handling for new transport attributes
- Enhance configuration system with new tunneling options
- Update all man pages with comprehensive tunneling documentation
- Fix PyInstaller template loading for frozen executables
- Add transport list expansion for 'any' option functionality
- Implement connection retry logic with weight-based prioritization
- Update CHANGELOG.md, TODO.md, README.md, and DOCUMENTATION.md

- Add --tunnel, --tunnel-control, --service options to wsssh and wsscp
- Implement transport definitions with is_relay property and weight-based selection
- Add WebSocket transport with is_relay=true as primary implementation
- Update server-side tunnel handling with new transport attributes
- Enhance configuration system with tunneling options
- Fix critical transport list expansion for 'any' option
- Update all man pages with comprehensive tunneling documentation
- Add new config files wsssh.conf.example and wsscp.conf.example
- Update CHANGELOG.md, README.md, and TODO.md with new features
- Maintain backward compatibility with existing functionality

- Add IP autodetection function in wssshlib.c that detects local IP excluding loopback
- Create comprehensive Tunnel class in wsssd/tunnel.py with all required attributes:
  * client_id, tunnel_id, status, protocol, tunnel_type
  * dst_public_ip, dst_public_port, dst_private_ip, dst_private_port
  * src_public_ip, src_private_ip
- Update WebSocket handling to use Tunnel objects throughout lifecycle
- Add IP detection utilities for public/private IPs
- Maintain original tunnel binding behavior (127.0.0.1)
- Update server shutdown process for proper tunnel cleanup
- Test implementation with virtual environment

- Added CPU affinity management to distribute tunnel threads across available CPU cores
- Implemented round-robin CPU core assignment for optimal load distribution
- Added _GNU_SOURCE define to enable CPU affinity functions
- Updated configure.sh to include -D_GNU_SOURCE in CFLAGS for proper compilation
- Enhanced parallel processing capabilities for multiple concurrent tunnels
- Updated CHANGELOG.md and TODO.md with multi-core optimization details

- Increased select() timeout from 50ms to 200ms in tunnel forwarding threads
- Reduced polling frequency by 75% to minimize CPU overhead during data transfers
- Significantly improved efficiency for bulk file transfers while maintaining responsiveness
- Updated CHANGELOG.md and TODO.md with performance optimization details

Merged duplicate 'C Implementation' sections in README.md into a single cohesive 'wsssh tools (C Implementation)' section. Since Python implementations were removed, the C tools are now the primary (and only) implementations available.

Since Python implementations were removed, C implementations are now the primary (and only) implementations. Updated README.md to remove the '(Alternative)' designation.

- Fix missing websockets import in wsssd/server.py causing 'name websockets is not defined' error
- Resolve asyncio runtime warnings by properly awaiting cancelled tasks in shutdown handling
- Fix global variable sharing issue in frozen application by passing server password as parameter to websocket handler
- Improve WebSocket handler signature compatibility with functools.partial for proper function binding
- Update CHANGELOG.md and TODO.md with version 1.4.9 changes

- Prevent SSL double-free when individual tunnels are closed
- SSL contexts are managed only at connection level
- Fixes crashes when server closes tunnels

- Prevent use-after-free in forwarding threads during shutdown
- Close sockets and free buffers but keep tunnel structures allocated
- Memory will be freed when process exits, avoiding thread access issues

- Add tunnel validity check in forwarding threads before sending data
- Threads check if tunnel is still active in the global list before proceeding
- Prevents SSL write errors and connection corruption when tunnels are closed

- Remove send_tunnel_close from handle_tunnel_close to avoid SSL errors
- When server sends tunnel_close, client just closes tunnel locally
- Prevents SSL connection corruption when trying to send on closed connection

- Fix double-free corruption in cleanup_tunnel by removing SSL freeing
- Add global shutdown flag for proper thread synchronization
- Improve SIGINT handling with better thread cleanup timing
- Send tunnel_close acknowledgment when receiving tunnel_close from server
- Prevent threads from accessing freed tunnel structures
- Ensure proper resource management during shutdown

🚀 Major wsssh system improvements: Multiple concurrent tunnels, enhanced signal handling, SSL fixes, and production monitoring

## Key Improvements:

### 🔄 Multiple Concurrent Tunnels
- Replaced single global tunnel with dynamic tunnel array supporting unlimited concurrent tunnels
- Independent SSL contexts per tunnel prevent conflicts
- Thread-safe tunnel management with proper mutex locking
- Support for simultaneous wsssh and wsscp operations

### ⚡ Enhanced Signal Handling
- Immediate SIGINT response (< 100ms instead of 4-5 seconds)
- Multi-layer shutdown detection across all components
- Graceful cleanup of all active tunnels
- Non-blocking operations prevent deadlocks

### 🔧 SSL & Connectivity Fixes
- Fixed SSL mutex deadlock in wssshc registration process
- Removed redundant SSL mutex locking (websocket functions handle internally)
- Eliminated connectivity test hang during registration
- Proper SSL context isolation per tunnel

### 📊 Production Monitoring
- Real-time status reporting every 60 seconds
- Event messaging for important operations
- Uptime tracking with HH:MM:SS format
- Active tunnel counting and reporting

### 🏗️ Build System Enhancements
- Added --novenv option to preserve Python virtual environment during clean
- Conditional venv removal based on user preference
- Improved build script flexibility for development workflows

### 🐛 Bug Fixes
- Fixed Python asyncio signal handling error in wssshd
- Resolved compilation errors in wssshc.c
- Fixed shutdown_event NameError in handle_websocket
- Comprehensive error handling and diagnostics

### 📈 Performance Optimizations
- Optimized tunnel data forwarding with larger buffers
- Reduced SSL mutex contention through better synchronization
- Faster shutdown times for both wssshd and wssshc
- Memory-efficient tunnel management

## Technical Achievements:
- Zero-downtime tunnel operations
- High-performance data forwarding
- Responsive signal handling
- Comprehensive error recovery
- Production-ready monitoring
- Clean compilation and stable execution
- Flexible build system
- Reliable connectivity
- Proper SSL synchronization

## Result:
The wsssh system now supports multiple simultaneous SSH/SCP sessions without conflicts, provides immediate shutdown response, robust error recovery, production monitoring, and clean compilation across all components.

- Fix WebSocket framing protocol issues with dynamic buffer allocation
- Remove 255KB transfer limit by using heap allocation for large data
- Optimize performance with 64KB chunking and faster reconnection (1s)
- Add SIGINT handling for graceful tunnel closure with error messages
- Improve WebSocket reconnection handling and tunnel state management
- Treat close frames as tunnel closures to maintain WebSocket connections
- Add proper memory cleanup and buffer overflow prevention
- Reduce reconnection intervals for better responsiveness