Repository navigation
Far fewer 1Password prompts: a token refresh writes back to the secret store only when it must
(#178).
Fixed
- Far fewer 1Password prompts. A token refresh no longer writes to the secret store unless
it must: a Gmail refresh (the refresh token never changes) writes nothing, and a Microsoft
365 refresh saves its rotated refresh token at most once a day. The access token stays in
memory and is refreshed again after a restart. Withsecrets = "1password"this takes the
daemon from about one prompt an hour per account to one when each account's sync starts. See
Tokens in 1Password.
Downloads
| Archive | For |
|---|---|
rail-v0.10.1-x86_64-unknown-linux-gnu.tar.gz |
Linux x86_64, glibc 2.36 or newer |
rail-v0.10.1-aarch64-unknown-linux-gnu.tar.gz |
Linux ARM64, glibc 2.36 or newer |
rail-v0.10.1-aarch64-apple-darwin.tar.gz |
macOS 11 or newer on Apple Silicon |
rail-v0.10.1-x86_64-apple-darwin.tar.gz |
macOS 11 or newer on Intel |
Each archive holds the rail binary, the README and docs/, the changelog, the licences and
BUILD-INFO.txt. Extract it and put rail in a directory on your PATH.
Check an archive against SHA256SUMS, and check where it was built:
sha256sum -c --ignore-missing SHA256SUMS # macOS: shasum -a 256 -c --ignore-missing SHA256SUMS
gh attestation verify rail-v0.10.1-<target>.tar.gz --repo vitosans/railOn other systems, build from the tag with Rust 1.88 or newer:
git clone --branch v0.10.1 --depth 1 https://github.com/vitosans/rail.git
cd rail
cargo install --locked --path crates/rail