silentmode/theseus
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
theseus/bundled-addons/vpn/addon.json

16 lines
964 B
JSON
Raw Normal View History

feat(theseus/vpn): VPN extension scaffold — sing-box under our own UI Ships the extension small (~50 KB tarball). No binaries in it — the platform-matched sing-box is downloaded on first "Turn on" from bns/theseus.x/vpn-binaries/<platform>/, sha256-verified against the manifest that ships inside this operator-signed tarball, and cached under extensions-data/vpn/bin/. Every subsequent launch re-verifies before spawning; a mismatch redownloads rather than trusts what is on disk. Config generator produces a sing-box config from a vless:// URL (the shape a 3x-UI VLESS+Reality inbound produces), plus a SOCKS5 inbound on 127.0.0.1:<ephemeral>. api.setSessionProxy points every Theseus request at that port while the tunnel is up; child.on("exit") clears it if sing-box dies. Off again clears the proxy back to whatever the browser had. Panel is a big on/off toggle with a status pill, a paste-and-save endpoint box, and an Advanced disclosure with "auto-on at browser start", "re-download binary" and "clear cache". Any user with a vless:// URL can flip it on today; the free tier and the Silent Mode exit inbound are the server-side half, documented under DESIGN.md. Binary manifest ships with PENDING sha256s until the binaries are uploaded to Sia — ensureBinary refuses to activate on a platform whose sha256 is PENDING, so a user cannot flip it on against an unverified download.
2026-09-21 23:39:32 +02:00
{
"id": "vpn",
"name": "VPN",
vpn 0.1.3 → 0.1.4: an https:// paste imports as a subscription The Custom box validated for a vless:// prefix and rejected anything else, so a provider's subscription URL — the thing most people are handed — got "paste a vless:// URL first" with no hint that the Subscription card two sections down was what it wanted. Now an http(s):// paste in that box is detected and routed to the subscription importer, the placeholder says both are accepted, and the dropdown option reads "Custom — vless:// or subscription URL". Also renames the three bundled entries' status from "coming-soon" to "awaiting-key-issuer". The exits exist and are running xray; what is missing is a way to hand a client credentials without shipping a shared secret. DESIGN.md now records why that list stays empty, since this is the second time the shortcut looked attractive: a vless:// URL is the credential, so writing one into the tarball (immutable, mirrored) or onto a public Sia object (mutable but world-readable) are the same category of mistake. Per-session minting is the fix, because then no shared credential exists to leak. Parser verified against plain-text, standard-base64 and url-safe unpadded-base64 subscription bodies; an HTML error page correctly yields zero entries instead of a JSON parse crash.
2026-09-23 23:21:51 +02:00
"version": "0.1.4",
feat(theseus/vpn): VPN extension scaffold — sing-box under our own UI Ships the extension small (~50 KB tarball). No binaries in it — the platform-matched sing-box is downloaded on first "Turn on" from bns/theseus.x/vpn-binaries/<platform>/, sha256-verified against the manifest that ships inside this operator-signed tarball, and cached under extensions-data/vpn/bin/. Every subsequent launch re-verifies before spawning; a mismatch redownloads rather than trusts what is on disk. Config generator produces a sing-box config from a vless:// URL (the shape a 3x-UI VLESS+Reality inbound produces), plus a SOCKS5 inbound on 127.0.0.1:<ephemeral>. api.setSessionProxy points every Theseus request at that port while the tunnel is up; child.on("exit") clears it if sing-box dies. Off again clears the proxy back to whatever the browser had. Panel is a big on/off toggle with a status pill, a paste-and-save endpoint box, and an Advanced disclosure with "auto-on at browser start", "re-download binary" and "clear cache". Any user with a vless:// URL can flip it on today; the free tier and the Silent Mode exit inbound are the server-side half, documented under DESIGN.md. Binary manifest ships with PENDING sha256s until the binaries are uploaded to Sia — ensureBinary refuses to activate on a platform whose sha256 is PENDING, so a user cannot flip it on against an unverified download.
2026-09-21 23:39:32 +02:00
"description": "Route Theseus's traffic through a Silent Mode VPN endpoint. Runs sing-box locally, exits at one of our servers, and switches on with one click. Paste any vless:// URL to point it at your own endpoint instead.",
"author": "Silent Mode",
"icon": "data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyNCAyNCI+PHBhdGggZD0iTTEyIDJMNCA1djdjMCA1IDMuNSA5LjIgOCAxMCA0LjUtLjggOC01IDgtMTBWNWwtOC0zeiIgZmlsbD0iIzBhYzE4ZSIvPjxwYXRoIGQ9Ik05IDEybDIgMiA0LTQiIGZpbGw9Im5vbmUiIHN0cm9rZT0iI2ZmZiIgc3Ryb2tlLXdpZHRoPSIyIiBzdHJva2UtbGluZWNhcD0icm91bmQiIHN0cm9rZS1saW5lam9pbj0icm91bmQiLz48L3N2Zz4=",
"main": "index.js",
Theseus: start extensions on first use, Startup switches in Settings Every enabled add-on used to be activated synchronously in initAddons(), during app.whenReady and before the window exists. That is the largest launch cost left (boot tracer, 2026-10-03). An add-on can now say "activation": "on-demand" in addon.json. It is then listed at launch but not started. Its declared surfaces stay live: "panels" (new: sidebar panels declared up front), toolbar-menu, context-menu-items and the page-inject bridge, whose source is read on the first matching page. activate() runs on first real use: a panel opened, a menu or context item picked, a message from its panel, tab or page bridge, a Settings addon-invoke, a wiz:// link (for Aegis). All of those go through AddonHost.dispatch(), which starts the add-on and waits for it, so no call is dropped. Concurrent callers share one activation, and activations run one at a time. Startup stays the default: the host cannot tell what an older add-on does in activate(). request-filter add-ons and add-ons that declare no surface are forced to startup. If activate() returns a promise, calls wait for it (at most 5 s). api.startAtLaunch(bool) lets an on-demand add-on ask to be started at launch again (for live relay sessions). Converted: notepad, screenshot, translate, docx-editor, pdf-editor, vpn (none has launch-time work: no file association, no auto-connect, and add-on file tabs are not part of the saved session). Shield and Cookie Pop-ups stay startup: Shield owns the request filter and must see the first request; Cookie Pop-ups costs ~6 ms and acts unasked on every page. Aegis stays startup and untouched: another session owns it. See NOTE-aegis-on-demand.md (next commit). Settings › Performance › Startup: - "Start extensions when first used" (default on). Off = all at launch; switching it off starts the waiting add-ons immediately. - "Start the wallet at launch". Shown disabled with a hint until the installed Aegis manifest allows on-demand. It applies with no Settings change once Aegis opts in. - "Preload common menus" gates prewarmOverlays(). - "Use lightest" preset. New keys are plain SETTINGS_DEFAULTS through the existing settings-set. No new IPC channels. Measured: boot-trace, fresh profile, --seconds 20 so the 30 s add-on OTA poll can't swap Aegis mid-series; warm runs 2-3 of two paired series. - Add-on activation at launch: 121-154 ms -> 104-174 ms. The six converted add-ons went from 16-20 ms to 0. The rest is Shield (83-148 ms, noisy) and Aegis (15 ms in this tree's 0.9.0). - Toolbar painted: 1278-1584 ms -> 1282-1481 ms (within noise). - With "Preload common menus" off: 0 overlays prewarmed, 8 processes instead of 11, about 50-70 MB less at 15 s. The bundled add-on versions are not bumped. Existing profiles keep their old addon.json, and so stay on startup activation, until those add-ons ship with a higher version (seedBundledAddons only reseeds a strictly newer bundle).
2026-10-03 16:05:32 +02:00
"activation": "on-demand",
"panels": [
{ "id": "main", "title": "VPN", "page": "panel.html" }
],
feat(theseus/vpn): VPN extension scaffold — sing-box under our own UI Ships the extension small (~50 KB tarball). No binaries in it — the platform-matched sing-box is downloaded on first "Turn on" from bns/theseus.x/vpn-binaries/<platform>/, sha256-verified against the manifest that ships inside this operator-signed tarball, and cached under extensions-data/vpn/bin/. Every subsequent launch re-verifies before spawning; a mismatch redownloads rather than trusts what is on disk. Config generator produces a sing-box config from a vless:// URL (the shape a 3x-UI VLESS+Reality inbound produces), plus a SOCKS5 inbound on 127.0.0.1:<ephemeral>. api.setSessionProxy points every Theseus request at that port while the tunnel is up; child.on("exit") clears it if sing-box dies. Off again clears the proxy back to whatever the browser had. Panel is a big on/off toggle with a status pill, a paste-and-save endpoint box, and an Advanced disclosure with "auto-on at browser start", "re-download binary" and "clear cache". Any user with a vless:// URL can flip it on today; the free tier and the Silent Mode exit inbound are the server-side half, documented under DESIGN.md. Binary manifest ships with PENDING sha256s until the binaries are uploaded to Sia — ensureBinary refuses to activate on a platform whose sha256 is PENDING, so a user cannot flip it on against an unverified download.
2026-09-21 23:39:32 +02:00
"capabilities": ["sidebar-panel", "session-proxy"],
"updateURL": "https://navigate.st/bns/theseus.x/extensions/vpn/updates.json"
}
Reference in a new issue Copy permalink