From 6d6e96f82b63cc09274367668de90d62dc027a32 Mon Sep 17 00:00:00 2001 From: Andrew Ayer Date: Tue, 17 Mar 2015 15:08:35 -0700 Subject: [PATCH] Clarify security section in README --- README | 2 +- README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README b/README index 46ed750..2eae0fe 100644 --- a/README +++ b/README @@ -79,7 +79,7 @@ SECURITY git-crypt is more secure that 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 is provably semantically +derived from the SHA-1 HMAC of the file. This mode of operation is provably semantically secure under deterministic chosen-plaintext attack. That means that although the encryption is deterministic (which is required so git can distinguish when a file has and hasn't changed), it leaks no information diff --git a/README.md b/README.md index 785b494..058f6ea 100644 --- a/README.md +++ b/README.md @@ -81,7 +81,7 @@ Security git-crypt is more secure that 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 is provably semantically +derived from the SHA-1 HMAC of the file. This mode of operation is provably semantically secure under deterministic chosen-plaintext attack. That means that although the encryption is deterministic (which is required so git can distinguish when a file has and hasn't changed), it leaks no information