Abstraction layer for symmetric data encryption, primarily designed for database column encryption.
Find a file
2024-04-07 22:10:40 +02:00
benches Change the randomly generated benchmark input 2024-04-01 16:25:37 +02:00
src Add more documentation 2024-04-07 22:10:40 +02:00
.gitignore First commit 2024-02-14 18:16:45 +01:00
Cargo.toml Allow to encrypt at a specific timestamp 2024-04-07 12:22:04 +02:00
deny.toml Update cargo-deny 2024-03-23 11:41:45 +01:00
README.md Update the readme 2024-02-25 23:05:22 +01:00
rustfmt.toml First commit 2024-02-14 18:16:45 +01:00

Coffio

License MIT OR Apache 2.0

Abstraction layer for symmetric data encryption, primarily designed for database column encryption.

Disclaimer

⚠️ DANGER: DRAGONS A(H)EAD! 🐲

This crate is experimental and has never been audited by an independent security professional. You should therefore NOT use it in production.

Although this crate aim to reduce the risk of misuse, it is still possible to use it in such a way that the cryptography it uses does not provides all the security guaranties you need. Ask your cryptographer if this crate is relevant to your use case and if you are using it correctly.

Frequently Asked Questions

Should I use this crate?

Although it may work, some parts are not stabilized yet. Expect breaking change that may result in the total loss of previously encrypted data.

Why should I use this crate instead of a symmetric encryption function?

  1. Strong algorithms only. If you don't know which one to chose, Coffio provides strong defaults.
  2. Key management is hard. Coffio largely simplifies it in a way it becomes largely accessible.

Why has this crate not been audited by a security professional?

Such an audit cost a lot of money. If you really care about this crate being audited, you may help financing it.

Where does the name coffio comes from?

It is a french slang for a safe or a strongbox. See coffio on the french Wiktionary.