aboutsummaryrefslogtreecommitdiffstats
path: root/packages/meshbay-client/scripts/index.html
diff options
context:
space:
mode:
Diffstat (limited to 'packages/meshbay-client/scripts/index.html')
-rw-r--r--packages/meshbay-client/scripts/index.html27
1 files changed, 27 insertions, 0 deletions
diff --git a/packages/meshbay-client/scripts/index.html b/packages/meshbay-client/scripts/index.html
new file mode 100644
index 0000000..337e180
--- /dev/null
+++ b/packages/meshbay-client/scripts/index.html
@@ -0,0 +1,27 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+ <meta charset="utf-8">
+ <meta name="viewport" content="width=device-width, initial-scale=1">
+ <title>MeshBay</title>
+ <!--
+ The interface is loaded from this package, never from the hub. That is the
+ whole point of the application existing (T3): a hub that ships the code can
+ lift keys from the page whatever the protocol does.
+
+ The Content-Security-Policy is NOT here. It is sent as a header by the
+ protocol handler in src/main.js, because `frame-ancestors` is ignored in a
+ <meta> element — a policy with a directive that silently does nothing is
+ worse than one without it. One source, and every directive effective.
+ -->
+ <link rel="stylesheet" href="./style.css">
+</head>
+<body>
+ <div id="app"></div>
+ <script src="./vendor/argon2.min.js"></script>
+ <script src="./keyderive.js"></script>
+ <script src="./crypto.js"></script>
+ <script src="./transport.js"></script>
+ <script type="module" src="./app.js"></script>
+</body>
+</html>