rind

Run object_store on rind

This page describes rind-object-store as main has it, ahead of rind-object-store 0.14.3 on crates.io. Until its next release, take it from git at the commit this page describes. Beside the lines below, add this line under the [patch.crates-io] table of your workspace's root Cargo.toml (add the table if it has none), then run cargo update -p rind-object-store:

rind-object-store = { git = "https://github.com/kixel-ai/rind", rev = "80fc7ba544b53a6ca9ab21ba9a946c275eb19a06" }

That moves every crate in your tree that depends on rind-object-store, and cargo tree -i rind-object-store then shows it from git+https://github.com/kixel-ai/rind.

This crate provides a CryptoProvider for object_store, backed by rind, a fork of Graviola. It signs S3, Azure, and GCS requests.

Build object_store with its aws-base, azure-base, or gcp-base features rather than aws, azure, or gcp, which also compile aws-lc-rs:

[dependencies]
object_store = { version = "0.14", default-features = false, features = ["gcp-base", "reqwest"] }
reqwest = { version = "0.13", default-features = false, features = ["native-tls"] }
rind-object-store = "0.14"

The -base features bring no HTTP transport: reqwest supplies one, and its native-tls feature keeps it off aws-lc-rs.

Then hand the provider to each store's builder:

let store = object_store::gcp::GoogleCloudStorageBuilder::new()
    .with_bucket_name("bucket")
    .with_crypto_provider(rind_object_store::default_provider())
    .build()?;

What rind cannot back

Nothing: it computes every digest, HMAC, and signature object_store's CryptoProvider names.

WebAssembly

It builds for wasm32-wasip2 and wasm32-unknown-unknown, the browser, where rind needs its JavaScript random source, getrandom = { version = "0.4", features = ["wasm_js"] }. PLATFORMS.md lists what each adapter's upstream needs there too, and why rind's constant-time checks do not cover wasm.

Switch with an agent

Paste this into your coding agent, in your repository:

Move this repository from ring or aws-lc-rs to rind, following
https://raw.githubusercontent.com/kixel-ai/rind/main/MIGRATE.md

It migrates on a local branch, reports the build time, binary size, benchmarks, and tests before and after, and asks before opening a PR or filing an issue. To migrate by hand, MIGRATING.md maps each ring and aws-lc-rs item to rind's.

Other libraries