SSH over HTTPS (trofi.github.io)

Article summary

The article discusses how to pass SSH traffic through HTTPS to bypass restrictive firewalls. This is achieved by tweaking the client and server configurations to use the CONNECT method, allowing SSH traffic to be encapsulated in HTTPS. The author provides examples of how to configure Apache and OpenSSH to achieve this. The method is useful for accessing SSH servers from behind restrictive firewalls that only allow HTTP and HTTPS traffic.

Main themes

• SSH over HTTPS
• firewall bypassing
• protocol encapsulation
• client certificates
• HTTPS as a transport layer
• network restrictions

What commenters say

• Some users prefer HTTP over SSH for its simplicity and ease of use.
• Client certificates can be used for authentication, but their usability is often poor.
• Using SSH over HTTPS can help bypass restrictive firewalls, but may not be necessary if the firewall only blocks specific ports.
• The use of HTTPS as a transport layer for other protocols is becoming more common due to its ubiquity and resistance to deep packet inspection.
• Some argue that the use of non-standard ports and protocols is often blocked by firewalls, making it necessary to use more robust solutions like SSH over HTTPS.
• Others suggest that using a VPN or other encryption methods may be more effective and easier to use than SSH over HTTPS.
• The development of new protocols is hindered by the limitations of the current internet infrastructure, leading to the use of HTTPS as a transport layer for other protocols.