Repository navigation
chore(deps): update dependency fnox to latest - #51
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/fnox-1.x-lockfile
branch
3 times, most recently
from
October 27, 2026 12:32
6c16a3f to
a6f5063
Compare
renovate
Bot
force-pushed
the
renovate/fnox-1.x-lockfile
branch
2 times, most recently
from
November 2, 2026 03:16
ead361b to
205a14b
Compare
renovate
Bot
force-pushed
the
renovate/fnox-1.x-lockfile
branch
2 times, most recently
from
November 10, 2026 07:58
5b2f412 to
cb4b493
Compare
renovate
Bot
force-pushed
the
renovate/fnox-1.x-lockfile
branch
from
November 18, 2026 21:16
cb4b493 to
2f7bff5
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
1.36.0→v1.50.0Release Notes
jdx/fnox (fnox)
v1.50.0: : Lite Linux builds, optional cloud SDK features, and stricter provider setting checksCompare Source
fnox can now be built without the cloud SDKs, Kubernetes, Keeper, Enpass and FIDO2, and Linux releases include a prebuilt
litevariant that doesn't need libudev.fnox check,exec,exportandgetno longer letif_missinghide a provider whose own settings fail to resolve. This is a behavior change forexecandexport. See Breaking Changes.Added
Cargo features for provider families (#1189) by @jdx. You can leave large provider families out of a source build. Every feature is on by default, so
cargo install fnoxand the full release binaries behave as before.awsaws-kms,aws-sm,aws-psproviders;aws-stsleaseazureazure-kms,azure-sm,azure-acproviders;azure-tokenlease;azure-container-appspush targetgcpgcp-kms,gcp-smproviders;gcp-iamleasekuberneteskubernetesprovider and leasekeeperkeeper-smproviderenpassenpassproviderfido2fido2provider (needs libudev on Linux)--no-default-featuresalone still includes age, 1Password, Bitwarden, Vault, KeePass, the OS keychain and Lua plugins. A config that names a provider, lease backend or push target left out of the build still loads, so secrets from other providers keep working. Only reading or pushing through the missing one fails, with afnox::not_in_builderror that names the Cargo feature you need. fnox checks for this before it asks for credentials. An unexpired cached lease still works without its backend.Lite Linux release archives (#1190) by @jdx. Each Linux target now also gets a
fnox-lite-<target>.tar.gzarchive, built for x86_64 and aarch64 with both glibc and musl. These archives use--no-default-features, and the glibc builds don't needlibudev.so.1at runtime. The full archives are unchanged and remain the default formise use fnox. To install the lite build with mise:fnox check --strict(#1187) by @jdx. This option treats every warning as an error and exits 1, so CI can fail on a provider that can't be configured even when its secrets useif_missing = "warn"or"ignore".Fixed
fnox checkno longer reports a broken provider as healthy (#1187) by @jdx. Previously, a provider setting such asendpoint = { secret = "APPCFG_ENDPOINT" }with that secret unset could still produce "Configuration is healthy". Nowcheckreports the failure once per provider, without needing--all. It's an error when the secret'sif_missingiserrorand a warning otherwise.checknow validates secrets served bydefault_provideror asyncprovider. It also fails on an unknown provider whenif_missing = "error", which matches whatexecandexportdo. As a result,checkcan now fail on configs it used to pass.type = "fido2". Now only reading a FIDO2 secret fails, and the error points you to a glibc build.Breaking Changes
exec,exportandgetfail when a provider's own settings don't resolve (#1199) by @jdx. This applies even if the secret usesif_missing = "ignore"or"warn". Before,fnox execcould run silently without the secret. Now it fails withFailed to resolve secret '<NAME>' for provider '<provider>' configuration.if_missingstill applies when the store is reachable but the key is missing, and a secret with adefaultstill falls back to it.To upgrade: if you relied on
if_missingto run without a store whose settings come from an unset secret, such as a per-stage endpoint, either set that value or give the dependent secret adefault. Runfnox check --strictto find affected providers.Full Changelog: jdx/fnox@v1.49.0...v1.50.0
💚 Sponsor fnox
fnox is built and maintained by @jdx, an open source developer at entire.io, the title sponsor of his open source work.
If fnox handles secrets or config for you or your team, please consider becoming an individual or company sponsor. Your support funds ongoing development and helps keep fnox secure, free, and independent.
v1.48.0: : Touch ID-protected macOS Keychain secrets and streaming proxy responsesCompare Source
The macOS
keychainprovider can now require Touch ID for each read, andfnox proxy runstreams rule-domain responses so SSE and LLM clients get events as they arrive. Secrets can record the URL where a new value is issued. This release also fixes several 1Password problems: secrets lost their trailing newline, andenvironment://references failed on CLI 2.42.0.Added
touch_id = trueon akeychainprovider:<service>.touch-idKeychain service. Before each read, fnox shows the invoking command, project path and secret name, then asks macOS for Touch ID. Canceling or failing the check blocks access, and there is no password fallback.touch_id = true,fnox provider testcreates a temporary protected item and reads it, so it checks real protected access.Fnox.apphelper. Official releases publish it as a separatefnox-touch-id-<target>.zipasset. Install it in/Applicationsor next to thefnoxbinary. Without the helper, Touch ID operations fail with an Apple missing-entitlement error.fnox set --open(#1145) by @jdx. A secret can now include aurlfield for the page where you create a new value, such as a service's token settings page. The URL must usehttporhttps.fnox set KEY --openprints that URL, opens it in your browser, and then shows the usual hidden prompt for the value:--openneeds an interactive terminal and can't be combined withVALUE,--from-fileor--generate.fnox listshows aURLcolumn only when at least one secret has a URL, andfnox tuishows the URL in the secret details.fnox provider discoverlists item metadata (ID, title, tags and vault) without reading any secret fields, so you can look up references before adding them to your config. It uses the provider's configured account and vault. If no vault is configured, it searches every vault the account can access. Tags can be comma-separated or passed more than once, and archived items are skipped.scripts/enable-sudo-touch-id.shcan check, preview or enable Touch ID forsudoon macOS, using the--check,--dry-runand--applymodes.--jsongives structured output. The script never elevates itself and only creates/etc/pam.d/sudo_localwhen that file doesn't exist. It refuses to change existing policies it doesn't recognize.Changed
fnox proxy runno longer waits for a rule domain's full upstream response before forwarding it. It sends the headers right away and then sends the body in chunks as it arrives. Secret values are still redacted, including values split across two chunks. Before this change, streaming APIs such as SSE-based LLM endpoints delivered no events until the upstream finished, and agent clients could time out.Fixed
fnox proxy runno longer exits when a client disconnects mid-response (#1112) by @jdx. Previously, the proxy was killed by SIGPIPE (exit 141). The child command then pointed at a closed port and the proxy's CA file was left in the temp directory.proxy runanddaemon servenow drop only the affected connection and keep running. Pipelines such asfnox get FOO | headbehave as before.[files]that OpenSSH rejected withinvalid format. Batched reads also no longer change multi-line values or drop empty ones. As a result, a stored value that really ends in whitespace now keeps it in environment variables too. Sync cache entries written by earlier versions keep the trimmed value until you refresh them.environment://references work with CLI 2.42.0+ (#1144) by @jdx. fnox now runsop environment secret list. It falls back toop environment readonly when the CLI doesn't know the new command, which is the case for older betas.fnox getandfnox syncresolve provider tokens stored as secrets (#1125) by @jdx. A provider token kept as its own fnox secret, such asBWS_ACCESS_TOKEN, is now resolved forgetandsyncas it already was forexecandexport.syncstill writes only the secrets you selected.fnox.tomlhas a schema error,hook-envnow warns with the parse error. Previously it reported a missing.config/fnox.local.toml, or showed no warning at all when that file existed.ttlonly whendurationis set (#1129) by @jdx. This fixesunknown field: ttlerrors from strict engines such as the GitHub secrets plugin on OpenBao. If you don't setduration, engines that honorttlnow use their role's default TTL instead of the 15 minutes fnox used to request. Setdurationto keep the old behavior.FNOX_AGE_KEYchanges (#1137) by @Aschenbath. Adding, replacing or removing the inline age key in the calling shell now takes effect on the next hook request, without restarting the daemon.fnox sync --local-filewarns before removing stale local cache (#1135) by @jdx. When entries are marked for removal,--dry-runand the confirmation prompt now show a hint. Personal secrets synced by v1.36.0 or older lacklocal_source = trueand look the same as cache copies, so you need to add that flag to keep them. The sync guide now documentslocal_sourceand how to recover those entries.New Contributors
Full Changelog: jdx/fnox@v1.47.0...v1.48.0
💚 Sponsor fnox
fnox is built and maintained by @jdx, an open source developer at entire.io, the title sponsor of his open source work.
If fnox handles secrets or config for you or your team, please consider becoming an individual or company sponsor. Your support funds ongoing development and helps keep fnox secure, free, and independent.
v1.47.0: : Named and passphrase-protected age identities, Azure Container Apps push targetCompare Source
The age provider can now pick one identity per machine from a shared config, read passphrase-protected identity files, and use a named table of recipients.
fnox pushadds an Azure Container Apps target that writes all of a target's variables in one request. This release also fixesop signindetection for 1Password andfnox synccaching for secrets that use a profile'sdefault_provider.Added
fnox.tomlcan list an identity for each machine, for example one per YubiKey. Choose one withdefault_identity, or setFNOX_AGE_IDENTITYto override it on a given machine. An entry can be a key file path or a{ provider, value }reference, such as an age identity unlocked through thefido2provider:key_file, oridentityfor provider-backed entries.FNOX_AGE_KEYstill takes precedence over everything.secretwithprovider/valueis rejected.identities,default_identityorFNOX_AGE_IDENTITYwork as before.key_filecan now point at an identity created withage-keygen | age -p -o identity.age, in binary or armored form. When fnox decrypts a secret, it prompts for the passphrase once per file in each run.fnox setonly uses the public recipients, so it never prompts. Without a terminal, fnox fails with an auth error that suggests decrypting the identity and settingFNOX_AGE_KEY. The daemon does not cache the passphrase, and no environment variable can supply it.recipientscan now be a table, so you can see whose key each entry is:fnox reencrypt. The array form still works.azure-container-appspush target (#1098) by @jdx.fnox pushcan now set environment variables on an Azure Container App through the ARM REST API. It uses the same credentials asazure-smandazure-ac: service principal environment variables, anaz/azdlogin, or a managed identity. Values never appear on a command line.secrets, are left alone. A pushed variable is stored as a plainvalueand replaces any existing variable with the same name, including one that used asecretRef.ETag, the write is conditional, so a concurrent change to the app causes the push to fail instead of being overwritten. fnox polls long-running updates for up to five minutes but doesn't wait for the new revision to become ready. Only the public cloud is supported.fnox pushnow groups writes by target, so output lines are ordered by target. If a batch fails, every variable in it is reported as failed.Fixed
opreports "You are not currently signed in", fnox now treats it as an authentication failure. In a terminal, it offers to runop signinand then retries. Otherwise, it shows theop signinhint. Item, vault or field names containing words like "authorization" no longer cause unrelated failures to be reported as sign-in errors. (#1102) by @djgokufnox syncnow caches secrets that have avaluebut noproviderand are read through the profile'sdefault_provider. Before,--local-fileskipped them, so they kept calling the remote provider and failed offline. The same rule now applies to--source, the "from" labels, and the cleanup of stale cache entries. (#1106) by @jdxNew Contributors
Full Changelog: jdx/fnox@v1.46.0...v1.47.0
💚 Sponsor fnox
fnox is built and maintained by @jdx, an open source developer at entire.io, the title sponsor of his open source work.
If fnox handles secrets or config for you or your team, please consider becoming an individual or company sponsor. Your support funds ongoing development and helps keep fnox secure, free, and independent.
v1.46.0: : Push secrets to CI and hosting platforms with fnox pushCompare Source
fnox 1.46.0 adds
fnox push, which copies secrets into CI and hosting secret stores such as GitHub Actions, Vercel and Fly. Proxy rules can now inject short-lived lease credentials,[files]entries can be cached locally withfnox sync, andallow_privateentries can be limited to one port. This release also fixes a macOS sandbox escape throughopen.Added
fnox pushand push targets (experimental) (#1079) by @jdx. CI secrets and hosting environment variables accept a value but never return it, so fnox can't read them as providers. Instead, a secret can now list the targets it should be sent to.fnox pushgets each value through the secret's own provider and writes it to every listed target, using the fnox key as the name.github-actions(viagh),gitlab-ci(viaglab),vercel,cloudflare-workers(viawrangler),fly,forgejo-actions(Forgejo/Gitea/Codeberg REST API, token fromFORGEJO_TOKEN/GITEA_TOKEN), andhcp-terraform(token fromTF_TOKEN_<host>,TFE_TOKEN, orterraform login).fnox pushasks for confirmation unless you pass--force.--non-interactiveonly works together with--force. fnox checks every target name and target config before it resolves or writes anything. If one write fails, the remaining writes still run, and the command exits non-zero with a list of the failures.[[proxy.rules]]entry can now setleaseinstead ofsecret. The proxy then mints a short-lived credential from that lease (for examplegitlab,github-app,vaultorcloudflare) and injects it only into matching requests. The command sees a placeholder and never sees the minted credential or the parent credential it was minted from.secretandlease.envdefaults to the variable the lease produces. Leases that produce several variables, andcommandleases, needcredential = "NAME"to pick one.aws-stsleases are rejected.fnox lease listandfnox lease revokecan clean them up if fnox was killed.fnox proxy runwon't start. If minting fails, that request is refused, and a later request tries again.[files](#1081) by @jdx.fnox syncnow caches[files]entries as well as secrets. A file stored in a slow remote provider such as 1Password can then be read from a local encrypted copy byfnox get --file,fnox files writeandfnox edit --file. The sync target must be an encryption provider defined in the global config, and the cache is always written to the global config.fnox set --file,fnox edit --fileandfnox reencryptdrop the old cache. Runfnox syncagain whenever the file changes at its source.fnox sync -p sync-age # or: fnox sync ~/.kube/configallow_privateentries (#1088) by @jdx. Underfnox proxy run --sandbox, you can now give the command access to one local service without opening every port on that address. Entries take the formsip:port,[ipv6]:port, or a CIDR block followed by a port. A bare IP or CIDR still covers every port. Port0, hostnames and malformed entries are rejected when the config loads.Changed
fnox proxy run(#1078) by @jdx. Outside the sandbox,fnox proxy runno longer exits as soon as it gets a signal. It passesSIGTERMandSIGHUPon to the command. It also passes onSIGINT, unless fnox is in the terminal's foreground process group, because Ctrl-C has already reached the command in that case. fnox then waits for the command to exit, so it can shut down the proxy and revoke leases.Fixed
open(#1090) by @jdx. A command run underfnox proxy run --sandboxon macOS could useopento launch an app through Launch Services. That app ran outside the sandbox, where it could read hidden paths and write outside the working directory (GHSA-38m4-h5j8-8fq6). The sandbox now blocks these launches. Linux is not affected.Full Changelog: jdx/fnox@v1.45.0...v1.46.0
💚 Sponsor fnox
fnox is built and maintained by @jdx, an open source developer at entire.io, the title sponsor of his open source work.
If fnox handles secrets or config for you or your team, please consider becoming an individual or company sponsor. Your support funds ongoing development and helps keep fnox secure, free, and independent.
v1.45.0: : Agents can ask you to enter a missing secret, and fnox proxy run serves MCP tools with placeholdersCompare Source
With fnox 1.45.0, an AI agent can ask you for a missing secret through a one-time local page, so the value never goes through the chat.
fnox proxy runcan now start before every secret is set, and it serves fnox's MCP tools using placeholders instead of real values.fnox env --describealso reports which file defines each key, and symlinked global configs now work with[files].Added
request_secretMCP tool (#1065, #1074, #1075) by @jdx. When an agent needs a credential you haven't stored yet, it can ask fnox for it by name. fnox serves a one-time page on127.0.0.1and sends the link to the MCP client through URL-mode elicitation. You type the value on that page and fnox stores it the same wayfnox setdoes. The agent is told only that the secret was stored, andexecinjects it from then on. The tool is off by default:mcp.secretsis set, the agent can only ask for names on that list. Theplainprovider is refused. If the secret already has a value, fnox doesn't ask for it again unless the agent passesreplace: true.fnox set NAMEin your own terminal. If the client rejects or cancels the prompt, or the request times out, the agent gets a message that is different from the one sent when you click Decline. That message also tells the agent not to reopen the prompt or ask for the secret in chat.fnox set --from-file. The page can't prove that you are the one filling it in. Another program running as your user could submit a value.fnox proxy run(#1072) by @jdx. When an agent runsfnox mcpinsidefnox proxy run(including--sandbox), the MCP server now relays to the proxy, and you don't need to change the agent's MCP config.get_secretreturns the secret's placeholder instead of its real value.request_secretopens its page from the proxy process, outside the sandbox. After you enter the value, the proxy starts injecting it into matching requests.execisn't offered in this mode.[mcp] toolsandsecretsstill apply. Only secrets that have a proxy rule can be used this way. Once the child starts,fnox proxy runno longer prompts for provider authentication, so authenticate before you start it.fnox proxy runexited if any rule's secret had no value. Now, if a secret is declared but not set, fnox prints a warning, starts anyway, and still gives the command a placeholder. Requests that need the secret get a 403 with a "not set yet" message. When you set the secret, for example withfnox set STRIPE_KEYin another terminal, the next matching request picks it up without a restart. The proxy checks for the value at most once every 3 seconds per secret. A rule that names an undeclared secret is still an error.fnox env --json --describe(#1059) by @jdx. Each key now has asourcefield withpath, the file whose definition wins, andglobal, which is true for the global config and the files it imports. Tools such as mise can use this to tell a project's own keys from your personal global ones. The field is left out when fnox can't trace a key to a file. The describe schema version is still 1. Infnox-client,KeyInfogainssourceand awith_sourcebuilder.Fixed
[files]when~/.config/fnox/config.tomlwas a symlink, as dotfiles managers such as stow create. Becausefnox set --filehad already stored the entry, every later command failed. fnox also rejected source files linked into~/.config/fnox/files/. Both now work.fnox setandfnox reencryptwrite through a source link instead of replacing it. They report an error, before storing anything, if the link is broken or points to the config file or to another entry's file. One case is now stricter: a projectfnox.tomlthat is a symlink into the config directory can no longer declare[files].Full Changelog: jdx/fnox@v1.44.0...v1.45.0
💚 Sponsor fnox
fnox is built and maintained by @jdx, an open source developer at entire.io, the title sponsor of his open source work.
If fnox handles secrets or config for you or your team, please consider becoming an individual or company sponsor. Your support funds ongoing development and helps keep fnox secure, free, and independent.
v1.44.0: : Store whole files by path and edit a single secretCompare Source
fnox 1.44.0 adds secret files: whole files such as
~/.kube/configstored in the global config under the path they belong at, and written there withfnox files write.fnox editcan now edit one secret, accepts editor commands that include arguments, and saves the change to the config file that defines the secret.Added
~/.kube/config,~/.aws/credentialsor~/.npmrc. You can now declare them in a[files]table, using the path as the key. Files use the same providers, profiles andfnox reencryptas secrets, but fnox never turns them into environment variables.[files]is only allowed in the global config. If a projectfnox.tomldeclares it, fnox reports an error, so a cloned repository can't make fnox overwrite paths such as~/.ssh/authorized_keys.~/. Content is kept byte for byte, including the final newline, and must be UTF-8 text.sourceinstead ofvalue. The path is relative to the config directory and can't point outside it. Theplainprovider can't be used for files.fnox files writeresolves every file before it writes any of them. It writes each file with mode0600and replaces a symlink at the path instead of writing through it. Files whose content already matches are left unchanged.--dry-runlists what would be written, and path arguments limit the write to those files.fnox files write.fnox execand shell integration don't write them.fnox edit KEYopens only that secret's resolved value in your editor, as raw text in a private temporary file. No other secrets are decrypted. When you save, fnox stores the new value with the secret's provider and keepsenv,descriptionand its other settings. If the only change is a final newline added by the editor, fnox ignores it. Secrets from read-only providers can't be edited this way. Runningfnox editwith no key works the same as before.Fixed
EDITOR="code --wait"orEDITOR="vim -n"used to fail withFailed to launch editor. fnox now splits the value using shell quoting rules. IfEDITORis empty, fnox usesVISUAL, thenvi(notepadon Windows). fnox now also reports an error when the editor exits with a nonzero status.fnox edit KEYsaving to the wrong file (#1048) by @jdx. Editing a secret defined in the global config or a parent project used to create a new./fnox.tomlin the current directory. The original definition kept the old value. The new value is now written to the file that defines the secret, encrypted with that file's providers. If afnox sync --local-filecache holds the secret, fnox updates the shared definition and removes the outdated cache entry.fnox seton synced and inherited secrets (#1045) by @jdx. Setting a new value now clears the secret'sfnox synccache, so an outdated cached value no longer takes precedence. Setting a value for a secret inherited from another profile or config layer now keeps itsas_file,env,descriptionand other settings.Full Changelog: jdx/fnox@v1.43.0...v1.44.0
💚 Sponsor fnox
fnox is built and maintained by @jdx, an open source developer at entire.io, the title sponsor of his open source work.
If fnox handles secrets or config for you or your team, please consider becoming an individual or company sponsor. Your support funds ongoing development and helps keep fnox secure, free, and independent.
v1.43.0: : Proxy sandbox and egress hardening, exec output redaction, and new lease backendsCompare Source
fnox 1.43.0 makes
fnox proxy runharder to misuse: it now has an OS sandbox, a per-session password and blocking of private network destinations. It also adds output redaction and secret filtering tofnox exec, four new lease backends, a local audit log, value-based secret scanning, generated secrets and KeePass field references. Some proxy setups need a config change; see Breaking Changes.Highlights
fnox execcan redact secret values from piped output,fnox scancan search for your actual secret values (including in a pre-commit hook), and an opt-in audit log records which secrets were read, without recording their values.Added
Proxy
fnox proxy run --sandbox(#1039) by @jdx. Runs the command in an OS sandbox where the proxy is the only network access. Inside the sandbox, the command can't read fnox config, state and data dirs,fnox.toml/profile files and their imports, age key files, or common credential dirs (~/.ssh,~/.aws,~/.kube,~/.gnupg, ...). On Linux it also can't reach local credential sockets. It can write only to the working directory and temp files, and it can't create or change.git/hooks,.git/configor fnox config files. The rest of the filesystem stays readable: fnox hides only the paths on its list.bwrap; on macOS fnox usessandbox-exec. Windows isn't supported. If the sandbox can't start, fnox stops before resolving any secrets and never runs the command unsandboxed. The macOS path hasn't been tested on real hardware yet. On macOS the sandbox can't hide other processes or the Keychain service.query = "<name>"instead ofheaderto substitute a secret into a URL query parameter. The value is percent-encoded, and fnox refuses the request (403) if the placeholder appears anywhere else or more than once.domainaccepts a leading*.that matches exactly one subdomain level. The apex domain and deeper subdomains don't match, and patterns like*.comare rejected.headeris now optional and still defaults toauthorization.allow_domainsandallow_private(#1038) by @jdx.allow_domainslets the proxy tunnel the hosts you list without inspection or credentials while egress stays strict.allow_privatelists the internal networks the proxy may reach (see Breaking Changes). The proxy audit output now also logsrefused requestlines with the destination and the reason.Exec
fnox exec --redact, secret values in the command's stdout and stderr are replaced with[REDACTED], but only for streams that are piped or redirected; terminal output is left alone. Redaction is off by default. To turn it on everywhere, setredact_exec = trueinfnox.tomlorFNOX_EXEC_REDACT=1.--no-redactturns it off for one run, and the flag takes precedence over the environment variable, which takes precedence over config. Values shorter than 3 characters aren't redacted, and you can't combine--redactwith--replace. Redaction matches exact values only, so it won't catch a secret that has been encoded or split before printing.--onlyand--except(#1030) by @jdx. These flags limitfnox execto the secrets you select. Unselected secrets are never resolved, so their providers aren't called and can't prompt for login or fail the run. Patterns are exact names or case-sensitive globs, and you can repeat the flag or separate patterns with commas. fnox still resolves the secrets a selected secret depends on, but passes them to the command only if they're selected too. Leases follow the same filter. An unknown name, or an--onlyglob that matches nothing, is an error.Leases
OAuth2, GitLab, Tailscale and Kubernetes backends (#1037) by @jdx:
oauth2-client-credentials: access tokens from any OAuth2 token endpoint. They're revoked only if you setrevocation_url.gitlab: project or group access tokens on gitlab.com or self-hosted GitLab, deleted on revoke. GitLab expiry is date-only, so a token can stay valid for up to a day after its lease ends unless you revoke it.tailscale: tagged, ephemeral, pre-authorized auth keys. With the defaultreusable = false, every command gets a new key and fnox doesn't cache it.kubernetes: ServiceAccount tokens from the TokenRequest API, without needingkubectl. These can't be revoked and expire on their own. The minimum duration is 10 minutes.Credential URLs must use https; plain http is accepted only for localhost.
fnox lease revokeandfnox lease cleanupnow load the parent credentials a backend needs to revoke a lease, so revocation also works when the parent token is stored in[secrets].Easier lease revocation and JSON listing (#1036) by @jdx.
fnox lease revokeaccepts a full lease ID, a unique ID prefix (including the shortened ID thatlease listprints) or a backend name, which revokes all of that backend's active leases.--allrevokes every active lease in the project. If a prefix matches more than one lease, fnox lists the matches and revokes nothing.fnox lease listgains aLABELcolumn and a--jsonflag that prints full IDs and timestamps but never cached credentials.Other additions
0600file with the time, command, profile, config file, secret name, provider and whether the value came from the daemon cache. Values and command lines are never recorded. The log coversexec,get,export,env --json,list --values,check, shell integration,mcp,proxy runand the TUI. It doesn't coverlease,sync,editorreencrypt. Usefnox auditto view entries, with--secret,--command,--provider,-n/--limit,--jsonand--path.FNOX_AUDIT=on|offandFNOX_AUDIT_PATHoverride the config. Any process running as your user can edit the log, so it isn't tamper-proof. Set[audit]in your global config so a projectfnox.tomlcan't choose the log path.fnox scan([#1Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.