Repository navigation
v0.62.0
v0.62.0 shows what a sealed document is and who can open it, keeps "My keys" to your own keys, and lets macOS Contacts edit a card in place.
What's new
- Inspect seal, on the web and the desktop.
- Inspect seal… on a sealed document shows who it is sealed to, who signed it, and its structure, at three levels of detail.
- Each recipient is matched to an enrolled key and marked whether they are still in the declared audience. A member removed without a re-seal shows as one who can still open this version, and Re-seal is offered where you manage the audience.
- On the desktop, Inspect a file… reads a local sealed file the same way and says which of your keys opens it.
- "My keys" lists your own keys only, an administrator's too. An administrator's view of the whole tenant moved to its own link (see Before upgrading).
- macOS Contacts edits a CardDAV card in place. Before, every edit on a Mac was saved as a new linked card, and the synced fields could not be changed.
- A field's value completes from a module's vocabulary (module ABI 2.2): a module can offer suggestions for a field while still accepting free text.
- A Sealed document in a personal space says it is sealed for its owner alone when it is added on the desktop, instead of offering an audience.
apass whoaminames the installation, the person and tenant the session acts as, the enrolled hardware keys and the stores you may read.apass lsnames those stores when My Passwords is empty.
Before upgrading
GET certificateswithoutholderanswers the caller's own certificates, for an administrator too.- Before, an administrator received the whole tenant's, so every client's My keys showed colleagues' keys.
- The whole tenant's listing is
GET /api/certificates/tenant, advertised on the API root astenant-certificatesto administrators only; anyone else is refused. alcifra certificates list(without--holder),inspectandrevokefollow the new link where it is offered. A script that read the tenant fromcertificatesas an administrator must followtenant-certificates.
- An Encryption Service at its ADR 0018 or later is needed for a reader whose certificate holds an EC key (a PIV card's key-management slot, a security key's P-256). An older service cannot address such a reader on a
Stricttenant. This is a standing entry, repeated from v0.35.0.
Every change since v0.61.0
- feat: a field's value completes from a module's vocabulary (ABI 2.2, #2288)
- feat: Inspect seal in the web and desktop clients (#2291, slice 1)
- fix(desktop): say a Sealed document in a personal space is sealed for its owner alone (#2293)
- feat: inspect a sealed file and try your keys on the desktop (#2291, slice 2)
- fix(dav): the home advertises its owner's privileges, so macOS Contacts edits in place (#2296)
- ci: split the e2e-2 leg into two (#2300)
- "My keys" lists the caller's own; the tenant under tenant-certificates (#2302)
- docs(readme): Inspect seal, for v0.62.0
- apass whoami, and ls says where the passwords are when My Passwords is empty
- Mutation testing runs the unit tests only (ADR 1087)
Full Changelog: v0.61.0...v0.62.0