Repository navigation
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.