Skip to content

Korely Agents 1.0.26

Choose a tag to compare

@verdana86 verdana86 released this 15 Nov 09:18
· 2 commits to main since this release

1.0.25 with the old secret of a rotated key holding no admin, every
request that comes during the proxy's first name lookup waiting for it, and
a check of the public copy for lines that name what only Korely Cloud has.
From 1.0.25, the one thing to look at is the old secret, in "Before and
after upgrading" below; from 1.0.22, read the 1.0.25, 1.0.24 and 1.0.23
entries too.

Before and after upgrading

  • No migration and no new setting.
  • The old secret of a rotated key holds no admin. During a rotation's
    overlap, a script that still sends the old secret to an /admin route
    gets 403 previous_secret_has_no_admin and nothing changes; one that
    erases with it an end user to whom a key is confined alone (DELETE /v1/users/{id}/memories) gets 403 previous_secret_cannot_manage_keys
    and nothing is erased. Send the key's current secret, the one the rotation
    answered with. Every other call of the key's scopes goes on working with
    the old secret until it ends.

Security

  • A leaked key's holder no longer has admin with the old secret.
    During the overlap (old_key_expires_in_hours, 24 by default) the old
    secret of an admin key was the key in full: its holder could rotate the
    key again with no overlap, end the new secret its owner had just taken
    and receive the newest (the security review of 14 Nov 2026), delete a
    project, which moves its keys, or set the model provider's key, which
    outlives the overlap (the skeptic's review of 15 Nov 2026). Now a request
    let in with the old secret holds the key's scopes but admin, as a key
    Stripe rolls keeps working for API calls (https://docs.stripe.com/keys):
    every /admin route refuses it as it refuses a key without admin, so
    it makes no webhook either (those made before stay), and an erasure that
    would revoke a key as it goes is refused to it. A rotation let in with the
    current secret a moment before the owner's own committed reads the key
    again under its lock, and is refused too. The key's current secret, and a
    person signed in to the dashboard, do all of it as before. For a key that
    leaked, rotate with "old_key_expires_in_hours": 0, or revoke it
    (Rotating a key).
  • The proxy's requests during the process's first name lookup are the
    proxy's.
    Up to 1.0.25 only the request that started the first lookup of
    the names in FORWARDED_ALLOW_IPS waited for it: a request of the proxy
    that came while it ran was served with the proxy's address and http, as
    one relayed by a stranger (one login lock and one cap per network for
    every client relayed so, /health without its details), and the
    one-time [proxy] warning said, wrongly, that the proxy was not trusted
    (found on the Cloud's deploy of 14 Nov 2026). Now every request that
    comes before the first lookup has answered waits for it, until 2 s after
    it began; a lookup that fails is no answer, never an error of the
    requests waiting for it; and the warning is said, once the names have
    answered, of any peer seen meanwhile that they leave out.

What is different

  • docs/guide/operations.md, "Your own proxy in front", says again that a
    proxy of yours keeps the paths it logs, which carry end users' ids, and
    says PUBLIC_BASE_URL, which only .env.example said.

API

  • Every /admin route: 403 previous_secret_has_no_admin for a request
    let in with the old secret of a rotation; their 403 in the OpenAPI says it.
  • DELETE /v1/users/{id}/memories: 403 previous_secret_cannot_manage_keys
    for the old secret of a rotation when the erasure would revoke a key.
  • GET /v1/ping lists the scopes the secret sent holds: the old one's
    without admin.

Tools in the repository (nothing to do for an install)

  • The checks a public copy of this repository passes before it is
    published also fail on a line that names what only Korely Cloud has
    ,
    by the names the code the copy leaves out calls itself and the words a
    sentence says them with, a sense of its own a public file gives one of
    those words allowed phrase by phrase, with why. A test runs the same check
    at the gate, and the ten lines the security reading of 1.0.25's public
    copy found are rewritten.
  • Two lines of the 1.0.23 entry pointed to notes the public copy does not
    carry; they now say what they meant where they are.