billion-context 0.1.67 → 0.1.68-pr.427.254
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +9 -0
- package/dist/index.js +826 -379
- package/dist/index.js.map +1 -1
- package/dist/mcp.js +51 -10
- package/dist/mcp.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -162,6 +162,15 @@ bili --host 0.0.0.0 # all interfaces (or use your LAN IP)
|
|
|
162
162
|
- MITM-mode `CONNECT` then also accepts remote clients — for **whitelisted
|
|
163
163
|
model hosts only**. Blind tunnels to arbitrary hosts stay loopback-only, so
|
|
164
164
|
the proxy can never be used as an open relay.
|
|
165
|
+
- The `/bili/<absolute-url>` tunnel has destination admission (#409): the
|
|
166
|
+
proxy itself and link-local/metadata addresses are **always denied**;
|
|
167
|
+
loopback/private destinations are allowed for local clients (self-hosted
|
|
168
|
+
upstreams) and **denied for remote clients** unless listed in
|
|
169
|
+
`BILI_TUNNEL_ALLOWED_HOSTS` (`host` or `host:port`, comma-separated) — a
|
|
170
|
+
remote peer must not use the proxy as an SSRF pivot into your LAN, and the
|
|
171
|
+
management plane is unreachable through the tunnel even via NAT hairpin
|
|
172
|
+
(tunneled requests carry an internal `x-bili-tunnel` marker that `/__bili/`
|
|
173
|
+
rejects).
|
|
165
174
|
- There is **no authentication**: only do this on a trusted LAN or behind a
|
|
166
175
|
firewall. The `/__bili/` management endpoints remain loopback-only.
|
|
167
176
|
- A startup `[security]` warning reminds you of the above.
|