diff options
author | Joey Hess <joey@kitenet.net> | 2013-04-26 18:22:44 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2013-04-26 18:22:52 -0400 |
commit | 8d7348fe1be96f95eda6c8cf386b54825e0b69fd (patch) | |
tree | 30cd1c58fcd6766573892873a2cd7f9fa999c196 /doc/encryption.mdwn | |
parent | ee51adad7bdad29e77e5d51a192c8de5653fd06e (diff) |
To enable an existing special remote, the new enableremote command must be used. The initremote command now is used only to create new special remotes.
Diffstat (limited to 'doc/encryption.mdwn')
-rw-r--r-- | doc/encryption.mdwn | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/encryption.mdwn b/doc/encryption.mdwn index 5349e8c7a..d93bee9d2 100644 --- a/doc/encryption.mdwn +++ b/doc/encryption.mdwn @@ -31,10 +31,10 @@ non-empty remote. The [[encryption_design|design/encryption]] allows additional encryption keys to be added on to a special remote later. Once a key is added, it is able to access content that has already been stored in the special remote. -To add a new key, just run `git annex initremote` again, specifying the +To add a new key, just run `git annex enableremote` specifying the new encryption key: - git annex initremote myremote encryption=788A3F4C + git annex enableremote myremote encryption=788A3F4C Note that once a key has been given access to a remote, it's not possible to revoke that access, short of deleting the remote. See |