github jdx/fnox v1.50.0
v1.50.0: Lite Linux builds, optional cloud SDK features, and stricter provider setting checks

one hour ago

fnox can now be built without the cloud SDKs, Kubernetes, Keeper, Enpass and FIDO2, and Linux releases include a prebuilt lite variant that doesn't need libudev. fnox check, exec, export and get no longer let if_missing hide a provider whose own settings fail to resolve. This is a behavior change for exec and export. 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 fnox and the full release binaries behave as before.

    Feature Adds
    aws aws-kms, aws-sm, aws-ps providers; aws-sts lease
    azure azure-kms, azure-sm, azure-ac providers; azure-token lease; azure-container-apps push target
    gcp gcp-kms, gcp-sm providers; gcp-iam lease
    kubernetes kubernetes provider and lease
    keeper keeper-sm provider
    enpass enpass provider
    fido2 fido2 provider (needs libudev on Linux)
    cargo install fnox --locked --no-default-features --features aws

    --no-default-features alone 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 a fnox::not_in_build error 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.gz archive, built for x86_64 and aarch64 with both glibc and musl. These archives use --no-default-features, and the glibc builds don't need libudev.so.1 at runtime. The full archives are unchanged and remain the default for mise use fnox. To install the lite build with mise:

    [tools]
    "packslip:github.com/jdx/fnox" = { version = "latest", variant = "lite", workflow = "release.yml" }
  • 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 use if_missing = "warn" or "ignore".

Fixed

  • fnox check no longer reports a broken provider as healthy (#1187) by @jdx. Previously, a provider setting such as endpoint = { secret = "APPCFG_ENDPOINT" } with that secret unset could still produce "Configuration is healthy". Now check reports the failure once per provider, without needing --all. It's an error when the secret's if_missing is error and a warning otherwise.
    • check now validates secrets served by default_provider or a sync provider. It also fails on an unknown provider when if_missing = "error", which matches what exec and export do. As a result, check can now fail on configs it used to pass.
  • musl builds load FIDO2 configs (#1189) by @jdx. Linux musl builds have never included FIDO2. Before, they rejected the whole config if any provider was type = "fido2". Now only reading a FIDO2 secret fails, and the error points you to a glibc build.
  • Windows binaries are published again (#1198) by @jdx. Windows zips are released unsigned until Authenticode signing is set up.

Breaking Changes

  • exec, export and get fail when a provider's own settings don't resolve (#1199) by @jdx. This applies even if the secret uses if_missing = "ignore" or "warn". Before, fnox exec could run silently without the secret. Now it fails with Failed to resolve secret '<NAME>' for provider '<provider>' configuration. if_missing still applies when the store is reachable but the key is missing, and a secret with a default still falls back to it.

    To upgrade: if you relied on if_missing to 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 a default. Run fnox check --strict to find affected providers.

Full Changelog: 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.

Don't miss a new fnox release

NewReleases is sending notifications on new releases.