Skip to content

0.5.0

Latest

Choose a tag to compare

@github-actions github-actions released this 20 Nov 20:17
1ba09a7

SealSkin 0.5.0

Three features headline this release. The home page is now a dashboard
of applications, links, and live widgets that an administrator lays out per
group and a user makes their own. The Bakery builds new applications on
top of installed ones, with anything a Dockerfile can add. Browser
policies
start every session of an application under the Chromium or
Firefox policies an administrator sets. Beside them: a brand per host name
or group, an idle limit for sessions, Podman, and cluster-wide GPU
placement.

Dashboards

  • The home page is a grid of tiles: applications, links, link bundles,
    widgets, and headings, dragged and resized freely in edit mode.
  • Administrators lay out shared dashboards for groups and users, shown as
    tabs, and can lock one or make it a kiosk.
  • Users rearrange what they are given and add their own tiles and pages,
    kept in their browser; an administrator's later changes merge in.
  • Bookmark import, page export and import, and a reset to the
    administrator's layout.
  • Appearance settings: background, tile style, density, width, labels, and
    accent color.
  • Icons from Font Awesome, dashboard-icons, selfh.st, Simple Icons, and
    Material Design Icons, from an upload, or from the linked site itself.
  • Application tiles show a running session's mark, and its live desktop at
    two rows high.
  • Links open in a new tab, the same tab, or in a session, a browser
    inside the server's network, so internal services are reachable from
    anywhere with only SealSkin exposed. Internal addresses pick this
    automatically, reuse a running session, and may leave through a VPN
    profile.
  • Up/down status dots and {username} substitution on administrators'
    links.
  • Widgets: clock, stocks, weather, feed (RSS, Atom, JSON Feed, OPML import),
    calendar (iCalendar), API values (Homepage customapi compatible), site
    monitor, notice, custom frame, embedded page, and notes.
  • Widget data is fetched by the server, with {{secret.NAME}} credentials
    filled in on the node and never sent to a browser.
  • Custom frame widgets run an administrator's own HTML and script in a
    sandboxed frame.
  • Users can add their own clocks, notes, weather, stocks, and, where
    allowed, feeds and calendars, fetched only from the public internet.
  • Per user and group switches for customizing the page, own links, and own
    feeds and calendars.
  • With no dashboard defined, everyone sees the built-in page as before.

The Bakery

  • Build a new application on top of an installed one, under its own name
    and icon, with any number of bakes per base.
  • Guided mode: a list of steps beside the Dockerfile they render, live.
    Steps cover packages (with a search of what the image can install),
    Chromium, Firefox, Google Chrome, Brave, and VS Code, Ubuntu PPAs,
    downloads and AppImages, Python, Node.js, Rust, Go, and Java toolkits,
    Docker, desktop entries, launch commands, fonts, files, certificates,
    environment, proxy and mirrors, and start-up scripts.
  • Developer mode: write the Dockerfile directly, including extra build
    stages, with warnings for what a session would not survive.
  • Trial builds and trial sessions that leave what users run untouched.
  • Recipes are built on every node of a cluster and rebuilt whenever the base
    image is pulled again; a failed build keeps the last good image.
  • Baked applications work as App Laboratory bases, and Installed Apps
    shows each application under the one it is built on.
  • Requires the Docker provider.

Browser policies

  • Named sets of Chromium and Firefox enterprise policies: home page,
    bookmarks, site allow and block lists, extensions, certificates, and
    everything else the engines support on Linux.
  • An editor with a tab per engine, common settings first, search across
    every policy, and the engines' own translations.
  • Chromium settings can be enforced or set as user-changeable defaults.
  • A JSON view that imports an existing policy file whole.
  • Assigned per application in its install dialog and inherited by meta-apps
    and baked applications.
  • Mounted read-only into every session for Chromium, ungoogled-chromium,
    Helium, Google Chrome, Brave, Edge, Opera, Vivaldi, Firefox, LibreWolf,
    Zen, and Mullvad Browser, in single-browser images and full desktops.

Also new

  • A brand per host name or group. Beside the brand everyone sees, an
    administrator can give a brand of its own to the host names the web app is
    reached at (portal.example.org, *.example.org), to the members of
    groups, or both: name, logo, accent color, wallpaper, and home page links.
    The sign-in page and the installed web app use the host name's brand; a
    group's brand shows after sign-in.
  • An idle limit. session_idle_minutes, per user or per group, stops a
    session nobody has had open for that many minutes. A session left open in
    a tab counts as open, and so does one whose image does not report its
    connections.
  • Podman. The server runs on Podman, rootful or rootless, including on
    SteamOS. It recognizes its own Podman container, gives NVIDIA GPUs to
    sessions as CDI devices, and logs an error at startup when its container
    is on no network it can share with sessions.
  • GPUs across a cluster. Nodes report the kind and driver of their GPUs,
    and a launch goes only to a node with a free GPU of a kind its application
    supports. The launchers list every node's GPUs, with Any NVIDIA GPU and
    Any DRI3 GPU. SEALSKIN_NODE_GPUS limits the GPUs a node offers, and
    SEALSKIN_NODE_GPU_PREFER picks the kind a launch for any GPU gets.
  • Application icons. A store application's icon can be replaced, and a
    manual application given one, with an upload in its install dialog;
    Reset takes it back.
  • Selkies 2.3.0. The template editor's variables follow Selkies 2.3.0
    and the LinuxServer.io base images built on it, and keep working with
    those on 2.2.1.

Server

  • POST /api/sessions/<id>/open_url hands a web address to a running
    session's application, which opens it beside what it already has open.
  • Docker session containers are named sealskin-<first eight characters of the session id>-<suffix>, the prefix Kubernetes session pods already
    have, instead of Docker's random names.
  • A server refuses to start while another container runs under its name,
    since a server's name is its identity in its records and its cluster.
  • An address a launch opens must be http, https, ftp, or a magnet
    link with no spaces, so nothing shaped like an option reaches the
    application's command line.
  • An uploaded application icon is read as a PNG, JPEG, WebP, GIF, ICO, or BMP
    picture and kept as a PNG at most 512 pixels wide; anything else is
    refused.
  • Every page the server serves runs only its own scripts, under a
    Content-Security-Policy. The room's page also allows the workers it
    builds, and a frame widget's page is sandboxed into an origin of its own.
  • A user's own widget, and a site icon a user asks for, are fetched only when
    every address the name resolves to is public, at every redirect, with no
    credential.
  • A web sign-in with the root key lasts until it is signed out, the key is
    revoked, replaced, or expires, or the node's root_sign_in is turned off,
    instead of ending after web_session_seconds unused.
  • A user's storage is measured in the background, at most every fifteen
    minutes, instead of on every status call, so landing on the page no
    longer waits on a large home directory.
  • A session container that fails to start is removed instead of left
    behind.
  • New settings: SEALSKIN_DASHBOARDS_PATH, SEALSKIN_WIDGET_SECRETS_PATH,
    SEALSKIN_DASHBOARD_LINK_SCHEMES, SEALSKIN_WEATHER_URL,
    SEALSKIN_STOCKS_URL, SEALSKIN_GEOCODING_URL, SEALSKIN_BAKERY_PATH,
    SEALSKIN_BAKERY_BUILD_IDLE_SECONDS, SEALSKIN_BROWSER_POLICIES_PATH,
    SEALSKIN_BROWSER_POLICY_FILES_PATH, SEALSKIN_NODE_GPUS, and
    SEALSKIN_NODE_GPU_PREFER.
  • The shared store gains dashboards/, bakery/recipes.yml with the files
    recipes copy under bakery/files/, browser_policies.yml, the pictures of
    each brand, and the icons uploaded for applications under app_icons/.
    Widget secrets, baked images, and policy files stay with each node.
  • Editing an installed application keeps its uploaded icon and the store it
    came from, and an application's uploaded icon is removed with it.
  • In the template editor, Dashboard Layout (SELKIES_UI_LAYOUT: the
    sidebar, the Wish toolbar, or the Edge button) replaces Dashboard
    Style
    (DASHBOARD). Appearance gains the desktop's color scheme
    (SELKIES_COLOR_SCHEME), lifecycle the applications' logs
    (SELKIES_APP_LOGS), and integrations Pelorus (PELORUS).
  • Congestion control moves to the performance card, since it adapts the
    video rate over WebSockets as well as WebRTC, and is on by default, as in
    Selkies. A template could not turn it off before.
  • The web client a Selkies 2.3.0 base image keeps in web/ is exported and
    served like the dashboards of older images.
  • The VPN image is built without a layer cache, so every build takes
    Alpine's current packages.
  • Dependency updates for the server, the documentation site, and the
    workflows.

Client

  • The admin dashboard gains the Bakery and Browser Policies tabs, the
    brand picker in Branding, and an application's browser policy and icon
    in its install dialog.
  • The web app loads in fewer round trips, and only UI files whose path
    carries the build's content hash are cached for a year.
  • In collaboration rooms, a collaborator's stream and desktop DPI follow
    their screen's pixel density, a Safari camera reaches the encoder, and the
    audio session is claimed before a room asks for the microphone.
  • The App Store tab shows a store's list from the page's own copy for a day;
    the refresh button fetches the store again.
  • The mobile app's Capacitor packages and build dependencies are updated to
    their patched releases.
  • Translations for the dashboards, brands, the Bakery and its guided steps,
    the browser policy editor, application icons, the idle limit, and the new
    template variables in all seventeen other languages.

Security

An audit of every route and of what each kind of account can reach found no
route that answered without the sign-in it requires. What it found beyond
that is fixed here.

  • Collaboration rooms. A participant's microphone, camera, and cursor
    messages carry their alias and nothing else. They carried the sender's room
    token, which let a read-only viewer come back as the controller.
  • User names. A name starting with sealskin_ is refused, whoever names
    the user. The server's own directories under the storage path start with
    it, and a user so named got one of them as a storage directory.
  • Home directories. The autostart script a launch writes, and the shared
    files a cluster syncs, go through a descriptor checked inside the
    directory, so a link a session left there cannot redirect what the server
    writes or reads. A launch or a move takes only a plain home directory
    name, and a listing reports a link as a link.
  • Sessions on the web app's origin. A session's container sets no cookie
    on the origin it is served from. A session whose container serves its own
    page there (a key-file client's session of an image with no web client to
    export) does not open in a browser signed in on the web.
  • VPN profiles. An OpenVPN profile's options are read by the names
    OpenVPN gives them, with quotes and leading dashes removed and setenv opt
    unwrapped, before the ones that run a program are dropped. A block OpenVPN
    does not read, or one that ends oddly, refuses the profile.
  • App stores. A store's YAML sets none of the session's identity
    variables (PUID, PGID, CUSTOM_USER, PASSWORD, SUBFOLDER, the
    Selkies tokens), nor DOCKER_MODS, S6_*, LD_*, FILE__*, BASH_ENV,
    ENV, PATH, HOME, or IFS.
  • Template editors. A user allowed to edit templates cannot set those
    variables either, nor delete a template that holds one or a session's
    identity, and an administrator's values survive an editor's save.
  • Reverse proxy sign-in. The check of the proxy's headers counts a
    request only when it came through this node's own proxy, so nothing sent
    to the API port can switch header sign-ins off, and a container a room
    swapped away from is trusted no more than the one it shows.
  • Hardening switches. Harden Container and Harden Window Manager
    force the Selkies values their base image presets set, not just the
    presets, since the image applies those only where nothing else did. A
    template or an application's environment that turned on file transfers,
    printing, command messages, or the files and apps panels, or on Selkies
    2.3.0 the window manager's menus, key binds, close button, or desktop
    switch, kept them for a hardened user.
  • Clusters. A node that joined to run sessions only keeps the roles,
    pool, and approval it was admitted with when it rewrites its own record.
  • Widgets and pictures. A user's widget is not fetched from a NAT64 or
    site-local address, an answer is read uncompressed up to its limit, and a
    redirect to another host carries none of the first request's headers. An
    icon or a screenshot is decoded up to a pixel limit, and a screenshot is
    read up to a byte limit.
  • Public endpoints. The server publishes no OpenAPI description and no
    explorer: /openapi.json, /docs, and /redoc answer 404. A shared file
    is sent as a download that a browser neither runs nor sniffs.
  • A held user's status lists no VPN profile, a room token and a malformed
    netrc file stay out of the log, and a key-file token whose subject is not
    text is refused.

Upgrading from 0.4

Nothing on disk needs changing, and nothing new is on until an administrator
sets it up: with no dashboard defined the home page is the built-in one, and
session_idle_minutes is -1, no limit. What changes:

  • A user's favorites become tiles on their page, and the background they set
    with the brush is under Appearance in edit mode.
  • Docker session containers are named sealskin-<session>-<suffix>.
    Anything that picked them out by Docker's random names, or by another
    pattern, needs the new one.
  • A server that shares its name with another running container no longer
    starts. Stop that container, or give the server a name of its own through
    its container's name or SEALSKIN_NODE_NAME.
  • Browser policy files are written under /storage/sealskin_browser_policies
    (SEALSKIN_BROWSER_POLICY_FILES_PATH), beside the home directories, and
    on Kubernetes on the storage claim. A policy holds only where sessions run
    without root: turn on desktop hardening for the users it is meant to hold.
  • A policy with a Firefox part replaces an image's own policies.json, so
    LibreWolf's and Mullvad Browser's shipped defaults do not apply under it.
  • The Bakery builds with the node's Docker daemon, using Docker's classic
    builder, and gives a build no registry credential. On Kubernetes the tab
    says so and recipes cannot be saved.
  • The weather and stocks widgets read Open-Meteo and Yahoo Finance once one
    is placed. A deployment without internet access points
    SEALSKIN_WEATHER_URL, SEALSKIN_GEOCODING_URL, and SEALSKIN_STOCKS_URL
    at hosts of its own, or leaves those widgets out.
  • In a cluster each node needs the widget secrets its widgets name, as files
    under SEALSKIN_WIDGET_SECRETS_PATH or as SEALSKIN_WIDGET_SECRET_<NAME>
    variables; the store holds only their names.
  • An address handed to a launch that is not http, https, ftp, or
    magnet is refused, as is an application icon that is not a picture.
  • Uploaded application icons are read from the shared store. A cluster on a
    bucket needs a meta-app's icon uploaded again, since the copy kept on the
    node it was uploaded to is not in the bucket.
  • The idle limit relies on the session's Selkies reporting its connections;
    a session of an image that does not is never stopped by it.
  • A user name starting with sealskin_ no longer signs in or is created.
    Rename such a user at the identity provider or the proxy.
  • An app store that set a session's identity variables or DOCKER_MODS in
    an application's environment has them ignored, with a line in the log. Set
    them in a template, as an administrator.
  • A user allowed to edit templates can no longer save PATH, HOME,
    LD_*, S6_*, FILE__*, BASH_ENV, ENV, or IFS; an administrator
    saves those.
  • Import an OpenVPN profile again if it was refused: one with a <block>
    OpenVPN does not read, or an option written with an escape, is not
    accepted. Profiles imported before stay as they are.
  • A node of a file store's cluster that ran sessions only and is to become a
    frontend is removed in the dashboard and joined again with a new code;
    SEALSKIN_NODE_ROLES alone no longer changes it.
  • /openapi.json and /docs are gone from both ports.
  • A template's DASHBOARD set to selkies-dashboard-wish becomes
    SELKIES_UI_LAYOUT: wish,default,edge when it is loaded, and any other
    DASHBOARD is dropped, since the base images have one dashboard. An older
    image with several still takes DASHBOARD from an application's own
    environment.
  • h264enc-striped, which Selkies 2.3.0 no longer has, becomes h264enc in
    a template's encoder list.
  • Whatever their template sets, a user under Harden Container runs
    without file transfers, printing, command messages, and the files and apps
    panels, and one under Harden Window Manager without the window
    manager's menus, key binds, and close button; neither can switch between
    the desktop and the application alone.
  • A root key sign-in on the web now lasts until it is signed out (its cookie
    is kept for 400 days). Sign out of shared browsers, or turn
    root_sign_in off on nodes where that is not wanted.
  • Under Podman, NVIDIA sessions need a CDI spec on the host, which
    nvidia-ctk cdi generate writes; a launch without one fails with an error
    naming the command.

Documentation

  • A Dashboards page; a Podman page, SteamOS included; and sections for the
    Bakery, browser policies, and a brand per host name or group under
    Administration. The API, object store, Kubernetes, cluster, and settings
    pages cover the new routes, objects, and settings.
  • The threat model covers the Bakery, browser policies, dashboards and their
    widgets, the widgets' fetches and secrets, the brand a request gets, the
    address a user hands a session, and the root key's web sign-in, with what
    each may and may not reach.

Build

  • Pull requests run Mobile Unsigned Validation: an Android debug build
    and an iOS simulator build without signing material, and Capacitor's own
    navigation regression tests.