The desktop client now shows only a few listed sites in the theatre's
browser (DuckDuckGo and Wikipedia, burrow-client "the browser shows a few
listed sites"), as its old Chromium has holes that will never be mended.
When it keeps an address out, browserState says so: the bar then reads
"<host> opens in your own browser, not here.", with the sites it shows
in the title, and "Open in your browser" hands the address to the client
to open in the system browser. A click on the notice goes back to the
address. A client that sends no `blocked` shows the bar as before.
duckduckgo.com, the browser's start page since 9720d30, is now listed
in .github/allowed-hosts.json, which the security check wanted.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
8fb5cfe's own-video player names www.youtube-nocookie.com and
player.vimeo.com in public/game.html, which the security check's
invariants refused: neither was in .github/allowed-hosts.json.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
- Discord: the account page links a player's Discord account through
Discord's sign-in (lib/discord.js); only linked names are shown on cards
(typed ones are cleared). A bot keeps the Server Booster badge on linked
accounts that boost. The game tells the client where the player is, for
the client's Discord rich presence (flashvars discordAppId).
- @username tags in chat, chat balloons and wall posts: only real players'
names (asked of the server, "xmn"), names with spaces too, drawn on a
blue box; a click opens the player's card.
- Settings: separate Music and SFX volume sliders for the old one.
- Device ids required: a launcher that sends none (before 1.3.0) is told
at the game's login "Your client is outdated. Update at
https://burrow.moe/download". AJ_REQUIRE_DEVICE=0 turns it off.
- Panels: clear a player's Jammer Wall posts; turning away masterpieces
and player items asks first.
- Item Giver: negative colour ids (the same colour written signed).
- buildVersion 71; the client rebuilt with Snipzil's sitting fix.
- Remove package-lock.json: the server uses no npm packages, which the
invariants check enforces (no supply chain to attack).
- Allow the two hosts the server really calls in .github/allowed-hosts.json:
cdn.jsdelivr.net (Twemoji pictures, lib/emoji.js) and vision.googleapis.com
(the optional SafeSearch check, lib/image-moderation.js). The github.com
mention in lib/emoji.js was only a comment, now reworded.
- logText strips line feeds with .replace(/\n/g, ""), the form CodeQL's
js/log-injection recognises as a sanitiser. The old [\r\n]+ to a space was
just as safe, but not recognised, so every log line using it was flagged
(34 alerts on main, 35 on this branch).
- /authenticate: the saved sign-in is decided by what the server finds for
the refresh token, not by whether the request has one
(js/user-controlled-bypass). A token that is not good is still refused
with error_code 100.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Security workflow, on every push, pull request and weekly:
- invariants: no npm packages, no child_process/vm/eval in the server,
no web address outside .github/allowed-hosts.json in the server or in
the SWFs players load, no committed keys, all JavaScript parses
- secrets: TruffleHog over the pushed commits
- codeql: security-extended queries for the JavaScript and the workflows
Commit messages are checked against Conventional Commits; the commits
publish-public.sh makes are exempt. Actions are pinned to commit SHAs.
Co-Authored-By: Claude Opus 5.5 <[email protected]>