decentraland / comms-gatekeeper / 31203221036

Builds Branch Commit Type Ran Committer Via Coverage
31203221036 2.29.1 fix(auth): upgrade crypto middleware validation (#287) push GitHub github
85.68
31196967398 main fix(auth): upgrade crypto middleware validation (#287) push web-flow github
85.68
31194401552 fix/comms-gatekeeper-canonical-signer-validation fix(auth): upgrade crypto middleware validation push Gabriel Diaz github
85.68
31105022351 2.29.0 fix: stop publishing the ban device id on the public status route (#286) push GitHub github
85.68
31103830479 main fix: stop publishing the ban device id on the public status route (#286) * fix: stop publishing the ban device id on the public status route GET /users/{address}/bans is unauthenticated and returned the full ban record, including bannedDeviceId.... push web-flow github
85.68
31103482699 fix/hide-device-id-from-public-ban-status docs: define the public ban schema standalone instead of subtracting a field push LautaroPetaccio github
85.72
31102000335 fix/hide-device-id-from-public-ban-status fix: stop publishing the ban device id on the public status route push LautaroPetaccio github
85.72
31062419960 main feat: enforce platform bans on voice and cast, and make ban status match the gate (#284) push GitHub github
85.68
31062185491 feat/device-aware-ban-status docs: stop claiming ban status matches token issuance exactly the note said the endpoint answers 'the same one every token path applies'. that is not true of the paths that carry a device identifier: they prefer the device on the request and fall... Pull #284 LautaroPetaccio github
85.72
31060594093 feat/device-aware-ban-status feat: evaluate the request device id on the cast gates too push LautaroPetaccio github
85.72
31059989220 feat/device-aware-ban-status docs: list GET /scene-stream-access among the gated key paths the note said the legacy coverage was POST/PUT while the code also gates GET, which returns an existing key. also records that DELETE is deliberately not gated, since revoking a key re... Pull #284 LautaroPetaccio github
85.68
31058619892 feat/device-aware-ban-status fix: gate stream key retrieval and document the 403s GET /scene-stream-access returns an existing streaming_key after a signed-fetch and admin check, and was left ungated when POST and PUT were fixed. that is the same key-bearer bypass on the thi... Pull #284 LautaroPetaccio github
85.68
31058160053 feat/device-aware-ban-status fix: evaluate the request device id on the stream-key gates the gates added in 635ccdc passed only the address, so a wallet with no ban and no recorded connection could reuse or mint a streaming key while the request itself carried a device id co... Pull #284 LautaroPetaccio github
85.66
31057257646 feat/device-aware-ban-status fix: gate the legacy scene-stream-access endpoints on platform bans POST and PUT /scene-stream-access are wallet-scoped signed-fetch admin endpoints that return or mint a streaming_key, and neither consulted userModeration. a platform-banned scen... Pull #284 LautaroPetaccio github
85.66
31053903951 feat/device-aware-ban-status docs: trim the comments added after the last pass the ban-status work reintroduced what the previous trim removed: an eighteen-line block on banStatusHandler restating the response shape, the matchedOn semantics and the disclosure rule, most of w... Pull #284 LautaroPetaccio github
85.63