aboutsummaryrefslogtreecommitdiffstats
path: root/packages/meshbay-client
diff options
context:
space:
mode:
Diffstat (limited to 'packages/meshbay-client')
-rw-r--r--packages/meshbay-client/build/appx-extensions.xml7
-rw-r--r--packages/meshbay-client/build/appx-manifest.xml14
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>