diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-04-07 16:05:30 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-04-07 16:05:30 -0400 |
| commit | bd1bbc21fac4b36975d03638d15e9aab915927cf (patch) | |
| tree | 4231858b98478ebfa00160c19ed547d17010af08 /doc/design/encryption.mdwn | |
| parent | 135d75f2b9c0f77b837da4243dea32a97d4088a5 (diff) | |
update
Diffstat (limited to 'doc/design/encryption.mdwn')
| -rw-r--r-- | doc/design/encryption.mdwn | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/design/encryption.mdwn b/doc/design/encryption.mdwn index f8f8656a7..8a8f38108 100644 --- a/doc/design/encryption.mdwn +++ b/doc/design/encryption.mdwn @@ -61,8 +61,8 @@ more gpg public keys. This scheme allows new gpg private keys to be given access to content that has already been stored in the remote. Different encrypted remotes need to be able to each use different ciphers. -There does not seem to be a benefit to allowing multiple cipers to be -used within a single remote, and it would add a lot of complexity. +Allowing multiple cipers to be used within a single remote would add a lot +of complexity, so is not planned to be supported. Instead, if you want a new cipher, create a new S3 bucket, or whatever. There does not seem to be much benefit to using the same cipher for two different enrypted remotes. |