Repository navigation
Releases
RAST 1.0.1-alpha.2
Added
-
E2E app matrix: the
app-matrixscenario (node tests/e2e/run.mjs --scenario=app-matrix) runs the five app checks (launcher, RAST window,
typing, saved file visible in File Station, normal close) for Chrome,
Firefox, VS Code and LibreOffice, with typing, scroll and window-drag
responsiveness budgets, against the dev instance or against production
with at-test account only. -
About RAST (Leptos) app: the first window rendered by the new
crates/rast-uicrate (Leptos, compiled to WebAssembly and built with
Trunk). It shows the product name and version; the WASM module is fetched
from/ui/only when the window is first opened. See
docs/adr/0003-rast-ui-leptos.md. -
Per-user file agent (one HOME, ADR 0005), groundwork. No account is
switched by this version; the HOME migration comes later.- New privileged helper operations:
home_ensure(prepares
<storage>/homes/<username>as the person's own Linux account's 0700
HOME with~/.config,~/.cacheand~/.local/…, and sets it as the
account's home),files_agent_startandfiles_agent_stop(the
socket-activated unitrast-files-u<uid>, running asrast-u<id>).
Removing a Linux identity, or deactivating the account, also stops its
file agent. - New hidden subcommand
rast file-agent: File Station over one HOME,
with the same safe-path checks and JSON shapes,writablefrom the
Linux account, and a realtime stream of changes in the visible tree.
/shared/<name>is the container that the server reads from its
database and sends in a header only the server sets; the agent opens it
directly below the shared root, checks its owner and group, and never
follows~/Shared/<name>links (they are for apps). - File Station forwards the requests of a one-HOME account (HOME owned by
its Linux identity,native_enabledon) to that account's agent after
the usual session, CSRF, path, shared-folder access, quota and audit
checks.503when the agent cannot be started. Legacy accounts are
unchanged. - Hardening from the task 1.2 security review: chunked uploads of such
accounts have the in-process limits (8 at a time per account, 64 in
all, then429); downloads, previews and other streamed agent replies
reach the browser with the agent's file headers only, and the server
setsX-Content-Type-Options: nosniffand a sandboxing CSP itself; the
agent cannot be traced by the account's other processes;home_ensure
never takes over a folder that was swapped in while it was being
created. - The file agent works through directory descriptors: every path is
opened below HOME or the shared folder withopenat2
(RESOLVE_BENEATH, no symlinks; below a shared folder also
RESOLVE_NO_XDEV, so a mount inside a shared folder, such as a
member's FUSE mount, is never entered; searches, sizes, copies and
removals below a shared folder also leave out every entry on another
file system), new files are created with
O_EXCL | O_NOFOLLOW, and copy, move and upload keep the folders they
checked open. A symlink that another member of a shared folder swaps in
during an operation can no longer make the agent copy the account's own
files (~/.ssh) into the share or write into~/.config/autostart. - Starting one account's file agent no longer holds up the File Station
requests of other accounts. Copy and move jobs and other forwarded
requests report the agent's403,404,413,415and429as
such (they were400). When an agent's socket unit was restarted with a
new token, the server asks the helper again once instead of answering
403until it restarts; an upload interrupted this way gets503. - Files that the agent uploads or copies into a shared folder are
read-write for the folder's members (0660, 0770 for executables)
instead of keeping 0644 or the source's bits, which would have taken
write access away from the other members once shared folders use Linux
groups. A move between HOME and a shared folder, or between two shared
folders, is a copy followed by a delete, so the moved files get the
destination's group and permissions; moves inside one folder tree are
still renames.
- New privileged helper operations:
-
Shared folders as Linux groups (ADR 0005, task 1.3).
- New privileged helper operations:
share_group_ensure,
share_group_removeandshare_members_set(one read-write group
rast-s<h>-rwand one read-only grouprast-s<h>-roper shared
folder, with gids fromlinux_uid_base + 1000001to
linux_uid_base + 1999999; members are replaced as a whole with
gpasswd -M, at most 8 000 per group; an accountrast-u<id>whose
uid is not the identity's is never added, is taken out of the groups
and is reported, while the other members are still set, and
rast doctorlists such accounts);share_dir_prepare(the
container becomesroot:rast-s<h>-rw2770 with the ACL
g:rast-s<h>-ro:r-x,u:rast:rwxand the same default ACL, and with
recursiveevery folder and file in it gets the group, group write
and the ACL);share_dir_remove; andshares_migrate_scan,
shares_migrate_applyandshares_migrate_rollbackfor
rast migrate shares. None takes a path: containers are one folder
name in<storage>/shared. - Further helper operations:
share_dir_repair(the recursive prepare
of a container that already has the layout; legacy containers are
left for the migration),share_deny_set(the exact set of
u:rast-u<id>:---entries on a prepared container, at most 256,
which every prepare keeps) and the read-onlyshare_session_groups
(which share groups the running processes of up to 200 users carry,
from/proc/<pid>/status). Only processes in the user's own units
(session, file agent, apps, terminals, from/proc/<pid>/cgroup)
whose real and effective uid are the identity count, so a set-uid
program of one user run by another no longer makes the first user's
session restart again and again; both files are read through one
descriptor of/proc/<pid>, so a reused pid is never read as the
process it replaced. - The helper walks shared folders through directory descriptors and
changes entries withfchown,fchmodandfsetxattron the open
descriptor, so a member who swaps an entry for a symlink cannot point
root anywhere else. Symlinks, special files, files with more than one
hard link, entries owned by root, entries owned by any account other
thanrastand the RAST identities (such as a file another account
owns that was hard-linked in and whose original was since removed) and
other file systems and mounts are left unchanged and reported. Mounts
are told apart by mount id (statx, Linux 5.8 or later), so a bind
mount on the same file system inside a shared folder is never entered
or emptied, a container that is itself a mount point is refused, and
removing a shared folder stops at a mount point inside it. Operations
on one shared folder's container never overlap: each holds a per-share
lock in the helper (share_busyafter 10 seconds, retried by the
server), and the migration apply and rollback also hold aflockin
the share's journal folder, so a rollback never runs beside an apply
whose CLI was killed. A walk holds at
most 1 000 000 names at a time: a member's folder with more names is
refused before they fill the helper's memory. shares_migrate_applywrites a journal of every group, mode and ACL
to<data_dir>/migrations/shares/<shareId>/<stamp>/journal.jsonl
(root, 0700/0600) and syncs it before changing anything; an apply that
stopped half way resumes with that journal. The rollback reads the
journal as untrusted input (root-owned folders only, no root owner or
group, set-uid bits dropped) and restores only entries that are still
the recorded inode with the recorded owner.
- New privileged helper operations:
-
rast migrate shares(ADR 0005, section 8). Moves the shared folders
of an existing install to the group layout, beforerast migrate home.
Run it as the service user:sudo -u rast rast migrate shares --dry-run
reports per shared folder what would change (entries, skipped symlinks,
hard-linked files, root-owned entries, old per-user ACL entries, and
every entry whose ACL holds entries RAST does not manage, with those
entries, since the apply replaces the whole ACL) and may
run while the server runs;rast migrate shares(apply) and
rast migrate shares --rollbackneed the server stopped. Every mode takes
--share <name>(one shared folder) or--all(every one),--json
gives a machine-readable report.
Each shared folder is migrated on its own and a failure does not stop the
others (exit code 1). The apply writes a journal first and resumes an
interrupted run; the rollback restores owners, modes and ACLs from it.
The rollback never restores set-uid bits, nor set-gid bits of regular
files (set-gid on folders is restored), and lists every entry that lost
a bit; the full list is kept next to the journal
(<stamp>.rolled-back/dropped-bits.txt). The command and the server's
repair pass wait up to an hour per shared folder for the helper (they
gave up after 15 seconds while the helper went on working, so a large
share was reported as failed in the middle of its apply).
Creating groups and setting their members waits up to two minutes. -
rast migrate home(ADR 0005, section 8, task 1.5). Moves a legacy
account into one-HOME mode: its HOME, app data and recycle bin become its
Linux account's (rast-u<id>). Run it as the service user, after
rast migrate shares, for one account at a time
(sudo -u rast rast migrate home --user <name> [--dry-run | --rollback])
or, only wh...
RAST 1.0.1-alpha.1
Added
-
E2E app matrix: the
app-matrixscenario (node tests/e2e/run.mjs --scenario=app-matrix) runs the five app checks (launcher, RAST window,
typing, saved file visible in File Station, normal close) for Chrome,
Firefox, VS Code and LibreOffice, with typing, scroll and window-drag
responsiveness budgets, against the dev instance or against production
with at-test account only. -
About RAST (Leptos) app: the first window rendered by the new
crates/rast-uicrate (Leptos, compiled to WebAssembly and built with
Trunk). It shows the product name and version; the WASM module is fetched
from/ui/only when the window is first opened. See
docs/adr/0003-rast-ui-leptos.md. -
Per-user file agent (one HOME, ADR 0005), groundwork. No account is
switched by this version; the HOME migration comes later.- New privileged helper operations:
home_ensure(prepares
<storage>/homes/<username>as the person's own Linux account's 0700
HOME with~/.config,~/.cacheand~/.local/…, and sets it as the
account's home),files_agent_startandfiles_agent_stop(the
socket-activated unitrast-files-u<uid>, running asrast-u<id>).
Removing a Linux identity, or deactivating the account, also stops its
file agent. - New hidden subcommand
rast file-agent: File Station over one HOME,
with the same safe-path checks and JSON shapes,writablefrom the
Linux account, and a realtime stream of changes in the visible tree.
/shared/<name>is the container that the server reads from its
database and sends in a header only the server sets; the agent opens it
directly below the shared root, checks its owner and group, and never
follows~/Shared/<name>links (they are for apps). - File Station forwards the requests of a one-HOME account (HOME owned by
its Linux identity,native_enabledon) to that account's agent after
the usual session, CSRF, path, shared-folder access, quota and audit
checks.503when the agent cannot be started. Legacy accounts are
unchanged. - Hardening from the task 1.2 security review: chunked uploads of such
accounts have the in-process limits (8 at a time per account, 64 in
all, then429); downloads, previews and other streamed agent replies
reach the browser with the agent's file headers only, and the server
setsX-Content-Type-Options: nosniffand a sandboxing CSP itself; the
agent cannot be traced by the account's other processes;home_ensure
never takes over a folder that was swapped in while it was being
created. - The file agent works through directory descriptors: every path is
opened below HOME or the shared folder withopenat2
(RESOLVE_BENEATH, no symlinks; below a shared folder also
RESOLVE_NO_XDEV, so a mount inside a shared folder, such as a
member's FUSE mount, is never entered; searches, sizes, copies and
removals below a shared folder also leave out every entry on another
file system), new files are created with
O_EXCL | O_NOFOLLOW, and copy, move and upload keep the folders they
checked open. A symlink that another member of a shared folder swaps in
during an operation can no longer make the agent copy the account's own
files (~/.ssh) into the share or write into~/.config/autostart. - Starting one account's file agent no longer holds up the File Station
requests of other accounts. Copy and move jobs and other forwarded
requests report the agent's403,404,413,415and429as
such (they were400). When an agent's socket unit was restarted with a
new token, the server asks the helper again once instead of answering
403until it restarts; an upload interrupted this way gets503. - Files that the agent uploads or copies into a shared folder are
read-write for the folder's members (0660, 0770 for executables)
instead of keeping 0644 or the source's bits, which would have taken
write access away from the other members once shared folders use Linux
groups. A move between HOME and a shared folder, or between two shared
folders, is a copy followed by a delete, so the moved files get the
destination's group and permissions; moves inside one folder tree are
still renames.
- New privileged helper operations:
-
Shared folders as Linux groups (ADR 0005, task 1.3).
- New privileged helper operations:
share_group_ensure,
share_group_removeandshare_members_set(one read-write group
rast-s<h>-rwand one read-only grouprast-s<h>-roper shared
folder, with gids fromlinux_uid_base + 1000001to
linux_uid_base + 1999999; members are replaced as a whole with
gpasswd -M, at most 8 000 per group; an accountrast-u<id>whose
uid is not the identity's is never added, is taken out of the groups
and is reported, while the other members are still set, and
rast doctorlists such accounts);share_dir_prepare(the
container becomesroot:rast-s<h>-rw2770 with the ACL
g:rast-s<h>-ro:r-x,u:rast:rwxand the same default ACL, and with
recursiveevery folder and file in it gets the group, group write
and the ACL);share_dir_remove; andshares_migrate_scan,
shares_migrate_applyandshares_migrate_rollbackfor
rast migrate shares. None takes a path: containers are one folder
name in<storage>/shared. - Further helper operations:
share_dir_repair(the recursive prepare
of a container that already has the layout; legacy containers are
left for the migration),share_deny_set(the exact set of
u:rast-u<id>:---entries on a prepared container, at most 256,
which every prepare keeps) and the read-onlyshare_session_groups
(which share groups the running processes of up to 200 users carry,
from/proc/<pid>/status). Only processes in the user's own units
(session, file agent, apps, terminals, from/proc/<pid>/cgroup)
whose real and effective uid are the identity count, so a set-uid
program of one user run by another no longer makes the first user's
session restart again and again; both files are read through one
descriptor of/proc/<pid>, so a reused pid is never read as the
process it replaced. - The helper walks shared folders through directory descriptors and
changes entries withfchown,fchmodandfsetxattron the open
descriptor, so a member who swaps an entry for a symlink cannot point
root anywhere else. Symlinks, special files, files with more than one
hard link, entries owned by root, entries owned by any account other
thanrastand the RAST identities (such as a file another account
owns that was hard-linked in and whose original was since removed) and
other file systems and mounts are left unchanged and reported. Mounts
are told apart by mount id (statx, Linux 5.8 or later), so a bind
mount on the same file system inside a shared folder is never entered
or emptied, a container that is itself a mount point is refused, and
removing a shared folder stops at a mount point inside it. Operations
on one shared folder's container never overlap: each holds a per-share
lock in the helper (share_busyafter 10 seconds, retried by the
server), and the migration apply and rollback also hold aflockin
the share's journal folder, so a rollback never runs beside an apply
whose CLI was killed. A walk holds at
most 1 000 000 names at a time: a member's folder with more names is
refused before they fill the helper's memory. shares_migrate_applywrites a journal of every group, mode and ACL
to<data_dir>/migrations/shares/<shareId>/<stamp>/journal.jsonl
(root, 0700/0600) and syncs it before changing anything; an apply that
stopped half way resumes with that journal. The rollback reads the
journal as untrusted input (root-owned folders only, no root owner or
group, set-uid bits dropped) and restores only entries that are still
the recorded inode with the recorded owner.
- New privileged helper operations:
-
rast migrate shares(ADR 0005, section 8). Moves the shared folders
of an existing install to the group layout, beforerast migrate home.
Run it as the service user:sudo -u rast rast migrate shares --dry-run
reports per shared folder what would change (entries, skipped symlinks,
hard-linked files, root-owned entries, old per-user ACL entries, and
every entry whose ACL holds entries RAST does not manage, with those
entries, since the apply replaces the whole ACL) and may
run while the server runs;rast migrate shares(apply) and
rast migrate shares --rollbackneed the server stopped. Every mode takes
--share <name>(one shared folder) or--all(every one),--json
gives a machine-readable report.
Each shared folder is migrated on its own and a failure does not stop the
others (exit code 1). The apply writes a journal first and resumes an
interrupted run; the rollback restores owners, modes and ACLs from it.
The rollback never restores set-uid bits, nor set-gid bits of regular
files (set-gid on folders is restored), and lists every entry that lost
a bit; the full list is kept next to the journal
(<stamp>.rolled-back/dropped-bits.txt). The command and the server's
repair pass wait up to an hour per shared folder for the helper (they
gave up after 15 seconds while the helper went on working, so a large
share was reported as failed in the middle of its apply).
Creating groups and setting their members waits up to two minutes. -
rast migrate home(ADR 0005, section 8, task 1.5). Moves a legacy
account into one-HOME mode: its HOME, app data and recycle bin become its
Linux account's (rast-u<id>). Run it as the service user, after
rast migrate shares, for one account at a time
(sudo -u rast rast migrate home --user <name> [--dry-run | --rollback])
or, only wh...
RAST 0.18.3
Fixed
- Native Linux apps could not see the person's own files. Opening an
app, and moving a Docker app to the native backend, linked and granted read
access tohomes/rast-u<id>(named after the app's Linux account) instead
of the person's homehomes/<username>. The folder was created empty, so
apps never saw the person's files. Apps now get the person's own home, as
docs/NATIVE-LINUX-APPS.mddescribes, and RAST no longer creates
homes/rast-u<id>folders. - An app could read another account's home. Because of the bug above,
an app of user id 5 was granted read access to the home of an account
namedrast-u5, if one existed. New usernames of the form
rast-u<number>are now refused, so such a name cannot be chosen again.
Changed
- Opening a native app no longer waits for the home access grant. The
recursive read ACL on the person's home now runs in the background, at most
one at a time per person. Measured on ext4 with a warm cache: about 0.4 s
for 100,000 files and 1.1 to 2.9 s for 300,000 files, which a blocking
grant would add to every app start.
Upgrade notes
- After upgrading, empty
homes/rast-u<id>folders left by earlier versions
can be removed by an administrator; RAST does not delete them. An existing
account whose username has the formrast-u<number>keeps working, and
apps of other users no longer reach its home. - The first app start after the upgrade grants the app's Linux account
read access to the person's home (recursiverxACL), as documented. Apps
still save into their own profile. The grant runs in the background, so on
the first app start the person's files can become readable a few seconds
after the app window opens. The helper stops a grant after 13 seconds, so a
home with more than about 1.5 million files and folders only gets a partial
grant. - The grant also adds a default ACL entry for the app's Linux account to
every folder in the home (d:u:rast-u<id>:rx), so files created later are
readable by the app at once. Files moved into the home (chunked uploads,
restores from the recycle bin, moves from shared folders) become readable
at the next app start.
Installation
curl -fsSL https://github.com/Enricko/rast/releases/download/v0.18.3/install.sh | sudo shPin this exact release:
curl -fsSL https://github.com/Enricko/rast/releases/download/v0.18.3/install.sh | sudo sh -s -- --version 0.18.3Upgrading 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 --helpRuntime 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/rastProvenance 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.
RAST 0.18.2
Fixed
- Composer could not be installed or updated ("PHP's phar extension is
missing"). The version check that ends an install runs in a sandbox that
could reach neither the PHP that App Center installed nor the
configuration of the distribution's PHP (/etc/php, where the phar
extension is enabled), so Composer started on a PHP without phar. A check
of an official package now finds the runtimes App Center installed, ahead
of the system's, exactly as a terminal does, and the system PHP reads its
configuration. Imported packages still see only their own files.
Installation
curl -fsSL https://github.com/Enricko/rast/releases/download/v0.18.2/install.sh | sudo shPin this exact release:
curl -fsSL https://github.com/Enricko/rast/releases/download/v0.18.2/install.sh | sudo sh -s -- --version 0.18.2Upgrading 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 --helpRuntime 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/rastProvenance 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.
RAST 0.18.1
Fixed
- An idle Terminal kept reconnecting and repeating its screen. Behind a
reverse proxy or tunnel that closes quiet WebSockets (Cloudflare: after 100
seconds), a terminal nobody typed in was disconnected again and again, and
every reconnect printed the session's recent output below what was already
shown, hiding the command being typed. The server now pings the connection
every 20 seconds so it stays open, and rejoining a session redraws the
screen instead of adding to it.
Installation
curl -fsSL https://github.com/Enricko/rast/releases/download/v0.18.1/install.sh | sudo shPin this exact release:
curl -fsSL https://github.com/Enricko/rast/releases/download/v0.18.1/install.sh | sudo sh -s -- --version 0.18.1Upgrading 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 --helpRuntime 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/rastProvenance 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.
RAST 0.18.0
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 andrast user create-adminaccounts 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
withfiles_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. @rootis 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
intermittentrole_enforcement_and_user_managementfailure).
Installation
curl -fsSL https://github.com/Enricko/rast/releases/download/v0.18.0/install.sh | sudo shPin this exact release:
curl -fsSL https://github.com/Enricko/rast/releases/download/v0.18.0/install.sh | sudo sh -s -- --version 0.18.0Upgrading 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 --helpRuntime 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/rastProvenance 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.
RAST 0.17.4
Fixed
- A terminal with
terminal_admin_accountdid not start ("the terminal
unit did not start"): the login account could not enter RAST's terminal
runtime directory to create the agent socket. The directory is now
traversable for it, as it already was for ordinary users' identities.
Broken in 0.17.2 and 0.17.3.
Installation
curl -fsSL https://github.com/Enricko/rast/releases/download/v0.17.4/install.sh | sudo shPin this exact release:
curl -fsSL https://github.com/Enricko/rast/releases/download/v0.17.4/install.sh | sudo sh -s -- --version 0.17.4Upgrading 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 --helpRuntime 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/rastProvenance 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.
RAST 0.17.3
Fixed
- A terminal that runs as a login account (
terminal_admin_account) gets the
umask of that account's login session (pam_umask:UMASKfromlogin.defs
withUSERGROUPS_ENAB,0002on Debian/Ubuntu) instead of0022, so files
created there have the same permissions as over SSH.
Installation
curl -fsSL https://github.com/Enricko/rast/releases/download/v0.17.3/install.sh | sudo shPin this exact release:
curl -fsSL https://github.com/Enricko/rast/releases/download/v0.17.3/install.sh | sudo sh -s -- --version 0.17.3Upgrading 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 --helpRuntime 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/rastProvenance 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.
RAST 0.17.2
Added
terminal_admin_account: the administrators' Terminal as a Linux login
account, exactly like SSH. Set it to the account you log in to the server
with (it must be insudo,adminorwheel) and an administrator's
terminal is a login shell of that account instead of a root shell: its own
home, groups,~/.profile/~/.bashrc, version managers and tool logins
(rustup's toolchain,claudewith its sign-in and skills, …), withsudo
for root. Nothing RAST-specific is added to that environment and the
Terminal runtime selection does not apply to it. A folder the account
cannot enter (Open in Terminal) starts in its home instead.
Installation
curl -fsSL https://github.com/Enricko/rast/releases/download/v0.17.2/install.sh | sudo shPin this exact release:
curl -fsSL https://github.com/Enricko/rast/releases/download/v0.17.2/install.sh | sudo sh -s -- --version 0.17.2Upgrading 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 --helpRuntime 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/rastProvenance 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.
RAST 0.17.1
Added
- Root terminals run the tools of the server's administrators. Commands
installed for the Linux account of someone who may already become root
(members ofsudo,adminorwheel) —claude,uv, rustup'scargo,
opencode, pnpm, Bun, Deno, a Flutter checkout, … in~/.local/bin,
~/.cargo/binand the other usual per-user directories — are on thePATH
of an administrator's root shell. They come last, so they never shadow a
system command or an App Center default; directories other accounts can
write to are left out. - App Center finds runtimes installed in an administrator's home, such as
rustup's Rust in~/.cargo/bin, and lists them as System installs with
the verified version as an update. The privileged helper looks (the service
cannot read/home) and runs version commands as the owning account.
Flutter is detected too; its version is read from the SDK instead of
runningflutter. terminal_path_extra: further directories to append to thePATHof
administrator root shells.
Installation
curl -fsSL https://github.com/Enricko/rast/releases/download/v0.17.1/install.sh | sudo shPin this exact release:
curl -fsSL https://github.com/Enricko/rast/releases/download/v0.17.1/install.sh | sudo sh -s -- --version 0.17.1Upgrading 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 --helpRuntime 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/rastProvenance 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.