Changelog
Elba changelog — what changed.
v1.1.12026 · the keeping of a promise
A small fix, so the code matches what we said it did.
Fixed
- · Changing the passphrase now re-seals the fence at the current 600,000 PBKDF2 iterations — as this changelog and the Manual already said it did. In 1.1 the change quietly kept the fence's recorded count, so a fence raised by 1.0 stayed at 310,000 after a passphrase change. No harm done to any fence; one more passphrase change under this version brings an older fence to the current count.
- · The Manual's technical note on the passphrase change now matches the code exactly: the salt is reused, and the count is always the current standard.
Changed
- · The Manual PDFs are re-rendered from the current text. The 1.1 package had carried them forward from 1.0, so the PDFs lacked everything the 1.1 Manual added; the three forms of the handbook now say the same thing again.
v1.12026 · the survey release
A fence you can also un-build.
Added
- · Removal: every open item has a Remove button; deletion is real, final, and confirmed once. Empty rooms can be removed from inside. A room with contents refuses to go.
- · Passphrase change: everything is re-sealed under the new key. The gate switches only after the last item, so an interruption leaves the old passphrase in charge; re-running with the same new passphrase resumes where it stopped.
- · A warning at the gate before sealing very large files (they are held whole in memory while sealing).
- · A plain message when a sealed item refuses to open (damaged, or sealed under a different passphrase), instead of silence.
Changed
- · Key derivation for new fences raised from 310,000 to 600,000 PBKDF2 iterations, matching current OWASP guidance. Existing fences record their own count and keep working; changing their passphrase re-seals them at the new count.
- · The typed passphrase is now wiped from the page's input fields the moment the key is derived, not only at lock.
- · VERIFY.txt now says plainly what the in-package checksums do and don't prove, and points to the independently published fingerprint.
- · The Manual's account of the no-network enforcement no longer claims the browser policy survives modification of the file itself; the checksums and the readable source carry that weight, and now the Manual says so.
- · The Manual's "edges of the map" now also names: the unsaved-draft window if the browser dies with a note open; that the folder is recognisable as an Elba fence (contents sealed, existence not); and the practical size ceiling at the gate.
- · The gift folder now carries its own copy of the README, so the letter's references arrive true.
v1.02026 · the first release
One file, one fence.
Added
- · A fence around any folder: AES-256-GCM at rest, key derived from your password and never stored.
- · Notes and arbitrary files, held as sealed items.
- · Rooms — nestable, and themselves sealed.
- · The grey island: everything sealed at rest; one item opens into colour at a time.
- · Idle auto-lock, without losing your work.
- · Optional, opt-in "remember this fence on this device" — stores only a pointer, never your password.
- · A sealed index that can be rebuilt from the items themselves.
- · File-size padding, so the length of your small things doesn't leak.
- · Content binding, so no sealed item can be silently swapped for another.
- · Zero network activity, enforced by browser Content-Security-Policy.
- · Two typefaces embedded directly in the file — not even fonts are fetched.
The horizon
1 January 2030 — by the terms of the license, Elba becomes open source under the MIT License and passes to the Commons.