mles-webproxy
| Crates.io | mles-webproxy |
| lib.rs | mles-webproxy |
| version | 0.8.8 |
| source | src |
| created_at | 2020-08-26 11:05:50.557887 |
| updated_at | 2023-11-26 16:03:10.988815 |
| description | Mles WebProxy - an Mles WebSocket proxy and a static WWW-server |
| homepage | |
| repository | https://github.com/jq-rs/mles-webproxy/tree/jq-rs/crates.io |
| max_upload_size | |
| id | 280934 |
| size | 103,975 |
(jq-rs)
documentation
https://mles.io
README
mles-webproxy
mles-webproxy is deprecated in favor of Mles v2 and will be obsolete from the beginning of year 2024.
mles-webproxy is an Mles WebSocket proxy service for Mles WebSocket protocols, like MlesTalk. It receives traffic over TLS and forwards it transformed to AES towards Mles server (and vice versa).
Mles WebProxy receives traffic over TLS. In case of Mles WebSocket protocol, the connection is upgraded and messages forwarded transformed to AES towards configured Mles server (and vice versa).
Please do end-to-end encrypt the data you send anyway. For more details, please check the Mles specifications.
Example how to create your own personal proxy server
- Install Rust and Cargo package manager to your preferred server
- Install
mles-webproxy:RUSTFLAGS="-C target-feature=+aes,+ssse3" cargo install mles-webproxy - Open port 80 and 443 of your firewall for Mles WebSocket protocol and Let's Encrypt certificates
- Startup
mles-webproxyMles WebSocket proxy in your local server. Notice: this will try to fetch certificates from Let's Encrypt by default:export MLES_KEY=<secret-server-key-string-here>; mles-webproxy <www-root> <email-for-tls> <domain-for-tls> <mles-srv-addr x.x.x.x:p>- default ports 80 and 443 need root privileges
- Connect to port 443 of your server with a browser or your Mles WebSocket application
Enjoy talking over Mles WebSocket proxy!
Available public proxy servers
- https://mles.io:443
- <please add your public server here>