This commit is contained in:
https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U 2011-04-08 21:51:17 +00:00 committed by admin
parent 9de1f5d9cf
commit 5bca5733fc

View file

@ -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. access to content that has already been stored in the remote.
Different encrypted remotes need to be able to each use different ciphers. 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. of complexity, so is not planned to be supported.
Instead, if you want a new cipher, create a new S3 bucket, or whatever. 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 There does not seem to be much benefit to using the same cipher for