Repository navigation
Conversation
Explain why end-to-end encryption matters before the mechanics, and compare against git-crypt, transcrypt, and git-remote-gcrypt with a metadata-visibility table and a capability table backed by footnotes citing each tool's own documentation. Move usage details to docs/guide.md and test notes to CONTRIBUTING.md, and add SECURITY.md, a Japanese README, and an overview illustration.
Drop transcrypt from the tables, reframe the third advantage as managed membership since gcrypt already uses per-participant keys, and replace the fetch row with a GitHub-storage caveat for both encrypted remotes.
Uniformly random 32-byte encapsulated keys set the top bit about half the time, which a real X25519 public key never does, so storage could count real readers. Seal a random key to a throwaway recipient instead, and add a regression test.
# Conflicts: # README.ja.md
Mark GitHub/GitLab storage as supported for every tool now that the carrier cache makes fetches incremental, rename rows to No master key, Roles, and No external dependencies, collapse the notes into a details block, and drop the post-quantum FAQ.
CI runners have no global Git identity, so committing in a fresh clone failed there while passing on developer machines.
Icons are MIT-licensed; the license is included next to the figure.
This was referenced Oct 14, 2026
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two things, stacked in one PR:
1. README rewrite
docs/art/overview.svg), moves usage details todocs/guide.mdand test notes toCONTRIBUTING.md, and addsSECURITY.md.2. Format v5: anonymous recipients
Storage previously saw every device's per-repository public keys, roles, and membership changes. v5 reduces that to a padded reader count (see
docs/design.md, "Anonymous recipients"):K_t-derived subkey. Policies travel inside the transition manifest's encrypted body;policies/objects are gone.docs/spec.md,docs/design.md,docs/guide.md, and the README tables are updated. v5 is intentionally incompatible with v4 (prototype; no migration).Also included
main(Flush Windows directory entries before acknowledging persistence #1 moved design/spec/benchmarks intodocs/), with one fixture fix (verified_refs) needed after combining it with previously unpushed local commits (benchmarks, incremental connectivity checks, storage validation refactor).Checks
cargo fmt --all -- --check,cargo clippy --all-targets -- -D warnings, andcargo test --all-targetspass locally: 70 passed, 1 ignored (the external power-cut harness).Notes
SECURITY.mdasks for private reports to git-remote-e2ee@combinatrix.ai.