|0.2.16||Oct 21, 2022|
|0.2.14||Jul 24, 2022|
|0.2.12||Feb 16, 2022|
|0.2.10||Dec 4, 2021|
|0.1.2||Jul 4, 2020|
145 downloads per month
Spritual successor of https://github.com/untoldwind/trustless taking over the concepts that worked, improving those that did not turned out so well and avoiding all the quirky stuff (potentially by replacing it with new quirky stuff).
Some major changes:
t-rust-lessis a ground up rewrite in rust (as the name suggests)
- ... which allows a much better control over memory and protecting/cleaning up sensitive data.
- For the most part
trustlesstried to be compatible with
t-rust-lessdrops this idea entirely in favor of adding some modern ciphers and key-derivations to the mix.
- ... which essentially means that a
trustlessstore will not be compatible with a
t-rust-lesswhatsoever. Sorry, but an
importwill be required.
Best use the
./build-release.sh script with will bootstrap a docker container containing all the relevant dependencies.
Otherwise you need:
- Rust version >=1.34
- If you want to make changes to
secret_store.capnpyou also need the Capn Proto compiler (capnpc), i.e. install
openssl-sysperl is required
To windows (library only atm)
Building (on Archlinux)
On one needs AUR
[target.x86_64-pc-windows-gnu] linker = "/usr/bin/x86_64-w64-mingw32-gcc" ar = "/usr/x86_64-w64-mingw32/bin/ar"
cd cli; cargo build --target x86_64-pc-windows-gnu --features crossterm_backend --no-default-features --release
(unluckily we cannot automatically toggle features based on target)
If you get an linkage error with
__onexitend, most likely the
crt2.o does not match:
mv ~/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-gnu/lib/crt2.o ~/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-gnu/lib/crt2.o.bak cp /usr/x86_64-w64-mingw32/lib/crt2.o ~/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-pc-windows-gnu/lib/crt2.o
To wasm (library only)
cargo build --release --target=wasm32-unknown-emscripten
Some tests are pretty slow and will be ignored during a regular development cycle with
cargo test. To run the full suit for regression:
cargo test --release