#encryption-key #encryption #encryption-decryption #key-derivation #protobuf

bin+lib tindercrypt

Data encryption with symmetric cryptographic keys or passwords/passphrases, and self-contained encryption metadata

8 releases

0.3.2 Jun 21, 2021
0.3.1 Apr 20, 2021
0.3.0 Jan 10, 2021
0.2.2 Apr 12, 2020
0.1.1 Aug 7, 2019

#943 in Cryptography

Download history 3/week @ 2024-06-15 9/week @ 2024-06-22 1/week @ 2024-06-29 30/week @ 2024-07-13 6/week @ 2024-07-20 18/week @ 2024-07-27 5/week @ 2024-08-03 7/week @ 2024-08-10 1/week @ 2024-08-17 3/week @ 2024-09-07 3/week @ 2024-09-14 24/week @ 2024-09-21 79/week @ 2024-09-28

109 downloads per month
Used in 2 crates

MPL-2.0 license

140KB
2K SLoC

Tindercrypt

A library that supports data encryption with symmetric cryptographic keys or passwords/passphrases. Uses Protocol Buffers for the serialization of the encryption metadata (salts, nonces, etc.) and is based on the ring Rust crate for the cryptographic primitives.

CI Crates.io Docs.rs

Overview

Tindercrypt's main goal is to provide a safe and easy API for data encryption. The user of this library simply chooses an encryption algorithm and provides a key/passphrase to encrypt their data. To decrypt their data, they provide the same key/passphrase. Behind the scenes, Tindercrypt generates the necessary encryption metadata (salts, nonces, etc.) and bundles them with the encrypted data, so that it can retrieve them when decrypting the data later on.

Features:

  • Does not reinvent crypto. Uses the cryptographic primitives of the well-tested ring crate; PBKDF2 for key derivation, AES256-GCM/ChaCha20-Poly1305 for symmetric encryption.
  • Sane defaults for all cryptographic operations; random nonces and salts, high number of key derivation iterations.
  • Extensibility and compatibility with older versions through Protocol buffers.
  • No book-keeping necessary by the user; all required metadata for the decryption are bundled with the ciphertext.
  • Offers a simple CLI tool that encrypts files with a passphrase.

For a design overview, see the docs section on Tindercrypt metadata.

Examples

You can encrypt (seal) a data buffer with a passphrase as follows:

use tindercrypt::cryptors::RingCryptor;

let plaintext = "The cake is a lie".as_bytes();
let pass = "My secret passphrase".as_bytes();
let cryptor = RingCryptor::new();

let ciphertext = cryptor.seal_with_passphrase(pass, plaintext)?;
let plaintext2 = cryptor.open(pass, &ciphertext)?;
assert_eq!(plaintext2, plaintext);

You can find more examples in the docs section on Tindercrypt's RingCryptor.

The equivalent operation in the CLI tool is the following:

$ echo The cake is a lie > plaintext
$  export TINDERCRYPT_PASSPHRASE="My secret passphrase"  # Note the extra space.
$ tindercrypt encrypt -i plaintext -o ciphertext
$ tindercrypt decrypt -i ciphertext
The cake is a lie

Documentation

You can read the latest docs in https://docs.rs/tindercrypt.

Usage

As a library

When adding this crate to your Cargo.toml, add it with default-features = false, to ensure that CLI specific dependencies are not added to your dependency tree:

tindercrypt = { version = "x.y.z", default-features = false }

As a binary

You can run Tindercrypt using one of the binaries of the stable releases, or the nightly builds. Alternatively, you can install it with one of the following methods:

  • From cargo:
$ cargo install tindercrypt
  • From source:
$ git clone https://github.com/apyrgio/tindercrypt
$ cd tindercrypt
$ cargo build --release
$ ./target/release/tindercrypt --help
Tindecrypt: File encryption tool ...

Contributing

You can read the CONTRIBUTING.md guide for more info on how to contribute to this project.

Licensed under MPL-2.0. Please read the NOTICE.md and LICENSE files for the full copyright and license information. If you feel like putting your mental stability to a test, feel free to read the LEGAL.md file for a foray into the waters of copyright law, and a glimpse of how they can be both boring and dangerous at the same time.

Dependencies

~7–18MB
~350K SLoC