vach 0.4.5

A simple archiving format, designed for storing assets in compact secure containers
Documentation

vach, pronounced like "puck" but with a "v", is an archiving and resource transmission format. It was built to be secure, contained and protected. It was, in fact, designed by the SCP to keep your anomalous assets compact and secure during transmission. A big benefit of vach is the fine grained control it grants it's users, as it allows for per-entry independent configuration. vach also has in-built support for multiple compression schemes (LZ4, Snappy and Brolti), data signing, leaf bitflags, encryption and some degree of archive customization. Check out the vach spec at spec.txt. Any and all help will be much appreciated, especially proof reading the docs and code review.

⛏ Who is this for?

  • You just released some software and don't want your assets pirated or easily read.
  • You want a simple convenient way to manage, decompress, decrypt and authenticate assets in distribution.
  • You want a pure Rust™️ archive format with no C bindings underneath (bindings for C may become available in the future).
  • You want your software to be neat, and all your assets to be in one neat secure container.
  • You like orbital cannons.

🧷 Simple usage

use std::fs::File;
use vach::prelude::{Archive, Resource, Flags};

let source = File::open("sounds.vach")?;

let mut archive = Archive::new(source)?;
let resource: Resource = archive.fetch_mut("footstep.wav")?;

// By default all resources are flagged as NOT secure
assert!(!resource.authenticated);

// Use the data
use my_crate::Sound;
println!("{}", Sound::new(resource.data.as_slice())?);

// Read data directly into an `io::Write` stream
let mut buffer = Vec::new();
let (flags, content_version, is_secure) = archive.fetch_mut("ftstep", &mut buffer)?;

For more information on how to use the crate, read the documentation or pass by the repository. Maybe also check out the CLI, for a more user-friendly use of vach