From f367759f30f43d0f18c4fa3e7160a3ee5604e261 Mon Sep 17 00:00:00 2001 From: Anders Betts Date: Thu, 17 Sep 2026 22:39:48 +0200 Subject: scripts: probe and set the Node Web Crypto flag for bw --- docs/DEPLOY.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/DEPLOY.md b/docs/DEPLOY.md index bd08da2..8862fab 100644 --- a/docs/DEPLOY.md +++ b/docs/DEPLOY.md @@ -132,7 +132,8 @@ BOKF_BW_ITEM=bokf bokftui-bw `bokftui-bw` works with `rbw` (its agent keeps the vault unlocked for the session) or the official Bitwarden CLI `bw`, where the session key is cached in `~/.cache/bokf/bw-session` (mode 0600) so the master password is only -asked when the session expires. It reads the item's password, or the custom +asked when the session expires. On Node < 19 the launcher adds +`--experimental-global-webcrypto` when the SDK's WASM crypto needs it. It reads the item's password, or the custom field named by `BOKF_BW_FIELD`, and execs the TUI. Prefer a scoped, revocable API token over the account password: create one -- cgit v1.3