Bookmarks

    Nothing saved yet. Use the bookmark on any article. Bookmarks are kept on this device only: they stay private and work without an account.

    Settings

    Appearance

    Reading mode

    Font size

    Content width

    Line spacing

    Keyboard shortcuts

    /
    Search
    j k
    Next / previous story
    ← →
    Previous / next section (columns)
    b
    Bookmarks
    s
    Settings
    r
    Columns / scroll
    t
    Light / dark

    Saved in this browser only.

    Ping2Prompt
    Subscribe to the Weekly Brief Sign in
    Close-up of a row of server cooling fans in a rack, with chrome coolant pipes running along the right side under purple and b
    Photo by Winston Chen on Unsplash

    Teleport 18.11.10 patch: stricter phase.yaml shell errors, Beam audit replay

    Teleport

    What changed

    Teleport 18.11.10 is a patch release with three changes. Multi-line shell commands in phase.yaml now fail on the first error. The release adds support for replaying Beam audit events, including traffic captures and session end events.

    It also fixes MCP tool-list responses that dropped fields.

    Who needs to act

    If your phase.yaml files contain multi-line shell commands, review them before updating, because those commands now fail on the first error. If you use MCP tool lists, this update fixes responses that dropped fields. If you use Beam, replay of its audit events is now supported.

    Download builds from https://goteleport.com/download. Plugin builds are on cdn.teleport.dev for Linux amd64 and arm64. The full release notes are at https://github.com/gravitational/teleport/releases/tag/v18.11.10.

    What the sources don't cover

    The release notes we reviewed give no release date, no upgrade or migration guidance, and no explanation of what Beam is or who the phase.yaml change affects.

    Sources

    Image: Photo by Winston Chen on Unsplash


    This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].

    Continue

    Share on Bluesky · Mastodon · Email ·

    Discussion