diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U <Richard@web> | 2011-04-08 21:51:17 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2011-04-08 21:51:17 +0000 |
| commit | 5bca5733fc674ed8244b5589855dde5c92df2934 (patch) | |
| tree | 4432a51a808608fb3404ccab636bfd144455771a | |
| parent | 9de1f5d9cfec3492ebee55fabc64f36a595d5be5 (diff) | |
typo
| -rw-r--r-- | doc/design/encryption.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/design/encryption.mdwn b/doc/design/encryption.mdwn index 8a8f38108..90b722b9b 100644 --- a/doc/design/encryption.mdwn +++ b/doc/design/encryption.mdwn @@ -61,7 +61,7 @@ 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. -Allowing multiple cipers to be used within a single remote would add a lot +Allowing multiple ciphers 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 |