*/!\ THIS VERY EARLY ALPHA SOFTWARE CAN (especially if you got an installer) BE USED TO SCAM (Do actions on your behalf, empty your inventory) YOU ON STEAM, BE VERY CAREFUL IF YOU DON'T UNDERSTAND HOW IT WORKS. YOU HAVE BEEN WARNED /!*
Enhanced Steam Standalone, a standalone version of the Enhanced Steam plugin for various browsers (Chrome*, Firefox, Opera), that works with any html-css-and-js-aware http client (including the Steam client).
For now, the installation requires several steps, with a lot of manual work:
- Clone this repository.
- Edit your hosts file to resolve store.steampowered.com and steamcommunity.com locally (use two different IPs, like 127.0.0.200 and 127.0.0.201; as it is needed for HTTPS). You can also append the hosts file from this repository to yours.
- Start rinetd using your terminal:
rinetd -c rinetd.conf
- Start nginx
- Start/Call the Steam client and navigate.
Note: If you modify the local IP addresses in the hosts file, please modify them in the rinetd configuration too.
This project is a hackish proxy that does inject some javascript script into the store and community steam pages, so they will be enhanced. Here is how it processes, step by step:
- The DNS records for the store and the community are spoofed, thanks to the hosts file.
- The browser then targets localhost for both domains.
- On the local host (a.k.a localhost), the nginx server is running, and therefore, ready to proxy the steam store and community.
- On that same local host, rinetd is running and ready to proxy any other TCP streams that would be needed (such as HTTPS).
- When connected to the proxi-ed steam pages, the nginx daemon queries the DNS (a real one, not the hosts file), to get the IP addresses of the called domain. Then it forwards the request.
- When the page is returned, it perfoms the js injection, and serves the content to the client.
With that principle in mind, and using these software (or similar ones), you can do the following things:
- Use Enhanced Steam with any browser you want, transparently.
- Serve Enhanced Steam for a whole network (a LAN for example)
- [IMPORTANT] The nginx sub_filter can only work with uncompressed streams, and that can be problematic, since it will cause an important waste of bandwith for Steam/Valve if this software is used too broadly.
- [TRIVIAL] The current link in the error page (50x.html) always redirects to the test for the store. It should depend on the host.
This project uses open source code from nginx, rinetd, and Enhanced Steam, and their contributors.
- The TCP proxy uses IP addresses for the redirection. It would be better to use domains instead (eg. store.steampowered.com and steamcommunity.com)
- Check if there is a way (probably not) to get the hosts header from the HTTPS requests.
- Improve the content of the error page, with better "is online" testing; and why not with js.
- Write an installer