Repository navigation
Published as a pre-release: a work in progress for the Raspberry Pi image. 0.6.0 was never published, so its notes (below) arrive with this one.
-
[Feature] Two hall screens, each with a mind of its own.
/hallis Screen 1 and/hall?screen=hdmi2is Screen 2, for a box with two monitors. Each can be Live (what it always did), Paused (it keeps showing what it showed, clock and all, while the hall moves on; Nunki keeps talking) or Black (nothing, not even a cursor - for the prize-giving, or for the hour in which nobody needs to be told the pairings again). Each can also be told which tournament to show, instead of guessing. All of it survives a restart, and an open screen follows a change at once.?t=still overrules everything, for whoever opens a screen by hand. -
[Feature] The control page grew up into a management display. The two screens sit side by side at the top with their three buttons, a small preview of what each shows, the tournament picker and a link to open it; on a wide monitor the rest of the page splits into two columns. Everything is big enough to hit with a finger. "Identify the screens" puts a 1 and a 2 the size of the monitor on each for five seconds, which settles the question of which cable went where faster than following it behind the desk.
-
[Feature] A sound switch. Off means nothing is said - not queued, not saved up for a dramatic reading later. The control page says so in red, the screens go on showing everything, and the "line being said" at the bottom of the hall screen stays away, since there is no line.
NUNKI_AUDIO=offmakes a fresh install start silent; it is only the default, and the switch wins once somebody touches it. -
[Feature] A local control API,
/api/local/v1, for programs on the same machine - the touch menu of the Raspberry Pi image, mainly.GET /state, andPOSTto/screen,/audio,/hall_tournament,/identifyand/stop, JSON both ways; the contract is docs/local-api.md. It answers loopback only, whatever the PIN andNUNKI_LISTENsay, and refuses anything a proxy passed on (tailscale serveincluded) or a web page sent. Bad input gets a 422 and a sentence, not a shrug. -
[Change] Nunki answers to its own Tailscale name. With
NUNKI_LISTEN=lanit asks the local Tailscale daemon, every fifteen seconds, what this machine is called on the tailnet and which addresses it has there, so a page opened ashttp://hall-pi.<tailnet>.ts.net:4062works even when Tailscale came up after Nunki. Only this machine's own name: "anything under ts.net" would have been a lovely gift to anybody doing DNS rebinding. The PIN still applies to everyone who is not this machine. -
[Change] After the PIN, a hall screen opened as
/hall?screen=hdmi2(with or withoutt=) goes back to that address instead of forgetting which screen it was. -
[Fix] One phone can no longer lock every other browser out of the PIN door. The box-wide cap of forty wrong guesses a minute stays, but once it is reached an address that has not failed yet still gets two tries of its own, and a right PIN gives back its own failure to the count instead of whichever one shared its second.
-
[Fix] "Remove" no longer claims OpenPairings is told when the line is down. The confirmation says when it will not be, and afterwards the page says OpenPairings was not told and that the device has to be removed there too. With the line up nothing changes.
-
[Fix] The plug-in says 0.6.0. It said 0.3.0 while speaking announcements and rooms, so OpenPairings' plug-in list was out of date; a test now holds it to the program's own version.
-
[Fix] The installer shows the PIN, and says that there is one.
install.sh --lanis for a box without a screen, the PIN was only ever shown on a screen, and the installer cheerfully ended with "no PIN", which made the first visit from the arbiter's laptop a short and unrewarding one. The installer now prints the PIN when it is done (it is in/var/lib/nunki/access-pinfor root to read, so the installer can), says where it lives, and the unlock page names the same file for a box with no screen. The three lines that claimed there was no PIN are gone. -
[Fix] A failed Linux update says it failed. The updater wrote down what went wrong and nobody read it, so the control page announced "Nunki stops and comes back in about a minute" to a Nunki that had not stopped and was not going to. The page now asks, and a failure is shown with the updater's own words and a button to try again.
-
[Fix] The updater trusts no symlink in a folder the service owns. It runs as root inside
/var/lib/nunki, which belongs to the unprivileged service user, and used to copy and chown whatever it found there. A state file or abackupsfolder that is a symlink is now skipped with a word, and so is a request that is not a plain file. -
[Fix] The PIN stays out of the log, and out of the lost-and-found.
pinjoins the parameters Phoenix hides when it logs a request. A PIN that cannot be written (full disk, read-only folder) is an error on the page instead of a crashed page whose crash report quoted the new PIN. Aaccess-pinedited in a Windows editor, whose lines end in CRLF, is the PIN it says, not a reason to make a new one; a file that really is unusable is replaced with a line in the log saying so. -
[Fix] A join that could not be saved is not a join. The one-time code is spent and the key lives only in
state.json; if that file cannot be written, the page now says so instead of listing a tournament that vanishes at the next start. State is flushed to disk before it replaces the old file. -
[Fix] A frame Nunki cannot make sense of is skipped. A round with boards that are not boards used to crash the line, reconnect, be sent again and crash again until the supervisor gave up on every tournament at once. It is now logged and skipped, and not stored.
-
[Fix] Reconnecting a line no longer adds another ping chain to it. A stopped reading no longer leaves its sound file in the speech folder on Windows, and the folder is swept at start. The cookie-signing secret is never in a world-readable file, not even for a moment.
POST /unlockwith a body that is not a PIN is a wrong guess, not a 500, and a control-page event with a made-up announcement is ignored. The 403 for a name Nunki does not answer to now says which name and what to do. -
[Security] There is always an access PIN, and every other computer is asked for it. Until now
NUNKI_LISTEN=lanmeant that anybody on the hall's network could start a countdown, stop a reading or read the pairings off the hall screen, on the theory that a hall is full of friends. Nunki now makes 6 random digits at the first start (access-pinin the data folder, owner-only), shows them on its own control page, and asks every browser that is not on this machine for them before any page, the hall screen included; a TV's browser enters them once. This machine is never asked, and neither is anybody while Nunki listens on this machine only, which is still the default. The PIN can be changed on the control page (6 to 64 characters, no space at either end, nothing invisible) or replaced by a new random one, and cannot be removed: an empty field is an error, not a policy. Five wrong guesses make an address wait 5 seconds, then 10, 20 and so on up to a quarter of an hour, and the right PIN is refused while it waits; the whole box takes at most 40 wrong guesses a minute. The guess is counted before it is compared, so a burst cannot outrun the count. A browser is given a keyed stamp of the PIN, never the PIN, so changing it logs every other browser out and closes their open pages. The PIN is never logged, never in an address, and never on the hall screen. A Raspberry Pi image can set it before Nunki starts with apin-requestfile (setand the PIN, ornew), which Nunki applies and deletes whatever came of it. -
[Change] Reference source, no longer a free-for-all. The Functional Source License lasted an afternoon, which is roughly the lifespan of a decision nobody finished thinking about. Nunki's source is now published for reference under the Microsoft Reference Source License (Ms-RSL): you may read it, and that is the whole grant. The builds we publish remain free to use for running chess events; builds you make yourself are not covered. The version published under the FSL today keeps the FSL for whoever already has it, since a licence, unlike a mood, cannot be taken back. CI runs on GitHub-hosted runners now that anybody may watch it, and the release workflows stay switched off until December.