@ctxfile/relay 0.1.0
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/LICENSE +202 -0
- package/README.md +56 -0
- package/dist/chunk-DKK4LTPB.js +58 -0
- package/dist/chunk-DKK4LTPB.js.map +1 -0
- package/dist/cli.js +1416 -0
- package/dist/cli.js.map +1 -0
- package/dist/index.d.ts +320 -0
- package/dist/index.js +1270 -0
- package/dist/index.js.map +1 -0
- package/dist/org-ZT7EGRAP.js +18 -0
- package/dist/org-ZT7EGRAP.js.map +1 -0
- package/package.json +67 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,56 @@
|
|
|
1
|
+
# @ctxfile/relay
|
|
2
|
+
|
|
3
|
+
The ctxfile relay: an always-on MCP endpoint over an encrypted vault. **Hosted, it is the Sync tier** (`sync.ctxfile.dev`). **Self-hosted, the same build is the Team/Enterprise hub.** One image, every SKU.
|
|
4
|
+
|
|
5
|
+
The relay is open source on purpose: it is the component that momentarily holds plaintext in Standard mode, so it is the component you must be able to audit. See [ctxfile.dev/security](https://ctxfile.dev/security).
|
|
6
|
+
|
|
7
|
+
## What it does
|
|
8
|
+
|
|
9
|
+
- **Stores ciphertext.** Devices encrypt every record client-side (XChaCha20-Poly1305, keys derived via Argon2id) and sync blobs up under opaque ids. The datastore never contains plaintext, and blob names leak nothing.
|
|
10
|
+
- **Serves the five ctxfile tools over Streamable HTTP** (`get_context`, `save_session`, `continue_thread`, `list_threads`, `ingest_context`) so any MCP-capable client surface — phone, web, chat app, another machine — can save and resume threads. Standard-mode vaults only: serve-time decryption happens in memory, per request, under a key wrapped by the keyring; nothing decrypted is persisted or logged.
|
|
11
|
+
- **Strict vaults are a wall:** the relay holds ciphertext it can never decrypt. Sync works; `/mcp` refuses; that refusal is the feature.
|
|
12
|
+
- **Handoff grants:** thread-scoped, read-only (or read+ingest), expiring, revocable bearer tokens — "take over my project while I'm out", enforced server-side.
|
|
13
|
+
- **Federation (Enterprise):** org identities (Ed25519), signed org-to-org grants, invite-only trusted-peer redemption, pull-model thread exchange between two hubs. No central server in the data path.
|
|
14
|
+
- **Append-only audit:** every vault event, blob push, MCP call, grant issue/redeem/denial, with actor and org attribution. `audit export` emits JSONL for your SIEM.
|
|
15
|
+
|
|
16
|
+
## Run
|
|
17
|
+
|
|
18
|
+
```bash
|
|
19
|
+
node dist/cli.js start --data-dir ~/ctxfile-relay # or: ctxfile-relay start
|
|
20
|
+
```
|
|
21
|
+
|
|
22
|
+
All state (SQLite, keyring master key, org identity) lives in the data dir: one folder to volume-mount, one folder to back up. Defaults: `127.0.0.1:5959`, registration open (self-host mode). Environment: `CTXFILE_RELAY_DATA`, `CTXFILE_RELAY_HOST`, `CTXFILE_RELAY_PORT`, `CTXFILE_RELAY_ORG`, `CTXFILE_RELAY_REGISTRATION` (`closed` for hosted deployments where the subscription flow provisions vaults), `CTXFILE_RELAY_PUBLIC_URL`.
|
|
23
|
+
|
|
24
|
+
Docker (build from the repo root; this is the Team hub artifact):
|
|
25
|
+
|
|
26
|
+
```bash
|
|
27
|
+
docker build -f packages/relay/Dockerfile -t ctxfile-relay .
|
|
28
|
+
docker run -p 5959:5959 -v ctxfile-relay-data:/data ctxfile-relay
|
|
29
|
+
```
|
|
30
|
+
|
|
31
|
+
Fly.io: `fly deploy -c packages/relay/fly.toml` (see the file's header for secrets).
|
|
32
|
+
|
|
33
|
+
## HTTP API
|
|
34
|
+
|
|
35
|
+
| Route | Auth | Purpose |
|
|
36
|
+
|---|---|---|
|
|
37
|
+
| `GET /healthz` | none | Liveness + org id |
|
|
38
|
+
| `POST /v1/vaults` | none (when registration is open) | Create a vault: salt, KDF params, passphrase/recovery key wraps; returns vault id + device token |
|
|
39
|
+
| `GET /v1/vaults/me` | bearer | Vault metadata a new device needs to unlock (salt, wraps) |
|
|
40
|
+
| `POST /v1/vaults/enroll-key` | bearer (write) | Standard mode only: the data key, immediately wrapped by the keyring |
|
|
41
|
+
| `GET /v1/blobs`, `GET/PUT /v1/blobs/:id` | bearer (read/write) | Ciphertext sync; LWW versions enforced server-side too; 512KB cap, per-token rate limits |
|
|
42
|
+
| `POST /v1/grants`, `GET /v1/grants`, `POST /v1/grants/:id/revoke` | bearer (write to issue) | Handoff grants |
|
|
43
|
+
| `POST /v1/federation/grants` | bearer (write) | Org-signed federation grant for an audience org |
|
|
44
|
+
| `POST /v1/federation/redeem` | signatures, not bearer | Trusted-peer redemption; every denial is audited |
|
|
45
|
+
| `GET /v1/audit` | bearer | The vault's audit rows |
|
|
46
|
+
| `/mcp` | bearer (vault or grant token) | Streamable HTTP MCP; one session per client, session bound to its token |
|
|
47
|
+
|
|
48
|
+
Tokens are stored as SHA-256 hashes and carry scopes (`read:context`, `write:sessions`). CLI: `vaults`, `tokens list|create|revoke`, `grants issue`, `org show|trust`, `federation issue|redeem`, `audit tail|export`.
|
|
49
|
+
|
|
50
|
+
## Security model, in one paragraph
|
|
51
|
+
|
|
52
|
+
Clients encrypt before upload; the relay stores ciphertext under opaque ids; Standard-mode serving unwraps a per-vault data key through the `KeyProvider` seam (local keyring file when self-hosted, cloud KMS when hosted, the customer's own KMS for BYOK — same two-method interface, which is why key revocation is crypto-shredding), decrypts in memory for one request, and discards; Strict mode never enrolls a key at all; no plaintext is ever written to logs (log lines carry ids and counts only); grants are least-privilege by default (single thread, read-only, 7-day expiry); federation is invite-only by exchanged org identity and every redemption or denial is an audit row. Production deployments terminate TLS in front (Fly edge, Caddy, nginx); hub-to-hub mTLS is on the deploy checklist.
|
|
53
|
+
|
|
54
|
+
## Boundary note (for the repo split)
|
|
55
|
+
|
|
56
|
+
The data path in this package (crypto, blob storage, vault serving) is Apache-2.0 and stays open — it is the trust story. The planned multi-org/team management layer (org member administration, policy workflows, SSO glue, managed-hub tooling) is the commercial module and will live in the private repo, plugging in the way `@ctxfile/pro` plugs into the core. What exists here today, including grants, federation primitives, and audit, is open.
|
|
@@ -0,0 +1,58 @@
|
|
|
1
|
+
#!/usr/bin/env node
|
|
2
|
+
|
|
3
|
+
// src/org.ts
|
|
4
|
+
import { createPrivateKey, createPublicKey, generateKeyPairSync, sign, verify } from "crypto";
|
|
5
|
+
import { chmodSync, existsSync, readFileSync, writeFileSync } from "fs";
|
|
6
|
+
import path from "path";
|
|
7
|
+
function loadOrCreateOrgIdentity(dataDir, orgId) {
|
|
8
|
+
const filePath = path.join(dataDir, "org-identity.json");
|
|
9
|
+
if (existsSync(filePath)) {
|
|
10
|
+
const stored = JSON.parse(readFileSync(filePath, "utf8"));
|
|
11
|
+
return {
|
|
12
|
+
orgId: stored.orgId,
|
|
13
|
+
publicKeyPem: stored.publicKeyPem,
|
|
14
|
+
privateKey: createPrivateKey(stored.privateKeyPem)
|
|
15
|
+
};
|
|
16
|
+
}
|
|
17
|
+
const { publicKey, privateKey } = generateKeyPairSync("ed25519");
|
|
18
|
+
const publicKeyPem = publicKey.export({ type: "spki", format: "pem" }).toString();
|
|
19
|
+
const privateKeyPem = privateKey.export({ type: "pkcs8", format: "pem" }).toString();
|
|
20
|
+
writeFileSync(filePath, `${JSON.stringify({ orgId, publicKeyPem, privateKeyPem }, null, 2)}
|
|
21
|
+
`, "utf8");
|
|
22
|
+
chmodSync(filePath, 384);
|
|
23
|
+
console.error(`ctxfile-relay: generated org identity "${orgId}" at ${filePath} (mode 600)`);
|
|
24
|
+
return { orgId, publicKeyPem, privateKey };
|
|
25
|
+
}
|
|
26
|
+
function canonicalJson(value) {
|
|
27
|
+
return JSON.stringify(value, Object.keys(value).sort());
|
|
28
|
+
}
|
|
29
|
+
function signGrantDoc(identity, doc) {
|
|
30
|
+
return sign(null, Buffer.from(canonicalJson({ ...doc })), identity.privateKey).toString("base64");
|
|
31
|
+
}
|
|
32
|
+
function verifyGrantSig(publicKeyPem, doc, sigB64) {
|
|
33
|
+
try {
|
|
34
|
+
return verify(null, Buffer.from(canonicalJson({ ...doc })), createPublicKey(publicKeyPem), Buffer.from(sigB64, "base64"));
|
|
35
|
+
} catch {
|
|
36
|
+
return false;
|
|
37
|
+
}
|
|
38
|
+
}
|
|
39
|
+
function signRedemption(identity, gid) {
|
|
40
|
+
return sign(null, Buffer.from(`redeem:${gid}`), identity.privateKey).toString("base64");
|
|
41
|
+
}
|
|
42
|
+
function verifyRedemption(publicKeyPem, gid, sigB64) {
|
|
43
|
+
try {
|
|
44
|
+
return verify(null, Buffer.from(`redeem:${gid}`), createPublicKey(publicKeyPem), Buffer.from(sigB64, "base64"));
|
|
45
|
+
} catch {
|
|
46
|
+
return false;
|
|
47
|
+
}
|
|
48
|
+
}
|
|
49
|
+
|
|
50
|
+
export {
|
|
51
|
+
loadOrCreateOrgIdentity,
|
|
52
|
+
canonicalJson,
|
|
53
|
+
signGrantDoc,
|
|
54
|
+
verifyGrantSig,
|
|
55
|
+
signRedemption,
|
|
56
|
+
verifyRedemption
|
|
57
|
+
};
|
|
58
|
+
//# sourceMappingURL=chunk-DKK4LTPB.js.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"sources":["../src/org.ts"],"sourcesContent":["import { createPrivateKey, createPublicKey, generateKeyPairSync, sign, verify, type KeyObject } from \"node:crypto\";\nimport { chmodSync, existsSync, readFileSync, writeFileSync } from \"node:fs\";\nimport path from \"node:path\";\n\n/**\n * Org identity (Enterprise PRD §4.1): every hub carries an org_id and an\n * Ed25519 keypair. Federation grants are signed by the issuing org and\n * redeemed only by orgs whose public keys this hub explicitly trusts —\n * invite-only federation, by exchanged identity, no discovery.\n */\n\nexport interface OrgIdentity {\n orgId: string;\n publicKeyPem: string;\n privateKey: KeyObject;\n}\n\nexport function loadOrCreateOrgIdentity(dataDir: string, orgId: string): OrgIdentity {\n const filePath = path.join(dataDir, \"org-identity.json\");\n if (existsSync(filePath)) {\n const stored = JSON.parse(readFileSync(filePath, \"utf8\")) as {\n orgId: string;\n publicKeyPem: string;\n privateKeyPem: string;\n };\n return {\n orgId: stored.orgId,\n publicKeyPem: stored.publicKeyPem,\n privateKey: createPrivateKey(stored.privateKeyPem),\n };\n }\n const { publicKey, privateKey } = generateKeyPairSync(\"ed25519\");\n const publicKeyPem = publicKey.export({ type: \"spki\", format: \"pem\" }).toString();\n const privateKeyPem = privateKey.export({ type: \"pkcs8\", format: \"pem\" }).toString();\n writeFileSync(filePath, `${JSON.stringify({ orgId, publicKeyPem, privateKeyPem }, null, 2)}\\n`, \"utf8\");\n chmodSync(filePath, 0o600);\n console.error(`ctxfile-relay: generated org identity \"${orgId}\" at ${filePath} (mode 600)`);\n return { orgId, publicKeyPem, privateKey };\n}\n\n/** A federation grant document; signed canonically (sorted keys) so both\n hubs compute identical bytes. */\nexport interface FederationGrantDoc {\n gid: string;\n issuer_org: string;\n issuer_url: string;\n audience_org: string;\n vault_id: string;\n thread_title: string;\n permission: \"read\" | \"read+ingest\";\n exp: number;\n}\n\nexport function canonicalJson(value: Record<string, unknown>): string {\n return JSON.stringify(value, Object.keys(value).sort());\n}\n\nexport function signGrantDoc(identity: OrgIdentity, doc: FederationGrantDoc): string {\n return sign(null, Buffer.from(canonicalJson({ ...doc })), identity.privateKey).toString(\"base64\");\n}\n\nexport function verifyGrantSig(publicKeyPem: string, doc: FederationGrantDoc, sigB64: string): boolean {\n try {\n return verify(null, Buffer.from(canonicalJson({ ...doc })), createPublicKey(publicKeyPem), Buffer.from(sigB64, \"base64\"));\n } catch {\n return false;\n }\n}\n\n/** Signature a requesting hub makes over a grant id, proving it holds the\n audience org's key when redeeming. */\nexport function signRedemption(identity: OrgIdentity, gid: string): string {\n return sign(null, Buffer.from(`redeem:${gid}`), identity.privateKey).toString(\"base64\");\n}\n\nexport function verifyRedemption(publicKeyPem: string, gid: string, sigB64: string): boolean {\n try {\n return verify(null, Buffer.from(`redeem:${gid}`), createPublicKey(publicKeyPem), Buffer.from(sigB64, \"base64\"));\n } catch {\n return false;\n }\n}\n"],"mappings":";;;AAAA,SAAS,kBAAkB,iBAAiB,qBAAqB,MAAM,cAA8B;AACrG,SAAS,WAAW,YAAY,cAAc,qBAAqB;AACnE,OAAO,UAAU;AAeV,SAAS,wBAAwB,SAAiB,OAA4B;AACnF,QAAM,WAAW,KAAK,KAAK,SAAS,mBAAmB;AACvD,MAAI,WAAW,QAAQ,GAAG;AACxB,UAAM,SAAS,KAAK,MAAM,aAAa,UAAU,MAAM,CAAC;AAKxD,WAAO;AAAA,MACL,OAAO,OAAO;AAAA,MACd,cAAc,OAAO;AAAA,MACrB,YAAY,iBAAiB,OAAO,aAAa;AAAA,IACnD;AAAA,EACF;AACA,QAAM,EAAE,WAAW,WAAW,IAAI,oBAAoB,SAAS;AAC/D,QAAM,eAAe,UAAU,OAAO,EAAE,MAAM,QAAQ,QAAQ,MAAM,CAAC,EAAE,SAAS;AAChF,QAAM,gBAAgB,WAAW,OAAO,EAAE,MAAM,SAAS,QAAQ,MAAM,CAAC,EAAE,SAAS;AACnF,gBAAc,UAAU,GAAG,KAAK,UAAU,EAAE,OAAO,cAAc,cAAc,GAAG,MAAM,CAAC,CAAC;AAAA,GAAM,MAAM;AACtG,YAAU,UAAU,GAAK;AACzB,UAAQ,MAAM,0CAA0C,KAAK,QAAQ,QAAQ,aAAa;AAC1F,SAAO,EAAE,OAAO,cAAc,WAAW;AAC3C;AAeO,SAAS,cAAc,OAAwC;AACpE,SAAO,KAAK,UAAU,OAAO,OAAO,KAAK,KAAK,EAAE,KAAK,CAAC;AACxD;AAEO,SAAS,aAAa,UAAuB,KAAiC;AACnF,SAAO,KAAK,MAAM,OAAO,KAAK,cAAc,EAAE,GAAG,IAAI,CAAC,CAAC,GAAG,SAAS,UAAU,EAAE,SAAS,QAAQ;AAClG;AAEO,SAAS,eAAe,cAAsB,KAAyB,QAAyB;AACrG,MAAI;AACF,WAAO,OAAO,MAAM,OAAO,KAAK,cAAc,EAAE,GAAG,IAAI,CAAC,CAAC,GAAG,gBAAgB,YAAY,GAAG,OAAO,KAAK,QAAQ,QAAQ,CAAC;AAAA,EAC1H,QAAQ;AACN,WAAO;AAAA,EACT;AACF;AAIO,SAAS,eAAe,UAAuB,KAAqB;AACzE,SAAO,KAAK,MAAM,OAAO,KAAK,UAAU,GAAG,EAAE,GAAG,SAAS,UAAU,EAAE,SAAS,QAAQ;AACxF;AAEO,SAAS,iBAAiB,cAAsB,KAAa,QAAyB;AAC3F,MAAI;AACF,WAAO,OAAO,MAAM,OAAO,KAAK,UAAU,GAAG,EAAE,GAAG,gBAAgB,YAAY,GAAG,OAAO,KAAK,QAAQ,QAAQ,CAAC;AAAA,EAChH,QAAQ;AACN,WAAO;AAAA,EACT;AACF;","names":[]}
|