Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

README.md: Disclose the fact that revoking access is not supported. #72

Closed
wants to merge 1 commit into from
Closed

README.md: Disclose the fact that revoking access is not supported. #72

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 13 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,19 @@ there may be backwards-incompatible changes introduced before version
Security
--------

git-crypt is more secure that other transparent git encryption systems.
Currently git-crypt doesn't support revoking access to an encrypted
repository which was previously granted. This first of all applies
to multi-user GPG mode (put simple, there's no del-gpg-user command
to complement add-gpg-user), but also applies to symmetric key mode
(there's no support to rotate this key). It's because this is inherently
complex problem in the context of historical data. For example, even
if a key was rotated at one point of history, a user having previous
key can still access previous repository history. This issue is discussed
in more detail in
https://github.com/AGWA/git-crypt/issues/47 .

On the bare encryption level, git-crypt is more secure than other
transparent git encryption systems.
git-crypt encrypts files using AES-256 in CTR mode with a synthetic IV
derived from the SHA-1 HMAC of the file. This mode of operation is
provably semantically secure under deterministic chosen-plaintext attack.
Expand Down