Dependencies are listed in the Dioxus documentation.
You can compile a production version using the following command:
cargo build --release
For a debug version, remove the --release flag.
When developing, be sure to:
- format the code using
cargo fmt - fix all warnings detected by
cargo clippy - detect outdated dependencies using
cargo outdated(requires cargo-outdated) - check the dependencies using
cargo deny check(requires cargo-deny)
You are free tu use, copy, modify, and/or distribute this software under the terms of the European Union Public License (EUPL) v1.2.
A copy of this license is available in the LICENSE directory.
The configuration should always be modified through the software's graphical
interface. For use cases where this option is not available (for example in
automatic deployments), it is possible to directly edit the configuration file.
This file is named config.toml and is written in the TOML format. Its
location varies depending on the operating system.
| Operating System | Value | Example |
|---|---|---|
| Microsoft Windows | {FOLDERID_RoamingAppData}\CNIL\loutre |
C:\Users\john_doe\AppData\Roaming\CNIL\loutre |
| GNU/Linux | ${XDG_CONFIG_HOME}/cnil/loutre |
/home/john_doe/.config/cnil/loutre |
| macOS | ${HOME}/Library/Application Support/cnil/loutre |
/home/john_doe/Library/Application Support/cnil/loutre |
As for 2025, all supported hashing functions uses a robust public algorithm without known vulnerability. All of them can therefore be safely used.
Those functions mostly varies in terms of fingerprint size, execution speed and popularity.
The most popular function is SHA-256. Aside from its large popularity, it has a small fingerprint size and almost every recent x86 CPU supports the Intel SHA extensions, which means it will be hardware-accelerated and therefore very quick to process. Those characteristics makes it an excellent choice.
The intrinsically fastest function is Blake-3. It is very recent (2020) and therefore rarely used, but its modern conception makes it so fast that, without hardware acceleration, its performances may be similar to a hardware-accelerated SHA-256. Its fingerprint size is equal to the SHA-256 one. This is a very good choice when used with CPU that does not support the Intel SHA extensions.
All the other functions are neither fastest nor more popular than SHA-256 and Blake-3. In most cases, the additional security brought by the longest fingerprint of some functions is not considered useful. Those additional functions are supported for two main reasons:
- A better integration in processes that already uses those functions.
- The possibility to quickly react to an eventual vulnerability discovered in the most popular functions.
After calculating the fingerprint of each file in the specified directory, Loutre stores those hashes in a file. You may chose the format of this file.
Important note: the Cksum format has no official name. We named it this way because of the cksum tool. There is two very different variants of this format: one is used by default on several BSD systems, the other one is used by default in systems using GNU coreutils (mostly GNU/Linux distributions). All known recent versions of those operating systems include tools capable of reading and writing both variants.
This is the default choice. This variant is recommended since it explicitly stores the hashing function that has been used to generate the fingerprints.
This format is compatible with the output of the following tools:
- On GNU/Linux and other systems using GNU coreutils: cksum (using one of the following algorithms: sha256, sha384, sha512, blake2b)
- On GNU/Linux and other systems using GNU coreutils:
sha256sum, sha384sum,
sha512sum, b2sum (using the
--tagoption) - On FreeBSD: sha256, sha384, sha512
- On OpenBSD: cksum (using the following algorithms: sha256, sha384, sha512)
This variant does not stores the hashing function that has been used to generate the fingerprints. The content file's name should therefore indicate it in its name.
This format is compatible with the output of the following tools:
- On GNU/Linux and other systems using GNU coreutils: cksum (using
the
--untaggedoption and one of the following algorithms: sha256, sha384, sha512, blake2b) - On GNU/Linux and other systems using GNU coreutils: sha256sum, sha384sum, sha512sum, b2sum
- On FreeBSD: sha256sum, sha384sum, sha512sum
- On OpenBSD: cksum (using the
-roption and one of the following algorithms: sha256, sha384, sha512)
This format has been created by the French data protection authority (Commission nationale de l'informatique et des libertés, CNIL). It is not standard and no other use of this format is known. Its usage is discouraged unless you work at the CNIL.
The favicon is generated from the SVG template using the following method:
- a set of PNG icons are generated using Inkscape
- those images are converted into a single favicon using ImageMagick
- temporary PNG images are deleted
for size in "256" "96" "80" "72" "64" "48" "40" "36" "32" "30" "24" "20" "16"; do inkscape -w "$size" -h "$size" "assets/favicon-template.svg" -o "assets/AppList.targetsize-${size}.png"; done
magick "assets/AppList.targetsize-*.png" -colors 256 "assets/favicon.ico"
rm assets/AppList.targetsize-*.png
Read more about application icons on the Microsoft Windows documentation and Wikipedia.