Skip to content

cxg changelog

Version 1.6.1

Fixed

  • cxg update failed on Homebrew installs with Update failed: IoError: No such file or directory (os error 2) at “Replacing binary file…”. Homebrew links bin/cxg -> ../Cellar/cxg/<version>/bin/cxg, and the replacement step resolved that relative link target against the current working directory rather than the link’s own directory, so it failed from everywhere except bin/ itself. macOS reports the symlink as the running executable, so that is where it showed; a plain-file install was not affected. The replacement now follows the link to an absolute path.

    1.5.0 and 1.6.0 still run their own updater, so cxg update on those releases cannot pick up this fix. Upgrade once through your package manager (brew upgrade cxg, cargo install cert-x-gen --force, or pulling the new image with docker pull ghcr.io/bugb-technologies/cert-x-gen:latest) or with a fresh download from the releases page.

Changed

  • cxg update no longer replaces a binary that a package manager owns. A cxg in a Homebrew Cellar, in cargo’s bin directory, or inside a container prints the command that upgrades it through its manager (brew upgrade cxg, cargo install cert-x-gen --force, docker pull …) and exits with status 3. --force replaces the file anyway.
  • cxg update verifies the downloaded binary against the release’s SHA256SUMS before replacing anything, and refuses a release without one.
  • cxg update no longer installs or refreshes detection templates on the way.