fix(security): secure recovery authorization and deployment defaults - #270
Merged
Merged
Conversation
ralph-bitgo
Bot
force-pushed
the
wcn-1929-secure-recovery-compose
branch
from
September 24, 2026 15:18
d020565 to
6163b8d
Compare
Require a recovery token on both services and reject unsafe non-local HTTP recovery. Switch the reference compose to private mTLS links with a certificate bootstrap so deployments cannot expose signed sweeps. Ticket: WCN-1929 Session-Id: b6e61b98-333e-49ec-81c7-f5dc6d5ab18f Task-Id: f204d240-69cb-41c8-b61d-680a4cb321ba
Keep generated deployment credentials out of Docker build layers, verify rejected requests never reach the KMS, and authenticate split recovery fixtures so the security guard covers every route. Ticket: WCN-1929 Session-Id: b6e61b98-333e-49ec-81c7-f5dc6d5ab18f Task-Id: f204d240-69cb-41c8-b61d-680a4cb321ba
ralph-bitgo
Bot
force-pushed
the
wcn-1929-secure-recovery-compose
branch
from
September 24, 2026 15:20
6163b8d to
4849d1a
Compare
ralph-bitgo
Bot
changed the title
ralph-bitgo
Bot
force-pushed
the
wcn-1929-secure-recovery-compose
branch
from
September 24, 2026 15:21
4849d1a to
6a1eab4
Compare
pranavjain97
changed the title
pranavjain97
marked this pull request as ready for review
September 24, 2026 16:49
4 tasks done
s84krish
previously approved these changes
Sep 25, 2026
…overy-compose # Conflicts: # docker-compose.yml
pranavjain97
enabled auto-merge
September 29, 2026 20:19
s84krish
approved these changes
Sep 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
X-Recovery-Tokenauthorization for recovery routes on both MBE and AWM, independent of transport authentication.Why
Recovery endpoints perform signing operations and were previously reachable under unsafe network and authentication defaults. This change makes the reference deployment secure by default and requires explicit operator authorization whenever recovery is enabled. It also restores the recovery-mode gate for MPCv2 recovery before it reaches coin or KMS operations.
Tickets: WCN-1929, WCN-1931