piping-ssh-web
yamux
piping-ssh-web | yamux | |
---|---|---|
3 | 3 | |
89 | 2,124 | |
- | 0.9% | |
6.7 | 0.0 | |
3 days ago | 11 days ago | |
Vue | Go | |
MIT License | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
piping-ssh-web
-
SSH over HTTP in Go and WebAssembly on browser
more: https://github.com/nwtgck/piping-ssh-web
-
Secure TCP tunnel from anywhere with curl and nc for single connection
Piping SSH and Piping VNC run on Web browser. This means a Web browser is an alternative frontend of curl ... | nc -lp ... | curl ... and a terminal. Those apps have SSH and VNC (RBF protocol) implementations in JavaScript, thanks to authors of based projects. This means that they work on your local device and never process on the server side. The server is only a Piping Server only for data transferring. See my previous post for detail.
- Why HTTP streaming upload matters on Web browser
yamux
-
List of ngrok/Cloudflare Tunnel alternatives and other tunneling software and services. Focus on self-hosting.
tunnel - This one is a Golang library, not a program you can just run. However, it looks easy to use for creating custom solutions. Uses a single TCP socket, and yamux for multiplexing.
-
Secure TCP tunnel from anywhere with curl and nc for single connection
A simple solution is to multiplex TCP requests over Unix pipe. In order to multiplex TCP requests, Yamux is available created by Hashicorp, who creates Vagrant, Terraform, and so on. The protocol of Yamux is inspired by SPDY, which is the basis of HTTP/2 specification. The protocol spec is found in https://github.com/hashicorp/yamux/blob/master/spec.md. libp2p, which is used in IPFS, also uses Yamux as one choice of multiplexes and maintains Go and Rust versions of Yamux libraries.
-
Protobuf wrapping up raw tcp packets
If so, the answer is probably to put down the protobuf library entirely and just use yamux. Then you just get various net.Conns you can work with and you ignore the entire multiplexing problem.
What are some alternatives?
noVNC - VNC client web application
piping-vnc-web - VNC client over pure HTTPS via Piping Server on Web browser
SSHy - HTML5 SSH Web Client
piping-server - Infinitely transfer between every device over pure HTTP with pipes or browsers
piping-server-rust - Infinitely transfer between every device over pure HTTP with pipes or browsers
piping-serverdemo_images
electerm - 📻Terminal/ssh/telnet/serialport/sftp client(linux, mac, win)
go-piping-server - Piping Server written in Go language (original: https://github.com/nwtgck/piping-server)
action-tmate - Debug your GitHub Actions via SSH by using tmate to get access to the runner system itself.
yamux-cli - Multiplexing TCP and UDP using yamux
openssl-aes-ctr-stream-npm - OpenSSL-compatible AES CTR encryption/decryption for stream