witmproxy 0.0.2-alpha

A WASM-in-the-middle proxy
Documentation

witmproxy ⚠️ under construction 👷

A WASM-in-the-middle proxy, written in Rust.

Quick Start

1. Installation and setup

cargo install witmproxy
witm              # First run: installs daemon and attaches to logs
witm -d           # Run detached (start daemon without attaching to logs)

On first run, witm automatically:

  1. Installs the proxy as a system daemon (using launchd on macOS, systemd on Linux, or Windows Services)
  2. Starts the daemon service
  3. Attaches to the daemon's log output (unless -d/--detach is specified)

2. Daemon management

# View daemon status
witm service status

# Control the daemon
witm service start    # Start the daemon
witm service stop     # Stop the daemon
witm service restart  # Restart the daemon

# View logs
witm service logs          # Show last 50 lines of logs
witm service logs -f       # Follow logs in real-time (like tail -f)
witm service logs -l 100   # Show last 100 lines

# Manage installation
witm service install    # Manually install the daemon
witm service uninstall  # Remove the daemon from the system

3. Add plugins

Plugins are how you can extend witmproxy with whatever functionality your heart desires.

witm plugin add @ezco/noop # add a plugin from the witmproxy.rs registry
witm plugin add ./path/to/component.wasm # add a local plugin

4. Creating a new plugin

witm plugin new <name> [...options] # creates plugin scaffolding

The witmproxy plugin WIT interface is automatically published to GitHub Container Registry and can be consumed using wkg:

# Fetch the WIT interface for plugin development
wkg get --format wit witmproxy:plugin@0.0.6 --output plugin.wit

See WIT Publishing Documentation for more information.

Architecture

A not-entirely-accurate but pretty LLM-generated diagram:

┌─────────────────┐      ┌─────────────────────────────┐      ┌─────────────────┐
│   User device   │      │          witmproxy          │      │  Target Server  │
│                 │      │                             │      │                 │
│  ┌───────────┐  │      │  ┌───────────────────────┐  │      │  ┌───────────┐  │
│  │    App /  │◄─┼──────┼─►│    TLS Termination    │◄─┼──────┼─►│   HTTPS   │  │
|  |  Browser  |  |      │  └───────────────────────┘  │      │  │  Server   │  │
│  └───────────┘  │      │  ┌───────────────────────┐  │      │  └───────────┘  │
│                 │      │  |   Encrypted SQLite    |  │      └─────────────────┘
└─────────────────┘      │  │   ┌───────────────┐   │  │      
                         │  │   │  WASM Plugins │   │  │
┌─────────────────┐      │  │   └───────────────┘   │  │
│  Web Interface  │      │  │                       │  │
│                 │      │  └───────────────────────┘  │
│  ┌───────────┐  │      │  ┌───────────────────────┐  │
│  │   Cert    │──┼──────┼─►│        Cert CA        │  │
│  │ Download  │  │      │  └───────────────────────┘  │
│  └───────────┘  │      └─────────────────────────────┘
└─────────────────┘

⚠️ Security Considerations

  1. Certificate Trust: Installing the root certificate allows the proxy to decrypt all HTTPS traffic.
  2. Plugin capabilities: Plugins only have the permissions you give them, but you are responsible for verifying those permissions are restricted appropriately.
    • Plugin execution can be limited using CEL expressions, restricting when they're allowed to run. While plugins come with their own recommended defaults, users always have the ability to restrict them as they see fit.
    • Plugins may request host capabilities, which you are responsible to decide whether or not to provide. future work: While witmproxy provides default implementations of capabilities we expect to be useful to plugin authors, as a user you may replace the implementation of capabilities granted to plugins.

Supporting the project

Consider either supporting the author directly, or supporting any of the maintainers of the projects that make witmproxy possible:

  • mitmproxy the inspiration for this project
  • sqlite the database engine used for storage
  • Tokio the projects async runtime
  • hyper the man-in-the-middle proxy server
  • salvo the backend powering the web interface and API
  • ...and more! (see cargo.toml for a full list of our dependencies)

Contributing

Prerequisites

  • Nightly Rust: witmproxy requires nightly Rust for development (rustup default nightly or use +nightly with cargo commands)
  • WASM target: Plugin development requires the wasm32-wasip2 target: rustup target add wasm32-wasip2
  • wkg: The wkg CLI is required for updating and fetching WIT (WebAssembly Interface Type) files used by the plugin interface

Steps

  1. Fork the repository
  2. Create a feature branch
  3. Make your changes
  4. Add tests
  5. Submit a pull request

Acknowledgements

Projects which make witmproxy possible (but don't actively list direct sponsorship options):

  • Rust the programming language used to build this project
  • wasmtime the WebAssembly runtime that runs plugins
  • sqlcipher the encrypted database engine used for storage
  • rustls the Rust TLS implementation

License

This project is licensed under the AGPLv3 License, with a paid commercial license available on request.