Repository navigation
Nightbell 3.3.0
Two reported issues, and a correction to something 3.2.0 shipped half done.
A monitor decides what its certificate has to prove (#6)
Nightbell could not watch a server with a self-signed certificate at all. Not a NAS, not a box behind a private CA, and not a Tor hidden service, where no certificate authority issues in the first place. The only way through was to stop using HTTPS.
Each monitor now picks one of three:
- System CAs is what every monitor did before, and is still the default.
- Pinned key records the server's key on the first successful check and requires exactly that key afterwards. This is stronger than CA trust rather than weaker: nobody can talk a CA into issuing the key your monitor already recorded. It is the right answer for a machine you administer yourself.
- Any certificate checks nothing. Off by default, and the detail screen says so on every visit rather than letting it be set once and forgotten.
A pinned monitor that is answered by a different key fails the check instead of quietly adopting the new key, and Trust the new key on the detail screen is how you accept a certificate you replaced on purpose.
The report behind this was titled "self-signed https certs?" and the URL in it was plain http:// on a .onion address. Both halves were true, and what joined them was a redirect: Follow redirects is on by default, so a service answering http with a 3xx to https turns an http monitor into a TLS check nobody asked for. That is now said out loud when it happens.
While there: certificates from CAs you installed on the phone yourself are trusted, and api.github.com, f-droid.org and the connectivity probe are held to system anchors in the same change, so widening the first cannot put an MDM-installed certificate in front of the GitHub token.
Page-element monitors and the element picker obey the same setting, so a self-signed host behaves the same whichever kind of monitor is watching it.
The latency budget, on the chart (#5)
The response time chart draws your latency budget across itself as a dashed line, and every check that answered slower than the budget is drawn in amber instead of green. Underneath, a count: Budget 5.30 s, 3 of 8 over.
Amber is not a new colour here. Degraded already means "answered, but slower than its budget", so a slow bar reads the same as the alert it would have raised.
A budget far above every sample would flatten the bars to nothing if the chart simply scaled to it, so the budget may claim a bounded amount of extra headroom and past that the line pins to the top edge, drawn dimmer, with the legend saying the budget is above the range. A capped line never looks like a placed one.
A new version is visible (#no issue)
3.2.0 added an update check with one surface: a single notification, once per version, ever. Worse, it ran inside the background sweep, so turning background checks off silently turned the update check off with it.
There is now a banner on the dashboard, under the fleet verdict, until you dismiss it. Dismissing hides that version for good and the next release still speaks; Settings can undo it, and shows your installed version against the latest as two numbers rather than one sentence. The check also runs when you open the app, capped at once every six hours either way.
Nothing is downloaded or installed for you. Both the banner and the notification open a page.
567 tests on the JVM and 145 on a device.
Signed with the same key as every release since 3.0.1, so this updates in place.