Artifact Firewall 0.11.0

Released: 2026-11-18

Added

  • OCI images are now a supported ecosystem in standalone mode. Rules of type: oci match a pull by repository, tag or digest, such as pkg:oci/library/redis?tag=6.0.5, and a denied pull gets a 403.
  • Rules can also name OCI images with docker purls, such as pkg:docker/nginx@1.25.3 for a pull of library/nginx:1.25.3.
  • Audit entries carry credential_hash, a hash of the credential the request carried, and user, who it belongs to when that can be worked out.
  • New route field force_ecosystem in standalone mode, which gives every request the route matches that type instead of detecting it from the client. Set it when the firewall does not recognise the client, such as a repository manager fetching through it, whose requests would otherwise pass through unchecked. Routes of one registry can name different types, for an origin such as Artifactory that serves several ecosystems below one URL.
  • The config file’s JSON Schema says what a reload does with each field: x-reload on a field is live when a reload applies it, and restart or refused when only a restart does. x-reload-index on the root lists them all, for deployment tools that decide whether to restart the firewall after a config change.

Changed

  • /api/eval says in its 400 why a purl or a set of parameters is invalid.
  • A config reload refused because it needs a restart now names the changed settings and the git and http ruleset sources that were added, removed or edited, and when sources were only reordered, the ones that moved. It used to leave out the sources whenever a setting needed a restart too, and named none when sources were only reordered.
  • A ruleset now fails to load, and -validate-rulesets reports it, when a rule’s version is a malformed vers: range or a range written as an exact version: where a single version is expected, as the whole of an exact version or after the comparator of each vers: constraint, percent-encoded or not, a version that starts with !, ^, ~, *, [ or (, or contains <, >, =, |, , or whitespace inside it. A vers: range with no constraints fails as well, and so does a blank version, which used to match nothing; leave version out to match every version. Whitespace around a version is ignored. vers:npm/>>1.0, vers:npm/>=1.0<2.0 and vers:pypi/>=1.0,<2.0 used to load and match nearly every version from the first bound up, and an exact ^1.2.3 or [1.0] matched no version the rule meant. Write ranges as vers:<scheme>/ constraints separated by |, such as vers:npm/>=1.0.0|<2.0.0, or vers:<scheme>/* for every version.

Fixed

  • Fixed denied NuGet versions downloading through a standalone firewall in front of nuget.org when the client fetches nuget.org’s v2 download URL, /api/v2/package/<id>/<version>, as a JFrog Artifactory remote repository does by default. The firewall now recognises it as a NuGet download, so rules apply to it.
  • A HEAD request for a package listing answered 502, so a JFrog Artifactory remote repository in front of the firewall, which sends HEAD before it fetches a listing, reported the package as not found. The HEAD now answers with the origin’s status, without the headers that describe the origin’s listing rather than the filtered one: Content-Length, Content-Encoding, Content-Type, ETag, Last-Modified and checksums. Version rules apply to the GET that follows, so a listing whose every version is blocked answers the HEAD with 200 and refuses the GET. A package denied as a whole refuses both.

®Varnish Software, Wallingatan 12, 111 60 Stockholm, Organization nr. 556805-6203