What's new in sett 5.7.0? 🚀

We’re excited to announce the release of sett version 5.7.0, packed with bug fixes and new features to enhance your experience.

Changelogs 📜: Detailed changelogs are available for both sett-guiand sett-cli:

• sett-gui/CHANGELOG.md
• sett-cli/CHANGELOG.md

Download 📥: The latest version can be downloaded from the download page

Linux Support 🐧

sett-gui now supports the latest Linux distributions like Ubuntu 24. Older distributions such as Ubuntu 20 and RockyLinux 8 are no longer natively supported but can still use sett-gui through the new Flatpak distribution format.

For detailed information about this change please see a previous announcement post.

sett-cli is unaffected, it can still be natively installed on all Linux distributions.

New distribution formats 📦

sett-gui is now available in Flatpak and RPM formats, enhancing installation and support for more Linux distributions.

Extended duration for S3 transfers ⏱️

Previously, S3 data transfers were constrained by a 24-hour duration limit, which was tied to the lifespan of a single authentication token.

With the latest release, this limitation has been eliminated. Authentication tokens are now automatically refreshed as needed, enabling transfers to continue beyond the previous 24-hour restriction. Additionally, this enhancement improves security by facilitating the use of short-lived tokens.

CLI

Personal Access Tokens 🎫

Support for Personal Access Tokens has been added in commands like encrypt s3-portal, decrypt s3-portal, and transfer s3-portal for automated data transfer solutions.

For more information see the Personal Access Token announcement on Portal.

Help 🆘

Example commands are now shown directly in the command line with the --help flag. For example:

sett encrypt s3 --help
Encrypt and send data directly to an S3 bucket

Usage: sett encrypt s3 [OPTIONS] --bucket <BUCKET> <FILE>...

...

Examples:

  Create and upload a data package to the specified S3 bucket from the contents of the `~/data` directory. S3 connection details and credentials are loaded from a local credentials file using the 'default' profile
  $ sett encrypt s3 --signer alice@example.org --recipient bob@example.org --bucket foo ~/data

  Create and upload a data package for two different recipients to the specified S3 bucket from the contents of the `~/data` directory. S3 connection details and credentials are loaded from a local credentials file using the 'local' profile
  $ sett encrypt s3 --signer alice@example.org --recipient bob@example.org --recipient chuck@example.org --bucket foo --profile local ~/data

  Create and upload a data package to the specified S3 bucket from the contents of the `~/data` directory.
  $ sett encrypt s3 --signer alice@example.org --recipient bob@example.org --bucket foo --endpoint http://localhost:9000 --access-key key --secret-key secret ~/data

Export keys in TUI 🔑

You can now export both private and public keys directly in the TUI. Simply select a key from the “Keys” tab and press Enter to access the key actions menu.

Stay tuned for more key actions in upcoming releases, as we continue to align TUI features with those available in the CLI and GUI.

Need Help or Have Feedback? ❤️

For questions or feedback, contact the BioMedIT Central Team at biomedit@sib.swiss.

The BioMedIT Central Team

• ←Previous
• Next→