- wtv-cookie support - further development will be in dev branch (may rebase alot) - compression not yet ready, leave it disabled - update: do not delete WTVSec on last socket, instead recreate on prereg - update: clean up SSID session data only if client is not seen for 3 minutes - update: add shouldWeCompress() function - update: tweak lzpf (still corrupted) - update: rename wtv-setup:/get to wtv-setup:/get-settings - update: add additional headers to wtv-setup:/get-settings - update: add initial blank wtv-music:/get-playlist - update wtv-tricks system - Info now shows Guest Mode or Subscriber Info - Implemented wtv-tricks:/unregister - Implemented wtv-tricks:/register - Show correct link in wtv-tricks:/tricks based on Guest Mode status - config.json: enable compression by default - WTVP does not use \r, so swapping the internal header's usage for now. May remove internal header in future update - lzpf: this doesn't fix anything but doesn't break it more either :) - renamed some functions - fixed some param documentation - added ConvertToBuffer function - WTVSec Updates - optimize WordArray to Buffer functions - update documentation in WTVSec - update WTVSec barrowed function in WTVLzpf - removed NewRC4Session, was a pointless alias to SecureOn
4.4 KiB
4.4 KiB
wtv minisrv node.js
The wtv minisrv, or "zefie_wtvp_minisrv" project is a node.js project that provides a mini WebTV Server, aiming for full WTVP (WebTV Protocol) support. This open source server is in alpha status. Use at your own risk.
Current status:
- Supports most known WebTV service encryption scenarios, for full trusted box access
- Can handle client "relogin" and "reconnect" events
- Suports
.jsservice files with synchronous or asynchronous requests - Supports multiple simultaneous users
- WebTV-compatible HTTP(S) Proxy (via minisrv, or using an external proxy for enhanced features (such as WebOne)
- WebTV Cookie (wtv-cookie) support for HTTP(s)
- Flashrom flashing support for all known units (including bf0app 'Old Classic')
- Can flash anything on Ultra Willies with optional
use_zefie_serverflag set onwtv-flashromservice. wtv-update:/syncfor Download-o-Rama style file downloading- Custom Tellyscripts (not yet customizable though)
- Flat file client session store and registration system
Current issues:
- wtv-cookie implementation is still partial
- wtv-lzpf compression support is not yet reliable
- Mis-configuring wtv-update:/sync DiskMaps may cause units to delete contents of partitions (need more info)
- Satellite Receiver units reportedly cannot surf with http or https proxy. (May be fixed by current partial wtv-cookie implementation)
Won't fix:
- wtv-encryption stream breaks when two different sessions have the same SSID (eg spoofing, won't fix (production did it too))
No intentions to support user accounts, registration, or any form of database system(I guess this was a lie, but we still don't use a database!)
Feature Todo:
- wtv-lzpf support (Milestone v1.0)
- TellyScript generation and/or manipulation without external dependancies
- wtv-cookie full support Done v0.9.13
Flashrom flashing for bf0app old classicDone v0.9.9SSID/IP black/whitelisting (including tying SSID to an IP or multiple IPs)Done v0.9.4Flashrom flashing functionality (at least for LC2 and higher)Done v0.8.0Implement HTTP proxy (needs to be able to defluff most of the web, think retro WAP converter)Done v0.7.1
How To Use:
- Install node.js. Be sure to say
Yeswhen asked aboutChocolatey. - Download a snapshot (either of master, or of any commit/branch/relase/tag etc)
- Extract zip somewhere and enter that directory with a command prompt
- Enter
zefie_wtvp_minisrvsubdirectory - Verify you are in the same directory as
app.js, then runnpm install - Check any configuration. Create your override
user_config.json. Especallyservice_ip. See user_config_README.md and user_config.example.json for more information.- Note: The intended use is for all custom config to be in
user_config.jsonand any custom service files to go inUserServiceVault. If you do not care about potential issues with futuregit pull, and will manually add new upstreamconfig.jsonentries, you could use the standardServiceVaultandconfig.json
- Note: The intended use is for all custom config to be in
- Run
node app.js - If you have trouble running it on Windows, try a Linux machine, Windows may need a full development enviroment or extra steps.
- Test with a WebTV Viewer or connect with a real box
- To connect with a real box, you will need to open ports in your firewall and have a way to connect your WebTV (and preferably reroute 10.0.0.1 to the server)
- See ServiceVault.md for a brief introduction to how the service files work
How to Support the Project
- Report Bugs
- Add a Feature and send a Pull Request
- Write and submit better documentation than I created (see Pull Request above)
- Support financially on Patreon