Repository navigation
v0.24.2
Hardening of guarded reads and esec vault decrypt. Only clients change; the
server stays at v0.24.0. Run esec vault daemon upgrade after installing.
- Fix: a reader's YubiKey stopped your Secure Enclave key. When no
YubiKey of a seal was plugged in, the read failed even if another of your
security keys opens it. A plugin that is missing or finds no key here is
now passed over; the read fails only when nothing here opens the seal, and
says why for each kind of key. - YubiKey slots with touch policy
neverare not used. A guarded read
with one needed only the dialog.esec vault security-keys addrefuses
them too. A slot with touch policycachedstill works, and the dialog
says that another read soon after needs no touch. - The guarded read's dialog shows the asking command, such as
esec vault decrypt prodoresec vault run prod -- ./deploy, so a print
can be told from a run. The session label is marked as the program's own. esec vault decryptcannot be made to forge lines or drive the
terminal. A secret name that is not printable, or holds=or;, is
refused (byruntoo). A value with control characters, tabs, invisible
formatting or a leading quote is quoted;--jsonescapes them; one value
on a terminal is shown quoted when it holds control characters. The
output is not shell syntax: neverevalit.esec vault runanddecryptalso say a read waits for a touch when the
environment is guarded by its seal record alone.esec vault unlockno
longer says guarded environments always ask: one guarded for the session
stays open until the vault locks.