Phase 5: federation
CI / Test (ubuntu-latest) (push) Canceled after 0s
CI / Test (windows-latest) (push) Canceled after 0s
CI / Storage tests on PostgreSQL (push) Canceled after 0s
CI / Complement (federation off) (push) Canceled after 0s
CI / golangci-lint (push) Canceled after 0s
CI / Smoke test the binary (push) Canceled after 0s
CI / Test (ubuntu-latest) (push) Canceled after 0s
CI / Test (windows-latest) (push) Canceled after 0s
CI / Storage tests on PostgreSQL (push) Canceled after 0s
CI / Complement (federation off) (push) Canceled after 0s
CI / golangci-lint (push) Canceled after 0s
CI / Smoke test the binary (push) Canceled after 0s
Implements PLAN.md Phase 5: the Server-Server API. Warp joins rooms on other servers and lets their users join its rooms, invites across servers with the invitee's server countersigning, rejects remote invites (locally if the inviter is unreachable), and exchanges events, typing, receipts and to-device messages with other homeservers — all behind the runtime switch, which now starts and stops real outbound traffic. The protocol lives in internal/federation with no knowledge of rooms: X-Matrix signing (fuzzed parser), the spec's discovery algorithm keeping the dial address and the TLS name apart, a signed client that refuses every request while the switch is off or the policy denies the destination, and a key ring that caches other servers' keys for at most a week, with optional notaries. The roomserver takes events from elsewhere through the spec's intake: signatures and hashes (a hash mismatch keeps the redacted form), the rules against the event's own auth events, against the state before it — with /get_missing_events for small gaps and /state_ids for wide ones — and against the current state, where a failure is a soft failure. Events held without their state are outliers: a column on roomserver_events, because the current state of a room joined over federation is almost all outliers, and excluded from every timeline query. Forks are resolved at the room's head. Membership across servers is make_join/send_join, make_leave/send_leave and countersigned invites, in both directions; m.room.server_acl is enforced on everything another server sends. History before a remote join is backfilled when /messages pages past it, stored at negative stream positions. internal/federationapi is the running component: the inbound endpoints, and an outbound queue that persists what it owes each destination, sends it in transactions of 50 PDUs and 100 EDUs, backs off from ten seconds to six hours, survives restarts, and drops events persisted while federation is off rather than delivering a backlog in one burst. Its Module is what the switch starts and stops. Also: a TLS listener for port 8448, trusted key servers, key validity and an outbound CA bundle in the config; per-destination health and backoff reset in the admin API; remote profiles, aliases and directories in the Client-Server API; a Complement federation profile. See docs/federation.md, including its known gaps (no partial-state joins, no key rotation). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
d187ad0d17
commit
6aaf554336
89 files changed
+11940
-262
No files matched your search
@@ -33,13 +33,13 @@ type SendToDeviceRequest struct {
|
||||
|
||||
// SendToDevice queues messages for delivery.
|
||||
//
|
||||
// A message to a user of another server is dropped rather than refused.
|
||||
// That is deliberate: a client encrypting for a room with remote members
|
||||
// sends one message per device in one request, and failing the request
|
||||
// because federation is off would stop it from delivering to the local
|
||||
// devices as well. The dropped recipients simply never see the key and
|
||||
// their client reports an undecryptable message, which is what they would
|
||||
// see anyway. Phase 5 routes them.
|
||||
// A message to a user of another server goes to the federation queue. With
|
||||
// federation off it is dropped rather than refused. That is deliberate: a
|
||||
// client encrypting for a room with remote members sends one message per
|
||||
// device in one request, and failing the request because federation is
|
||||
// off would stop it from delivering to the local devices as well. The
|
||||
// dropped recipients simply never see the key and their client reports an
|
||||
// undecryptable message, which is what they would see anyway.
|
||||
func (s *API) SendToDevice(ctx context.Context, req SendToDeviceRequest) error {
|
||||
if req.EventType == "" {
|
||||
return errInvalidParamf("an event type is required")
|
||||
@@ -48,11 +48,19 @@ func (s *API) SendToDevice(ctx context.Context, req SendToDeviceRequest) error {
|
||||
var (
|
||||
queued []storage.NewToDeviceMessage
|
||||
woken []string
|
||||
remote = map[string]map[string]json.RawMessage{}
|
||||
sentAt = s.nowMS()
|
||||
)
|
||||
for userID, byDevice := range req.Messages {
|
||||
localpart, ok := s.localpartOf(userID)
|
||||
if !ok {
|
||||
// A remote recipient goes to the federation queue when there
|
||||
// is one and the sender is ours; a remote sender's message to
|
||||
// a remote user is not this server's to forward.
|
||||
if s.outbound != nil && s.isLocal(req.Sender) {
|
||||
remote[userID] = byDevice
|
||||
continue
|
||||
}
|
||||
s.log.Debug("dropping a to-device message for a remote user",
|
||||
"sender", req.Sender, "recipient", userID)
|
||||
continue
|
||||
@@ -95,6 +103,9 @@ func (s *API) SendToDevice(ctx context.Context, req SendToDeviceRequest) error {
|
||||
woken = append(woken, userID)
|
||||
}
|
||||
|
||||
if len(remote) > 0 {
|
||||
s.outbound.ToDevice(ctx, req.Sender, req.EventType, remote)
|
||||
}
|
||||
if len(queued) == 0 {
|
||||
return nil
|
||||
}
|
||||
|
||||
Reference in new issue
Block a user