Version 0.87.1

The crash screen's “Send a report” button now reaches the report form for everyone.

Pressing it reloads the page, and your session lives only in this browser’s memory, so it ends there. If you had not ticked “Remember this device” you arrived at the sign-in screen instead of the report form, and signing in did not help either, because the part of the address that says what you came to do was dropped on the way. You now arrive at the form you were heading for with the error text already filled in, and any address that says what to do on arrival survives a sign-in. Signing in is still required if you have not asked this browser to remember your account code, which is what keeping the key out of storage costs.

Two things announced in 0.87.0 did not actually work in that build, and now do.

The line under the account-creation screen's copy button was empty, and the pre-filled inquiry draft was not cleared when the inbox was opened without the ask form. Both were deliberate breakages made while checking that the new tests actually fail, and the step that put them back did not run. 0.87.0 was live for about forty minutes.

A mistyped private key is no longer repeated back inside an error message.

Pasting an external wallet’s private key with one character wrong is the ordinary mistake. The library NMTS hands the text to answers by putting the whole pasted string into its error message — measured, not assumed — and that message reached the screen, where it can be photographed or pasted into an inquiry that is stored readable on our server for 30 days. NMTS now answers with its own sentence, which says what to paste and repeats nothing. A private key is the one value here with no reset and no copy on our side.

Three checks that guard the crypto worker and the clipboard now check what they claim to.

Nothing here was leaking: these are the machine checks behind yesterday’s fix for the bug that could encrypt one account’s file list with another account’s key, and each was looking at less than its own note claimed. The list of worker calls allowed to run when the page and the worker disagree about which account is signed in had eleven names and the check could not see two of them at all, so a call that hands a wallet’s private key back to the screen could have been added to that list with every check still passing. The check that says every road to a new set of keys ends the old session first read one file, and the list of places that put a secret on the clipboard was written by hand — which is how the account-creation screen came to copy a 32-character account code with no warning at all until yesterday. All three now compare complete sets, and each reports how many things it judged.