Crates.io | litcrypt |
lib.rs | litcrypt |
version | 0.3.0 |
source | src |
created_at | 2021-02-04 14:18:18.108152 |
updated_at | 2021-09-10 11:30:40.219912 |
description | Let's encrypt your string statically during compile time |
homepage | |
repository | https://github.com/anvie/litcrypt.rs |
max_upload_size | |
id | 350533 |
size | 15,633 |
It is abbreviation from "Literal Encryption", a Rust proc macro designed to encrypt text literal using simple "XOR" algorithm.
LITCRYPT let's you hide your static string literal in the binary from naughty eyes seamlessly and protect your valuable app from illegal cracking activity.
LITCRYPT works by encrypting string literal during compilation time and the encrypted string remain encrypted in both disk and memory during runtime until it will be used.
Dependencies:
[dependencies]
litcrypt = "0.3"
Example:
#[macro_use]
extern crate litcrypt;
use_litcrypt!();
fn main(){
println!("his name is: {}", lc!("Voldemort"));
}
use_litcrypt!
macro call should be called first for initialization before you can
use lc!
macro function. The first parameter is your secret key used for encrypt your
literal string. This key is also encrypted and will not visible under static analyzer.
Please take note that you need to set your encryption key using environment variable
LITCRYPT_ENCRYPT_KEY
before compile:
e.g:
$ export LITCRYPT_ENCRYPT_KEY="myverysuperdupermegaultrasecretkey"
Litcrypt will encrypt each string written inside lc!
statically.
Check the output binary using strings
command to verify:
$ strings target/debug/my_valuable_app | grep Voldemort
If the output is blank then your valuable string in your app is safe from static analyzer tool like Hexeditor etc.
For working example code see ./examples
directory, and test using:
$ cargo run --example simple
[] Robin.