Skip to content

RAST 0.18.0

Choose a tag to compare

@github-actions github-actions released this 15 Nov 11:34

Added

  • Three roles: super administrator, administrator and user. A super
    administrator is the server owner: besides everything an administrator
    does, they get the server itself (the root file system in File Station and
    the root shell in Terminal) and they alone create, change, disable or reset
    administrator accounts and change roles. An administrator runs RAST for its
    people (users, groups, shared folders, apps, backups, settings) without the
    server's own files or shells. Control Panel → Users shows and sets the
    three roles. The first account and rast user create-admin accounts are
    super administrators; the last active one cannot be demoted or disabled.
  • Root file system in File Station, for super administrators. File
    Station now has three places: Home (your own storage), Shared
    folders
    , and Server → Root file system, the server's own files from
    / with full access as root: browse, preview, download, upload (resumable),
    new folder, rename, copy, move and delete. There is no quota and no recycle
    bin there, so a delete is permanent and every change asks first. New files
    get the owner of their folder; a replaced file keeps its owner and mode.
    Changes and downloads are in the activity log. Turn it off for everyone
    with files_root_enabled = false.

Changed

  • Upgrade note (schema v14): every administrator that exists at the
    upgrade becomes a super administrator, so nobody loses access. Demote the
    accounts that should only run RAST in Control Panel → Users.
  • The root (or terminal_admin_account) shell in Terminal is for super
    administrators. Administrators without that level get the unprivileged
    identity, like selected users; a root terminal closes when its owner stops
    being a super administrator.
  • @root is a reserved name for new files and folders in Home and shared
    folders.

Fixed

  • The in-process access cache is keyed per database as well as per account.
    A single server was never affected; the test suite, which runs several
    servers in one process, could read another server's decision (the
    intermittent role_enforcement_and_user_management failure).

Installation

curl -fsSL https://github.com/Enricko/rast/releases/download/v0.18.0/install.sh | sudo sh

Pin this exact release:

curl -fsSL https://github.com/Enricko/rast/releases/download/v0.18.0/install.sh | sudo sh -s -- --version 0.18.0

Upgrading an existing installation preserves /etc/rast, /var/lib/rast and /srv/rast.

Release assets

Asset Description
rast-linux-x86_64 Static frontend embedded; x86_64 Linux (glibc >= 2.35)
rast-linux-aarch64 Static frontend embedded; aarch64 Linux (glibc >= 2.39)
SHA256SUMS SHA-256 checksums for every asset
install.sh Installer (POSIX sh, pinned to this release)
uninstall.sh Uninstaller
rast.toml.example Fully commented configuration reference

Verification

sha256sum -c SHA256SUMS
sh install.sh --help

Runtime verification

Both binaries were smoke-tested on their native build runners
(GitHub-hosted x86_64 and arm64): the server started with a temporary
config, answered /healthz, accepted CLI administrator creation and a
JSON API login. This workflow does not exercise native Xpra window/input
or audio playback. The separate disposable-systemd installer harness
can be run with scripts/test-installer-clean.sh; its results are not
implied by a successful release build.

Provenance

Both binaries and SHA256SUMS carry GitHub artifact attestations
(Sigstore keyless build provenance). Verify them after downloading:

gh attestation verify rast-linux-x86_64 --repo Enricko/rast
gh attestation verify rast-linux-aarch64 --repo Enricko/rast
gh attestation verify SHA256SUMS --repo Enricko/rast

Provenance proves the files were built by this repository's release
workflow for the tagged commit; it is not a reproduction or code-review
guarantee. The installer can enforce it with --verify-attestation.