Skip to content

Guardana Control 0.9.0-alpha

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 07 Oct 13:05
· 175 commits to main since this release
Immutable release. Only release title and notes can be modified.

A confirmed finding can now stop the run it is about. An operator signs a
route that says which findings may stop a run and which key lifts a stop,
and starts a stop list; after guardana-control supervise,
guardana-control react writes a stop for each deterministic, confirmed
finding the route allows about an opened run that is still open. A plane
configured with the route refuses that run's later calls, and no other
run's, and blocks every call while it cannot read or trust the list. A call
already running is not cut, and only a lift signed with the route's lift key
ends a stop while a plane runs. The refund example shows it on a live plane
with two runs. The other changes and fixes come from an audit of 0.8.0, and
four of them matter on upgrade. The gateway refuses a configuration file
when it, or a directory or link on its path, belongs to an account other
than its own or root, when another account or its group may write it, or
when it has a second name: a checkout under a umask of 002 needs
chmod g-w, and a container's configuration has to be owned by the image's
user. An upstream that asks for more input ends the call as failed. A second
override of one tool is refused at start. runs open --parent refuses a
child whose expiry would pass its parent's.

Added

  • A confirmed finding can stop the run it is about
    (ADR-0046).
    An operator signs a route with guardana-control route sign, naming the
    procedures and rules whose findings may stop a run and the key that lifts a
    stop, and starts a stop list with stops init. guardana-control react
    appends a stop for each deterministic, confirmed finding the route allows,
    about an opened run that is open, and never lifts one; stops lift, signed
    with the lift key, ends a run's stops, and stops list shows them. A plane
    configured with the reaction keys checks the route against its own floor
    at start and reads the list every poll interval: a stopped run's later calls
    are refused RUN_STOPPED (45) and no other run's, and every call is blocked
    STOP_STATE_UNAVAILABLE (46) while the list cannot be read, shrinks, is
    rewritten or does not verify. A call already running is not cut, and a
    stopped run's children are not stopped. doctor, /healthz and /metrics
    report the route and the list; examples/refund-supervision/ stops one of
    two runs on a live plane and lifts the stop.

Changed

  • The policy key and the freshness key, in the configuration and in
    guardana-control policy renew, are compared as points up to their sign:
    one private key signs for a point and its negation, so two keys that
    differ only there were taken as two authorities.
  • An upstream that answers a call, a read or a prompt with input_required, or
    with input requests of any kind, ends that call as failed, with a fixed
    answer the gateway does not relay. The
    library had sent the same call to the upstream again on its own, up to ten
    times, for the one call the plane decided and recorded.
  • A second override of the same tool on one upstream is refused at start. The
    last one won, so an effect: READ after an effect: DELETE classified a
    delete as a read.
  • guardana-control runs open --parent refuses a child whose expiry would
    pass its parent's.
  • The MCP adapter refuses an obligation that carries a parameter its type does
    not read, as the gateway already did; a non-advisory one stops the call. The
    obligations page lists the parameters each type reads.
  • The gateway refuses a configuration file when the file, or any directory or
    link on its path, is owned by an account other than its own or root, or
    another account may write it (a sticky directory, or root's on a read-only
    mount, excepted), and a file with a second name. Its group may not write it
    either: a checkout under a umask of 002 needs chmod g-w. The file names
    the policy keys, the pause file and the credentials the plane sends, and was
    read whatever its owner and mode. A container's configuration now has to be
    owned by the image's user.
  • Each agent connection gets a 64 KiB send buffer, so on Linux, as on macOS,
    the answer bound measures a slow client's progress in steps of that size.
    Linux grows a connection's buffer to megabytes, which cut off a client
    reading steadily but slowly.

Fixed

  • A plane whose policy floor is read back below the statement it confirmed,
    a copy restored from before its raise, counts the poll as refused under
    floor and logs it; it went unremarked.
  • guardana-control coverage counts a span that claims two parents once, so
    a few dozen observations whose spans form a ladder of diamonds no longer cut
    a walk as past 65,536 spans. Counting such spans is bounded per source, and
    a count past that bound cuts the walk.
  • The evidence-report example stops reading an endless line at the export's
    byte bound, and refuses a header without a well-formed source and a cursor
    that is not one of its file; the demo's call.sh exits 1 on an HTTP status
    that is not 2xx. The benchmarks page's argument sizes are what the
    benchmarks measure now, held by a test.
  • A release refuses a commit while main has an open CodeQL alert of severity
    high or critical, and its verification requires a bill of materials for each
    archive, not one for all. The gate refuses lint ignore comments in the
    protocol files, compares the installed tools with their pins, and holds the
    CI job that runs it, the secret scan's configuration and the code owners of
    every guarded tree to what they must be.
  • An agent that cancels a call no longer leaves its trail without a closing
    record, a held request open for the plane's life, or a sink failure counted
    for a sink that did not fail: once proposed, a call's records, its hold and
    its consume finish whatever the agent does.
  • A call whose opened run the plane cannot read or name is blocked before the
    external decision point is asked about it.
  • An approval or a rejection the store returns that does not check out (another
    major, another request time, no decision time or one outside the request's
    window, another id, a state that is not an answer) is recorded as the plane's
    own expired approval, never as decided. An agent that
    cancels before its approval is consumed spends nothing.
  • guardana-control observe export judges the log as the reader does: a link,
    a file another account owns, one the group or others may reach, or one with
    a second name is refused; it was exported.
  • An observation import refuses a write that would take the log past its
    1 GiB bound, which the reader then refused.
  • Coverage counts a source's records only in the tenant and project its
    descriptor names; bounds each walk of a trace's spans on its own, walking a
    long chain once, and a walk cut at its bound reads not checked and exits 1,
    since an agent can cut one on purpose; and prints a join as not checked where the plane's
    record of that call does not validate, rather than as joined or as a call
    around the plane.
  • Supervision tells no order between two steps whose proposals, in two
    planes' exports, carry the same time; the order of the --evidence flags
    decided it.
  • doctor judges the approvals and hold journal directories for owner and
    mode as run does; it reported ok for a directory run refuses. It also
    names the bytes of a torn evidence tail it cut, and a floor directory that
    would not close is no longer ok.
  • A scenario step whose arguments canon cannot hash compares the recorded
    proposal's hash with none, where it printed "not compared" and passed.
  • The runs directory's reader refuses a string that is not valid Unicode. It
    read an unpaired surrogate or a bad byte as U+FFFD, so two different files
    could read as one record.
  • A plane whose bundle and statement do not change judges its serial floor at
    every poll as a raise would, and counts a floor it cannot read, one holding a
    newer serial or another digest at its serial, and a clock behind it, as a
    refused poll; it read the floor only when a file changed.
  • With an authenticator that names no user, the forwarded resource, template
    and prompt lists are refused as the tool list is.
  • An approval whose own schema version is not of major 1 is refused when it is
    held, answered or read, and an answer dated after the moment it would be
    spent, or with no date, is not yet an answer.
  • The hold journal, and the markers of the approvals and journal directories,
    refuse a member named twice, in another case or unknown, and the journal an
    expiry spelled otherwise than the plane writes it.
  • The start's sweep of expired approval records says it is unmeasured when the
    directory holds more records than approvals.max_records; it gave a count
    as if it had read them all.
  • The approvals page refuses an answer to an id an incomplete listing left out
    as unknown, where it said there was no such approval.

Image: ghcr.io/guardana/control-gateway@sha256:487abb8361c24f756385f86ee46962380005bdf1df8e5686704e5240a86b039a