zefie b96718555b v0.9.18
- numerous bug fixes
 - too much to remember
   - rewrote sync system yet again
   - more classes
      - WTVShared class for shared functions
      - clientShowAlert class for easy client:showalert urls
    - User File Store
      - Can upload with PUT commands in wtv-disk
      - Programmically access files with new functions in WTVClientSessionData
      - TODO: file browser
    - other stuff I can't remember
  - work on post data bug
  - proper gzip download for disk system (aka WNI reinventing the Content-Encoding: gzip wheel)
  - send Last-Modified for static files
  - send wtv-checksum for all disk system downloads
  - update to v90 modem firmware
    - offer kflex with `Old` diskmap
2022-11-29 08:27:58 -05:00
2022-11-29 08:27:57 -05:00
2022-11-29 08:27:58 -05:00
2021-07-11 18:19:53 -04:00
2022-11-29 08:27:58 -05:00
2022-11-29 07:43:51 -05:00
2022-11-29 07:43:53 -05:00
2022-11-29 08:27:57 -05:00
2022-11-29 07:43:53 -05:00
2022-11-29 07:43:52 -05:00
2022-11-29 08:27:57 -05:00
2022-11-29 07:43:51 -05:00

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.

License: GPL v3

Current status:

  • Supports most known WebTV service encryption scenarios, for full trusted box access
  • Can handle client "relogin" and "reconnect" events
  • Suports .js service 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 support (wtv-cookie) for HTTP(s)
  • Flashrom flashing support for all known units (including bf0app 'Old Classic')
  • Can flash anything on Ultra Willies with optional use_zefie_server flag set on wtv-flashrom service.
  • wtv-update:/sync for 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 classic Done v0.9.9
  • SSID/IP black/whitelisting (including tying SSID to an IP or multiple IPs) Done v0.9.4
  • Flashrom flashing functionality (at least for LC2 and higher) Done v0.8.0
  • Implement 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 Yes when asked about Chocolatey.
  • 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_minisrv subdirectory
  • Verify you are in the same directory as app.js, then run npm install
  • Check any configuration. Create your override user_config.json. Especally service_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.json and any custom service files to go in UserServiceVault. If you do not care about potential issues with future git pull, and will manually add new upstream config.json entries, you could use the standard ServiceVault and config.json
  • 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

Description
we do funny shit over here
Readme GPL-3.0 417 MiB
Languages
Logos 75.8%
JavaScript 19.8%
HTML 3.1%
C 0.5%
C++ 0.4%
Other 0.2%