e639ffc · favela-peer · pear-git-v3

Changed files (2) +26 -3

lib/bridge.js +14 -2

…	…	@@ -19,7 +19,7 @@ import ProtomuxRPC from 'protomux-rpc'
19	19	import c from 'compact-encoding'
20	20	import b4a from 'b4a'
21	21	import { signAttested } from 'favela-identity/lib/attestation.js'
22		import { claimBytes, releaseBytes } from 'favela-identity/lib/bridge-claim.js'
	22	import { claimBytes, releaseBytes, frontBytes } from 'favela-identity/lib/bridge-claim.js'
23	23
24	24	export const PROTOCOL = 'favela/bridge-register/1'
25	25	const HEX64 = /^[0-9a-f]{64}$/i
…	…	@@ -92,7 +92,19 @@ export function buildRelease ({ nonce, username, root, cred }) {
92	92	return { username, root, nonce, proof: signAttested(releaseBytes({ nonce, username }), cred) }
93	93	}
94	94
95		export default { connectBridge, buildClaim, buildRelease, PROTOCOL }
	95	/**
	96	* Ask a bridge to CARRY an identity this node holds, rather than to name one.
	97	*
	98	* ⚠ `id` is opaque to this daemon on purpose. It is a credential this node holds on some other
	99	* network; what it means there is the bridge's business, and boundary.test.js is what keeps that
	100	* true.
	101	*/
	102	export function buildFront ({ nonce, id, root, cred }) {
	103	if (!root) throw new Error('this node cannot sign yet — link this device to its identity first')
	104	return { id, root, nonce, proof: signAttested(frontBytes({ nonce, id }), cred) }
	105	}
	106
	107	export default { connectBridge, buildClaim, buildRelease, buildFront, PROTOCOL }
96	108
97	109	// ── which bridges carry this node ────────────────────────────────────────────────────────────────
98	110	//

lib/rpc.js +12 -1

…	…	@@ -104,7 +104,7 @@ const MUTATIONS = new Set(['post', 'follow', 'unfollow', 'like', 'unlike', 'repl
104	104	// ⛔ Asking a bridge to carry this identity puts a name for it on somebody's domain, which is the
105	105	// same class of act as turning a network on — so it needs an ATTESTED device, not merely a
106	106	// signed-in browser.
107		'bridge-claim', 'bridge-release'])
	107	'bridge-claim', 'bridge-release', 'bridge-front'])
108	108
109	109	/**
110	110	* The room, or a refusal that says which of the two possible things is wrong.
…	…	@@ -417,6 +417,17 @@ export async function dispatch (node, cmd, a) {
417	417	rememberBridge(node.storage, r.body && r.body.acct, a.bridge)
418	418	return { ...r.body, pending: r.status === 202 ? (r.body && r.body.pending) \|\| true : false }
419	419	}
	420	// ⛔ CARRIED, not named. A bridge that fronts an identity serves what that identity SIGNED — it
	421	// holds no key for it — so this asks for availability, not for authority.
	422	case 'bridge-front': {
	423	const { connectBridge, buildFront } = await import('./bridge.js')
	424	const { rpc } = await connectBridge(node.swarm, a.bridge)
	425	const { nonce } = await rpc.request('challenge', {})
	426	const r = await rpc.request('front', buildFront({ nonce, id: a.id, root: node.rootHex(), cred: node.cred }))
	427	if (r.status !== 200 && r.status !== 202) throw new Error((r.body && r.body.error) \|\| ('bridge refused: ' + r.status))
	428	return r.body
	429	}
	430
420	431	case 'bridge-release': {
421	432	const { connectBridge, buildRelease, bridgeFor, forgetBridge } = await import('./bridge.js')
422	433	// ⚠ The remembered key wins over one supplied by the caller: the node knows which bridge it

favela-peer commits / e639ffc

Changed files (2) +26 -3