diff options
| author | Christophe Besson <cbesson@gmail.com> | 2026-10-14 22:20:15 +0200 |
|---|---|---|
| committer | Christophe Besson <cbesson@gmail.com> | 2026-10-14 22:20:15 +0200 |
| commit | 422647e7898b8df67cd11f8fb060aec23dec84aa (patch) | |
| tree | 7ecca0e8df1bc8a7d26cf4b471bd44906dd9cfd1 /packages/meshbay-client/build | |
| parent | 28c88908b88c58cba4de08710f6bb268ede02d57 (diff) | |
| download | meshbay-422647e7898b8df67cd11f8fb060aec23dec84aa.tar.gz | |
feat(cli): meshbay-cli, a command-line client for members
Signs in to the hub, lists the account's groups and their folders, and
downloads and uploads files directly with each group's node, end-to-end
encrypted. With no argument it opens a two-pane interactive mode (Textual).
Session and device keys are kept encrypted under the system's key storage,
or a 0600 key file where there is none; node keys are pinned at first
contact; a new machine links as a device.
Packaged on its own on Linux (deb and rpm, on meshbay-common's venv, with a
man page generated from the parser) and frozen next to meshbay-node in the
full Windows installer, not the light one, with a self-test the build runs.
client/keys.py ports keyderive.js and is LGPL like it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Diffstat (limited to 'packages/meshbay-client/build')
| -rw-r--r-- | packages/meshbay-client/build/appx-extensions.xml | 7 | ||||
| -rw-r--r-- | packages/meshbay-client/build/appx-manifest.xml | 14 |
2 files changed, 17 insertions, 4 deletions
diff --git a/packages/meshbay-client/build/appx-extensions.xml b/packages/meshbay-client/build/appx-extensions.xml index 3326dd8..db6e345 100644 --- a/packages/meshbay-client/build/appx-extensions.xml +++ b/packages/meshbay-client/build/appx-extensions.xml @@ -13,3 +13,10 @@ <uap5:ExecutionAlias Alias="meshbay-node.exe" /> </uap5:AppExecutionAlias> </uap5:Extension> + <!-- `meshbay-cli` in a terminal, the command-line client: the same alias + mechanism, for the same reason. --> + <uap5:Extension Category="windows.appExecutionAlias" Executable="app\resources\node-runtime\meshbay-cli.exe" EntryPoint="Windows.FullTrustApplication"> + <uap5:AppExecutionAlias> + <uap5:ExecutionAlias Alias="meshbay-cli.exe" /> + </uap5:AppExecutionAlias> + </uap5:Extension> diff --git a/packages/meshbay-client/build/appx-manifest.xml b/packages/meshbay-client/build/appx-manifest.xml index a8dba41..c097fdd 100644 --- a/packages/meshbay-client/build/appx-manifest.xml +++ b/packages/meshbay-client/build/appx-manifest.xml @@ -44,10 +44,11 @@ ${extensions} </Application> </Applications> - <!-- The node accepts connections from peers (WebRTC, QUIC, casting). Rules - declared here are created by Windows at install with no administrator - prompt, follow the executable's versioned path on every update, and go - with the package. A rule the app made itself named that path and was + <!-- The node accepts connections from peers (WebRTC, QUIC, casting), and + the command-line client does during a transfer (WebRTC). Rules declared + here are created by Windows at install with no administrator prompt, + follow the executable's versioned path on every update, and go with the + package. A rule the app made itself named that path and was stale after the next update; the network capabilities create rules for sandboxed apps only, which a full-trust process is not. Both measured on a real install. --> @@ -64,5 +65,10 @@ <desktop2:Rule Direction="in" IPProtocol="UDP" Profile="all" /> </desktop2:FirewallRules> </desktop2:Extension> + <desktop2:Extension Category="windows.firewallRules"> + <desktop2:FirewallRules Executable="app\resources\node-runtime\meshbay-cli.exe"> + <desktop2:Rule Direction="in" IPProtocol="UDP" Profile="all" /> + </desktop2:FirewallRules> + </desktop2:Extension> </Extensions> </Package> |