A QUIC proxy that enables SSH connections over QUIC without patching client or server.
quicssh is a proxy tool that enables SSH connections to be tunneled over the QUIC protocol instead of TCP. It solves the problem of SSH performance and reliability in poor network conditions by leveraging QUIC's features like multiplexing and reduced latency, without requiring changes to SSH clients or servers.
System administrators, DevOps engineers, and developers who frequently use SSH in unstable or high-latency network environments and want to improve connection reliability.
Developers choose quicssh because it provides a drop-in solution to modernize SSH with QUIC's benefits, offering potential performance improvements and better handling of packet loss without the complexity of patching SSH implementations.
SSH over QUIC
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Works with standard SSH clients and servers using ProxyCommand, as shown in the architecture diagram, eliminating the need to patch or update existing SSH implementations.
Leverages QUIC's UDP-based protocol to reduce latency and improve reliability in unstable networks, addressing packet loss and connection drops common with TCP-based SSH.
Available as a Docker image for easy setup and self-hosting, simplifying server installation and management, as indicated by the Docker badges in the README.
Uses a clear client-server model that seamlessly integrates with SSH workflows, demonstrated in the usage examples with minimal configuration changes.
Relies on UDP for QUIC, which may be blocked or restricted in corporate or controlled networks, limiting its applicability in some environments.
Requires running separate client and server components and configuring ProxyCommand, adding steps and potential points of failure compared to direct SSH connections.
The README is minimal and lacks details on advanced SSH features like agent forwarding or SCP support over the proxy, which could hinder adoption for complex workflows.
Introducing a proxy layer might add latency, especially if the quicssh server is not optimized, despite QUIC's benefits, as it's an extra hop in the connection path.