diff options
| author |  guilhem <guilhem@fripost.org> | 2013-03-29 17:06:02 +0100 |
|---|---|---|
| committer |  Joey Hess <joey@kitenet.net> | 2013-03-29 18:04:52 -0400 |
| commit | 71760a359f5515053085f242258dc615a1db1fd8 (patch) | |
| tree | 0e49337fb773b721173aa25fc36635e05d8918f8 /doc/design/encryption.mdwn | |
| parent | f3ee9b50b3a9caff7ec65ddaa9197f6daaf6f745 (diff) | |
Allow other MAC algorithms in the Remote Config.
Diffstat (limited to 'doc/design/encryption.mdwn')
| -rw-r--r-- | doc/design/encryption.mdwn | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/design/encryption.mdwn b/doc/design/encryption.mdwn index b7acbb732..45eb43cc9 100644 --- a/doc/design/encryption.mdwn +++ b/doc/design/encryption.mdwn @@ -59,10 +59,11 @@ for each file in the repository, contact the encrypted remote to check if it has the file. This can be done without enumeration, although it will mean running gpg once per file fscked, to get the encrypted filename. -So, the files stored in the remote should be encrypted. But, it needs -to be a repeatable encryption, so they cannot just be gpg encrypted, -that would yeild a new name each time. Instead, HMAC is used. Any hash -could be used with HMAC; currently SHA1 is used. +So, the files stored in the remote should be encrypted. But, it needs to +be a repeatable encryption, so they cannot just be gpg encrypted, that +would yeild a new name each time. Instead, HMAC is used. Any hash could +be used with HMAC. SHA-1 is the default, but [[other_hashes|/encryption]] +can be chosen for new remotes. It was suggested that it might not be wise to use the same cipher for both gpg and HMAC. Being paranoid, it's best not to tie the security of one |