Public Access
jaap-jan
b20f7cae04
The relay checkbox said it was not wired up, and the plan said the server half was built and shipped. It was not: there was ADR 0004, the contract records, RelayOptions and a CHECK constraint, and RelayOptions said in its own remarks that there was no endpoint and no dialler. So both halves are built here, as step 3 of docs/reaching-a-host-you-cannot-dial.md. Server, in Features/Relay: - POST /api/v1/relay/tickets makes every decision: the host, Connect on its vault, the relay switched on, and the stored name resolved once and judged by RelayAddressPolicy. Loopback, link-local, 0.0.0.0/8, multicast and the metadata endpoints are refused with no configuration escape, with IPv4-mapped and NAT64 spellings unwrapped first; then the operator's denials, allow-list and private-network switch. What passes goes into a Data Protection ticket, and nothing resolves the name again. Every target refusal is the same 403, so the endpoint cannot be used to map the operator's DNS; the real reason is logged. - GET /api/v1/relay/connect takes the ticket as a second subprotocol, checks its expiry against TimeProvider and spends it with a unique insert into relay_ticket_use before accepting the upgrade. After the upgrade a refusal is a close code: 4502 for a host the server could not reach, 4429 for a limit, 4408 idle, 4409 lifetime, 1001 after a drain. - relay_session is the audit row, written from short-lived scopes. Client: - RelayBridge is a loopback SOCKS5 listener that accepts once and pipes to the relay socket. It rides on the new SshLoopbackProxy.Lifetime, so the connection disposes it on every way a session ends and a failed connect disposes it before throwing. - ServerRelay, exposed as IVaultServer.Relay from /api/v1/meta, asks for the ticket, opens the socket, starts the bridge and turns every refusal into a sentence. - VaultViewModel and TransfersViewModel reach a relayed host through it, never fall back to dialling it directly, and replace SSH.NET's transport error with the relay's own reason when it gave one. Neither side ever cancels a WebSocket operation. Cancelling one aborts the socket, and an aborted socket sends no close frame, which is the only way the client learns the server could not reach the host. AnIdleSession_IsClosedWithTheIdleCode asserts that the code arrives. Three departures from ADR 0004, recorded in it: awaited copy loops rather than Pipelines (same backpressure, two 32 KiB buffers), no ?ticket= fallback, and no device id in the ticket. Tests: API 245, shell 582 (5 skipped), layout 170, SSH 110 including a real login through the bridge, API client 30, contracts 25. Not run: the Android build (its change is copy only) and the Alpine layout oracle.
44 lines
2.5 KiB
XML
44 lines
2.5 KiB
XML
<Project Sdk="Microsoft.NET.Sdk">
|
|
|
|
<!--
|
|
The client's session lifecycle: where a profile lives on disk, how a vault is unlocked, and how a
|
|
fresh machine gets one in the first place.
|
|
|
|
This is the composition layer the application shell sits on, and it is deliberately Avalonia-free
|
|
like every other Client.* project except App. That is what lets the part that actually matters —
|
|
that an unlock works with no network, and that a wrong passphrase is a return value rather than a
|
|
crash — be a fast unit test instead of something only reachable by clicking.
|
|
-->
|
|
|
|
<ItemGroup>
|
|
<ProjectReference Include="../DodoSSH.Client.Api/DodoSSH.Client.Api.csproj" />
|
|
<ProjectReference Include="../DodoSSH.Client.Auth/DodoSSH.Client.Auth.csproj" />
|
|
<ProjectReference Include="../DodoSSH.Client.Domain/DodoSSH.Client.Domain.csproj" />
|
|
<!--
|
|
The SSH layer, for one type: VaultKnownHostStore, which is the IKnownHostStore the application
|
|
actually composes. It has to live on this side of the seam, because it is the only thing that needs
|
|
both the interface the handshake asks and the vault the answer comes from — and it must not live in
|
|
Client.Ssh, which has no project references at all so that connections, authentication and PTY
|
|
handling stay testable with no cache, no keyring and no server.
|
|
-->
|
|
<ProjectReference Include="../DodoSSH.Client.Ssh/DodoSSH.Client.Ssh.csproj" />
|
|
<ProjectReference Include="../DodoSSH.Client.Storage/DodoSSH.Client.Storage.csproj" />
|
|
<ProjectReference Include="../DodoSSH.Client.Sync/DodoSSH.Client.Sync.csproj" />
|
|
<!--
|
|
The terminal layer, for one interface: IConnectionLogSink, which ConnectionRecorder implements. The
|
|
direction is the point. Client.Terminal references only Client.Ssh and must keep doing so — a workspace
|
|
that knew about vaults would be a workspace that could not keep a shell running through a lock — so the
|
|
hole is declared down there and filled up here, exactly as VaultKnownHostStore fills IKnownHostStore.
|
|
Nothing in Client.Terminal references this project, so the graph stays acyclic.
|
|
-->
|
|
<ProjectReference Include="../DodoSSH.Client.Terminal/DodoSSH.Client.Terminal.csproj" />
|
|
</ItemGroup>
|
|
|
|
<ItemGroup>
|
|
<InternalsVisibleTo Include="DodoSSH.Client.Session.Tests" />
|
|
<!-- The shell suite drives a real ServerRelay over an in-process socket through its test constructor. -->
|
|
<InternalsVisibleTo Include="DodoSSH.Client.App.Tests" />
|
|
</ItemGroup>
|
|
|
|
</Project>
|