Skip to content

Releases

v1.97.2

Choose a tag to compare

@Irdanwen Irdanwen released this 07 Nov 09:42

Sub Rosa v1.97.2

Correctif de sécurité de la 1.97.1 pour l'assistant sur Mac. / Security fix for 1.97.1, for the Mac assistant.

Français

Ce qui est corrigé

  • Avant la 1.97.0, une session en bac à sable détournée pouvait déposer un
    fichier (un module, ou du code Python déjà compilé dans __pycache__)
    dans le dossier de l'extension de garde de Sub Rosa, à l'intérieur du
    dossier partagé avec les routines et les messageries. La 1.97.0 a mis de
    côté ce qu'une session avait pu planter dans ce dossier partagé, mais
    épargnait ce dossier d'extension, que seul le côté qui démarrait
    réécrivait. Quand le côté en bac à sable démarrait le premier, un tel
    fichier restait en place, et il était chargé hors du bac à sable à chaque
    démarrage des routines et des messageries, en 1.97.0 et en 1.97.1.
  • Désormais, quel que soit le côté qui démarre, et à chaque démarrage des
    routines et des messageries, ce dossier ne contient plus que les fichiers
    de Sub Rosa : tout le reste est retiré, __pycache__ compris.
  • Si ce nettoyage retire quelque chose alors que les routines et les
    messageries tournent déjà, elles redémarrent une fois, pour ne plus garder
    ce qu'elles avaient chargé. Un dossier propre ne provoque aucun
    redémarrage.

Ce qu'il faut savoir

  • Aucune exploitation connue. Le défaut demandait qu'une session en bac à
    sable ait été détournée avant la mise à jour vers la 1.97.0 ; ses effets,
    eux, auraient été sérieux, car le fichier planté s'exécutait hors du bac à
    sable.
  • Rien à refaire de votre côté. Si quelque chose a été retiré, le journal
    de Sub Rosa le note.

Ce qui reste ouvert

Inchangé depuis la 1.97.1 (voir les notes de la 1.97.1).

English

Fixed

  • Before 1.97.0, a hijacked sandboxed session could drop a file (a module,
    or Python code already compiled in __pycache__) into the folder of Sub
    Rosa's guard plugin, inside the folder shared with routines and messaging.
    1.97.0 set aside what a session could have planted in that shared folder,
    but spared this plugin folder, which only the side that started rewrote.
    When the sandboxed side started first, such a file stayed in place, and it
    was loaded outside the sandbox every time routines and messaging started,
    in 1.97.0 and 1.97.1.
  • Now, whichever side starts, and every time routines and messaging start,
    this folder holds only Sub Rosa's files: everything else is removed,
    __pycache__ included.
  • If this cleaning removes something while routines and messaging are
    already running, they restart once, so they no longer keep what they had
    loaded. A clean folder causes no restart.

Good to know

  • No known exploitation. The flaw required a sandboxed session to have been
    hijacked before the update to 1.97.0; its effects would have been serious,
    since the planted file ran outside the sandbox.
  • Nothing to redo on your side. If something was removed, Sub Rosa's log
    says so.

Still open

Unchanged since 1.97.1 (see the 1.97.1 notes).

Changes

  • chore(website): publish the 1.97.1 downloads (#485)
  • fix(jail): the shared home's plugin is the app's, whichever home starts (ADR-0140, 1.97.2) (#486)

v1.97.1

Choose a tag to compare

@Irdanwen Irdanwen released this 05 Nov 08:22

Sub Rosa v1.97.1

Correctif de sécurité de la 1.97.0 pour l'assistant sur Mac, en session « bac à sable ». / Security fix for 1.97.0, for the Mac assistant in a sandboxed session.

Français

Ce qui est corrigé

  • Une session en bac à sable pouvait écrire des fichiers que d'autres parties
    de Sub Rosa lisent et exécutent ensuite hors du bac à sable : réglages,
    routines, extensions, scripts, connexions. Elle a désormais son propre
    dossier, séparé de celui du côté sans restriction, des routines et des
    messageries, et ne peut plus rien y écrire de ce qui s'exécute ailleurs.
  • Elle ne peut plus lancer ni piloter d'autres programmes : ouvrir une
    application ou un lien, AppleScript, Raccourcis, éléments d'ouverture,
    menu Services, frappes ou clics simulés, captures d'écran, presse-papiers.
    Elle n'hérite plus des autorisations de Sub Rosa (Accessibilité,
    enregistrement de l'écran).
  • Elle ne peut plus joindre l'agent ssh ou gpg, Docker et les autres moteurs
    de conteneurs, un multiplexeur de terminal, ni un service local de cette
    machine autre que ceux dont elle a besoin, ni envoyer de datagramme
    (UDP). Elle n'écrit plus dans les dossiers temporaires partagés.
  • Un dossier que macOS ou vos programmes lisent à l'ouverture de session
    (~/Library/LaunchAgents, Application Support, Preferences et
    voisins) ne peut plus être choisi comme dossier de travail.
  • Sub Rosa n'exécute plus git sur le dossier de travail d'une session sans
    protection : un réglage planté dans .git/config par une session
    (présent depuis la 1.97.0) ne s'exécute plus quand la revue de code ou le
    conseil lisent ce dossier. Un dossier dont la configuration git définit un
    programme (un filtre, une commande de comparaison), ou dont git ne peut
    pas lire la configuration, n'est plus lu par git.
    Ailleurs, git tourne dans un bac à sable qui ne lit le contenu que du
    dépôt, ne joint aucun réseau et s'arrête au bout de 30 secondes.
  • Le conseil et la revue de code n'envoient jamais le contenu d'un fichier
    sensible (.env et ses variantes, une clé, .npmrc, .netrc, .pgpass,
    des identifiants...) : ils le nomment, sans son contenu, que git le suive
    ou non. Ces fichiers sont reconnus par leur nom : une copie sous un nom
    anodin ne l'est pas.
  • Le conseil, la revue de code et le panneau Fichiers ne suivent plus un
    lien posé par une session dans son dossier : un lien vers vos clés ssh,
    par exemple, n'est plus lu ni envoyé aux modèles du conseil. Ce défaut
    existait déjà dans la 1.97.0.
  • À l'arrêt de l'assistant, les processus qu'une session en bac à sable a
    laissés derrière elle sont arrêtés, même détachés.
  • Chaque conversation est lue dans le dossier de son mode, jamais dans
    l'autre, et une tâche n'est rattachée qu'à une conversation de son propre
    mode : une session en bac à sable ne peut plus imiter la conversation
    d'une tâche lancée sans restriction.
  • Une connexion à un serveur MCP lancée depuis le bac à sable n'ouvre plus
    seule l'adresse d'un serveur local ou privé : elle vous la montre. Le bac
    à sable ne peut plus écouter que sur son propre port.

Ce qu'il faut refaire

Au premier lancement, un avis dit ce qui a été mis de côté et ce qu'il faut
refaire. Selon votre installation :

  • associer de nouveau vos messageries ;
  • réinstaller les serveurs MCP du catalogue ;
  • vous reconnecter aux connecteurs qui demandaient une connexion, depuis une
    session en bac à sable (les connexions ne sont plus partagées entre les
    deux côtés) ;
  • vos tableaux de tâches, routines à script, extensions et scripts ont été
    mis de côté, jamais supprimés : vous pouvez les remettre un par un, après
    confirmation, depuis l'avis ;
  • l'ancien dossier de l'assistant est l'« Unrestricted workspace » du
    panneau Fichiers.

En session en bac à sable, ces actions ne marchent plus : ouvrir un lien ou
une application depuis un outil (l'assistant vous donne le lien), le
presse-papiers, les notifications, les captures, écrire dans /tmp par son
nom, joindre une base de données locale ou un serveur local lancé par la
session, l'agent ssh. Pour en avoir besoin, démarrez une session sans
restriction.

La revue de code et le conseil ne lancent plus git sur un dépôt qui définit
un programme dans sa propre configuration git (un filtre comme celui de
git-lfs installé dans le dépôt, une commande de comparaison) : la revue
l'affiche au lieu de démarrer, et le verdict du conseil le signale (il lit
alors les fichiers modifiés depuis le début du travail). Git ne lit plus
votre configuration globale, sauf votre fichier d'exclusions, relu comme
une simple liste de motifs : ce que vous ignorez partout reste ignoré. Un
dépôt git-lfs ordinaire est lu sans son filtre : ses fichiers dont la date
a changé apparaissent modifiés.

Ce qui reste ouvert

  • Windows n'a pas de bac à sable.
  • Le dossier de travail reste écrit par la session : ce que vos propres
    outils y exécutent ensuite (votre git, direnv, un script de build) est
    hors de ce correctif.
  • Les adresses d'un VPN ou de Tailscale sur ce Mac n'ont pas été mesurées
    contre la règle de la boucle locale : la règle réseau du bac à sable ne
    sait nommer que « cette machine » ou « tout », jamais une adresse.
  • Un programme qui parlerait lui-même le protocole privé de launchd pourrait
    arrêter, relancer ou désactiver un de vos agents ou Sub Rosa (une gêne,
    pas un programme lancé hors du bac à sable).
  • Un processus qui se détache à chaque fork plus vite qu'un balayage peut
    survivre à l'arrêt, toujours dans le bac à sable, sans aucune autorisation
    de Sub Rosa.

English

Fixed

  • A sandboxed session could write files that other parts of Sub Rosa read
    and then run outside the sandbox: settings, routines, plugins, scripts,
    sign-ins. It now has a folder of its own, apart from the unrestricted
    side, routines and messaging, and can write nothing there that runs
    elsewhere.
  • It can no longer start or drive other programs: opening an app or a link,
    AppleScript, Shortcuts, login items, the Services menu, simulated keys or
    clicks, screenshots, the clipboard. It no longer inherits Sub Rosa's
    permissions (Accessibility, screen recording).
  • It can no longer reach the ssh or gpg agent, Docker and other container
    engines, a terminal multiplexer, or a service of this Mac other than the
    ones it needs, or send a datagram (UDP). It no longer writes the shared
    temporary folders.
  • A folder macOS or your programs read at login (~/Library/LaunchAgents,
    Application Support, Preferences and the like) can no longer be
    picked as a working folder.
  • Sub Rosa no longer runs git on a session's working folder unprotected: a
    setting a session planted in .git/config (present since 1.97.0) no
    longer runs when the code review or the council reads that folder. A
    folder whose git configuration defines a program (a filter, a diff
    command), or whose configuration git cannot read, is not read by git.
    Elsewhere, git runs in a sandbox that reads only the repository's
    contents, reaches no network and stops after 30 seconds.
  • The council and the code review never send a sensitive file's content
    (.env and its variants, a key, .npmrc, .netrc, .pgpass,
    credentials...): they name it, without its content, whether git tracks it
    or not. These files are recognized by their name: a copy under a plain
    name is not.
  • The council, the code review and the Files panel no longer follow a link a
    session put in its folder: a link to your ssh keys, say, is no longer read
    or sent to the council's models. This flaw was already in 1.97.0.
  • When the assistant stops, the processes a sandboxed session left behind
    are stopped, detached ones included.
  • Each conversation is read from the folder of its own mode, never the
    other one, and a task is attached only to a conversation of its own mode:
    a sandboxed session can no longer pose as the conversation of a task
    started without restriction.
  • A sign-in to an MCP server started from the sandbox no longer opens a
    local or private server's address by itself: it shows it to you. The
    sandbox can listen only on its own port.

What to redo

At first launch a notice says what was set aside and what to redo.
Depending on your setup:

  • pair your messaging channels again;
  • install the catalog MCP servers again;
  • sign in again, from a sandboxed session, to the connectors that asked you
    to (sign-ins are no longer shared between the two sides);
  • your task boards, script routines, plugins and scripts were set aside,
    never deleted: you can put them back one by one, after a confirmation,
    from the notice;
  • the assistant's former folder is the "Unrestricted workspace" of the
    Files panel.

In a sandboxed session these no longer work: opening a link or an app from
a tool (the assistant gives you the link), the clipboard, notifications,
screenshots, writing /tmp by name, reaching a local database or a local
server the session started, the ssh agent. When you need them, start an
unrestricted session.

The code review and the council no longer run git on a repository that
defines a program in its own git configuration (a filter such as git-lfs
installed in the repository, a diff command): the review shows it instead
of starting, and the council's verdict says so (it then reads the files
changed since the work began). Git no longer reads your global
configuration, except your excludes file, read again as a plain list of
patterns: what you ignore everywhere stays ignored. An ordinary git-lfs
repository is read without its filter: its files whose date changed show
as changed.

Still open

  • Windows has no sandbox.
  • The working folder is still written by the session: what your own tools
    later run from it (your git, direnv, a build script) is outside this
    fix.
  • A VPN's or Tailscale's addresses on this Mac were not measured against the
    loopback rule: the sandbox's network ...
Read more

v1.97.0

Choose a tag to compare

@Irdanwen Irdanwen released this 22 Oct 17:14

Sub Rosa v1.97.0

Changes since v1.96.0.

Changes

  • chore(website): publish the 1.96.0 downloads (#464)
  • fix(studio): stop the phone gallery freezing after a large sync (#397)
  • chore(deps): Bump the npm-minor-and-patch group with 17 updates (#455)
  • fix(studio): let a mix read the sounds it decodes (#466)
  • chore(deps): Bump the cargo-minor-and-patch group in /src-tauri with 10 updates (#456)
  • fix(agent-hud): a clean, draggable, translated sessions HUD on Windows (#465)
  • chore(deps): Bump tokio from 1.53.2 to 1.53.3 in /june-api in the cargo-minor-and-patch group across 1 directory (#457)
  • chore(deps): Bump actions/setup-java from 6.0.1 to 6.1.0 in the actions group (#458)

v1.96.0

Choose a tag to compare

@Irdanwen Irdanwen released this 20 Oct 13:34

Sub Rosa v1.96.0

Changes since v1.95.0.

Changes

  • chore(website): publish the 1.95.0 downloads (#452)
  • fix(studio): never save the empty canvas of a workflow whose steps are not drawn yet (#460)
  • feat(studio): the apps have their own tab on the desktop (#453)
  • fix(workflow): every shipped app judged before a run, and three it caught (#454)
  • feat(studio): import a clip, a track or a picture from the device into an app's field (#459)
  • feat(studio): the phone's Apps screen shows each app as a card with its picture (#461)
  • fix(studio): what the first real runs of the apps showed (#462)

v1.95.0

Choose a tag to compare

@Irdanwen Irdanwen released this 18 Oct 21:44

Sub Rosa v1.95.0

Changes since v1.94.1.

Changes

  • chore(website): publish the 1.94.1 downloads (#440)
  • feat(workflow): measure the ComfyUI importer on the official templates (#441)
  • fix(studio): let a video-to-video render take its length from the clip (#446)
  • refactor(workflow): one catalog list for the shipped templates, sorted by kind (#442)
  • feat(workflow): nine templates for products and brands (#443)
  • feat(workflow): eight templates for characters, shots and films (#444)
  • feat(workflow): three templates for sound (#445)
  • feat(workflow): a video step takes a clip to change and a line to say (#447)
  • docs: close the template catalog work in the parity matrix and notes (#448)
  • perf(workflow): build the shipped templates once per mount (#450)
  • test: give findBy and waitFor four seconds on slow runners (#451)

v1.94.1

Choose a tag to compare

@Irdanwen Irdanwen released this 17 Oct 22:26

Sub Rosa v1.94.1

Changes since v1.94.0.

Changes

  • chore(website): publish the 1.94.0 downloads (#437)
  • fix(mobile): a run keeps going when the person leaves the app's screen (#438)

v1.94.0

Choose a tag to compare

@Irdanwen Irdanwen released this 17 Oct 20:06

Sub Rosa v1.94.0

Changes since v1.93.0.

Changes

  • chore(website): publish the 1.93.0 downloads (#395)
  • feat(website): new models, a catalog that answers "which one?", and a price table in dollars (#396)
  • refactor(studio): split the workflow canvas and engine into modules (#398)
  • fix(studio): guard every paid workflow step and fix the canvas's leftovers (#399)
  • feat(studio): the workflow canvas speaks all six languages (#400)
  • feat(studio): workflow format 2, node migrations, read-only newer workflows (#401)
  • feat(studio): re-queue rate-limited renders, gate submissions, hear jobs settle (#402)
  • feat(studio): reuse an unchanged workflow step instead of buying it again (#403)
  • feat(studio): show a workflow's last results on reopen, and its run history (#404)
  • feat(studio): start workflow steps when ready, run one step, show problems on it (#405)
  • feat(studio): set a workflow step aside without unwiring it (#406)
  • feat(studio): live prices on every workflow step, and a spend ceiling (#407)
  • feat(studio): undo, clipboard and shortcuts on the workflow canvas (#408)
  • feat(studio): find a step by typing, and drop a connection to add what fits (#409)
  • fix(studio): give canvas runs the step cache, scheduling and rate-limit budget (#410)
  • feat(studio): a bar over selected steps, wires coloured by what they carry (#411)
  • feat(studio): arrange a workflow, compact steps from afar, collapse, pin, tint, relay (#412)
  • feat(studio): files a workflow makes lead back to the workflow (#413)
  • feat(studio): import a ComfyUI workflow from a picture or video it made (#414)
  • feat(studio): frames and notes on the workflow canvas (#415)
  • feat(studio): save a copy with its workflow (#416)
  • feat(studio): blocks, several steps that run as one (#417)
  • feat(studio): open a block to change it (#418)
  • feat(studio): keep blocks in the library (#419)
  • feat(studio): upscale, cut out, mix sounds and compare as workflow steps (#420)
  • feat(studio): retouch a zone and draw a contact sheet as workflow steps (#421)
  • feat(studio): eight blocks shipped with the app (#422)
  • feat(studio): text template, preview, switch, and settings taken from a connection (#423)
  • feat(studio): lists, a step run once per item (#424)
  • feat(studio): keep versions of a workflow (#425)
  • fix(studio): show a list's results on its steps, and keep Run on the toolbar's line (#426)
  • feat(studio): workflows and library blocks travel with the account (#427)
  • feat(studio): open workflows as tabs, with each run going on in its own (#428)
  • feat(studio): fifteen templates, sorted, priced and pinned to today's catalog (#429)
  • feat(studio): import ComfyUI subgraphs as blocks, reroutes as relays, partners from a table (#430)
  • feat(studio): a workflow can be shown as an app (#431)
  • feat(mobile): use workflows made apps from the phone's Studio (#432)
  • feat(studio): the assistant proposes workflows, and never runs them (#433)
  • docs(studio): the ComfyUI parity matrix, kept by a test (#434)
  • fix(deps): read and write zips with zip 9, past three new advisories (#436)

v1.93.0

Choose a tag to compare

@Irdanwen Irdanwen released this 16 Oct 09:55

Sub Rosa v1.93.0

Changes since v1.92.0.

Changes

  • chore(website): publish the 1.92.0 downloads (#370)
  • fix(cloud): assertion route answers 404 before reading the body; one partner contract again (#380)
  • fix(account): a device key is never lost, and leaving the account reaches Carpe Diem (#379)
  • chore(ci): artifacts are kept only as long as they serve (#381)
  • feat(website): the account page shows the balance Carpe Diem reports now (#383)
  • feat(account): Carpe Diem in the account settings: balance, keys per device, low-balance alert (#384)
  • chore(deps): bump serde_json from 1.0.151 to 1.0.152 in /june-api in the cargo-minor-and-patch group (#378)
  • chore(deps): bump windows from 0.61.3 to 0.62.2 in /src-tauri (#376)
  • chore(deps-dev): bump @vitejs/plugin-react from 5.2.0 to 6.1.2 (#372)
  • fix(deps): rustls 0.23.46 everywhere, ammonia 4.2.3 in the account service (#388)
  • Recordings leave a chosen age after transcription, everywhere (ADR-0112) (#368)
  • chore(deps): p256 0.14 and hpke 0.14; coreaudio-rs moves with cpal (#387)
  • chore(deps): Tauri plugins and npm minor updates together, notification 2.6 on both sides (#386)
  • Choose what a note records, and capture the computer's sound on Windows (#385)
  • chore(deps): bump sha2 from 0.11.0 to 0.11.1 in /june-api in the cargo-minor-and-patch group (#389)
  • chore(deps-dev): bump @testing-library/user-event from 14.6.7 to 14.6.8 in the npm-minor-and-patch group across 1 directory (#393)
  • chore(deps): bump diffy from 0.4.2 to 0.5.2 in /src-tauri (#392)
  • chore(deps): bump the cargo-minor-and-patch group across 1 directory with 4 updates (#394)

v1.92.0

Choose a tag to compare

@Irdanwen Irdanwen released this 13 Oct 15:14

Sub Rosa v1.92.0

Changes since v1.91.0.

Changes

  • chore(website): publish the 1.91.0 downloads (#359)
  • chore(design): a layer scale, a ratchet on raw colours and layers, the dead film tab removed (#351)
  • feat(studio): the desktop Studio on the stage, with five tabs (#352)
  • feat(shell): six places in the sidebar, a New menu, the chat's hero everywhere (#353)
  • feat(chat): the hero composer keeps its toolbar for every message (#354)
  • feat(settings): one list of settings, four groups, Advanced folded, a filter (#355)
  • feat(notes): one word for notes, previews a person reads, exports in one menu (#357)
  • feat(states): one way to say nothing, failure and waiting (#360)
  • feat(polish): reduced transparency, more contrast, a popover entrance, a shortcuts sheet (#361)
  • feat(website): one button that asks, a menu on phones, share cards and a sitemap (#358)
  • feat(website): a legal notice naming the publisher, and an operator on the privacy page (#362)
  • feat(website): a home page that says what the app is, shows it, and prices it (#363)
  • feat(website): page templates: trust pages as one set, aligned downloads, guides with real captures (#364)
  • feat(website): the account says where it stands before asking for the vault (#365)
  • perf(website): the guides leave the entry script, the German title fits, a sweep under the production policy (#366)
  • fix(deps): quinn-proto 0.11.19 for three new advisories (#367)

v1.91.0

Choose a tag to compare

@Irdanwen Irdanwen released this 12 Oct 15:30

Sub Rosa v1.91.0

Changes since v1.90.0.

Changes

  • chore(website): publish the 1.90.0 downloads (#350)
  • The account keeps inside its quota, and text never waits for files (ADR-0110) (#356)