* sd-pdf * Process PDF blocking render inside a spawn_blocking - Load a single global Pdfium instance * Migrate pdf thumb logic to sd-images - Replace block_in_place with spawn_blocking - Only load LibHeif once - Allow thumbnailer (both indexed and non-indexed locations) to process documents - Disable loading pdf viewer in Inspection in favour of loading it's thumbnail * Try to load pdfium lib from absolute path * Revert removed import due to rebase * Small nitpick and some warnings --------- Co-authored-by: Ericson Fogo Soares <ericson.ds999@gmail.com> |
||
---|---|---|
.. | ||
assets | ||
benches | ||
examples | ||
src | ||
Cargo.toml | ||
README.md |
Crypto
This crate contains Spacedrive's cryptographic modules.
This includes things such as:
- The key manager
- Encryption and decryption
- Encrypted file header formats (with extremely fast serialization and deserialization)
- Key hashing and derivation
- Keyring interfaces to access native OS keystores
It has support for the following cryptographic functions:
Argon2id
Balloon
hashingBLAKE3
key derivationXChaCha20-Poly1305
AES-256-GCM
It aims to be (relatively) lightweight, easy to maintain and platform-agnostic where possible. It does contain some platform-specific code, although it's only built if the target matches.
Features
A list of all features can be found below (NOTE: none of these features are enabled by default)
serde
- provides integration with theserde
andserde_json
crates. this also enables header metadatarspc
- provides integration with therspc
cratekeymanager
- provides an interface for handling the encryption, decryption, storage and derivation of passwords/keys. this enables theos-keyrings
featureos-keyrings
- provides a unified interface for interacting with OS-keyrings (currently only supports MacOS/iOS and Gnome/KDE (viagnome-keyring
andkwallet
respectively))
Security Notice
This crate has NOT received any security audit - however, a couple of our upstream libraries (provided by RustCrypto) have.
You may find them below:
- AES-GCM and XChaCha20-Poly1305 audit by NCC group (link)
Breaking changes are very likely! Use at your own risk - no stability or security is guaranteed.
Security Policy
Please refer to the security policy for details and information on how to responsibly report a security vulnerability or issue.