Cahut 1.2.0

Cahut 1.2.0 lets people delete their own account from the console, and starts the workers of the data of Windows on AlmaLinux 10.2.

Upgrading from 1.1.1

1.2.0 is a minor release: under the default CAHUT_UPDATES=patch, the daily timer does not install it. Install it from the console of the server, under Updates, or:

sudo /usr/local/bin/cahut update

• One migration of the database of each Cahut, 0037: the setting that lets its people delete their own account. As every update does, it takes a snapshot of the databases first, and rolls back if the health check fails.
• People may delete their own account in every Cahut, as soon as it is updated. In a Cahut where they must not, for instance where an organization keeps the work of the people who leave, or where another app manages the accounts, turn it off right after the update, from the People page of its console, or with:

sudo -u cahut /usr/local/bin/cahut settings account-deletion --off --domain <domain>

• No operation or MCP tool goes away, and no MCP tool comes: the new operations serve people, in the console.

Added

• People delete their own account (#256, ADR 59). The Account page of the console ends with a section that says what would go, what would stay and what stops the deletion, then asks for the password and the handle in full.
  • What goes: what goes when an administrator deletes the person, that is their account, sessions, tokens, connected AIs, Knocks, personal Room, and the team Rooms where they are the only member, with their Windows; and the Windows they kept for themselves in the Rooms that stay.
  • What stays: the team Rooms that have another owner, and what the person published there, without an author. The Logbook keeps its entries, and the handle becomes free.
  • What stops it: a team Room they own alone and that has other members, until they give it another owner or delete it; being the last administrator of the Cahut; and the setting of its administrators.
  • When the Cahut sends e-mail, a message tells the person that their account is deleted.
• The setting of the administrators (#256): a switch on the People page of the console, set_account_deletion in the API, and cahut settings account-deletion --on|--off on the command line. get_cahut shows it.
• cahut doctor starts a worker of the data of Windows, in a folder of its own, and has it check a migration (#274). It fails when the worker does not answer within 10 seconds, where it used to say only which version of Landlock confines the workers.

Fixed

• The data of Windows on AlmaLinux 10.2 (#272, #274). On Linux 6.12 with Landlock 6, as AlmaLinux 10.2 ships it, each worker that runs the SQL of a Window waited forever as it confined itself, and no Window with data could be published: the AI got declaration.data: the statement ran out of time. The worker now adds the signal scope of Landlock only on kernels that report its fix, erratum 2 of Landlock, from Linux 6.15. Elsewhere it stays confined to the folder of its database, without network, and may signal the processes of the cahut user, as under Landlock 5. Thanks to @dhippo for the report.