mirror of
https://github.com/restic/restic.git
synced 2024-12-23 00:07:25 +00:00
Clarify B2 Application Keys once again
This commit fixes documentation about Application Keys in Backblaze B2.
This commit is contained in:
parent
686f24b578
commit
30fa305c07
1 changed files with 1 additions and 6 deletions
|
@ -301,12 +301,7 @@ dashboard in on the "Buckets" page when signed into your B2 account:
|
|||
$ export B2_ACCOUNT_ID=<MY_ACCOUNT_ID>
|
||||
$ export B2_ACCOUNT_KEY=<MY_SECRET_ACCOUNT_KEY>
|
||||
|
||||
You can either specify the so-called "Master Application Key" here (which can
|
||||
access any bucket at any path) or a dedicated "Application Key" created just
|
||||
for restic (which may be restricted to a specific bucket and/or path). The
|
||||
master key consists of a ``B2_ACCOUNT_ID`` and a ``B2_ACCOUNT_KEY``, and each
|
||||
application key also is a pair of ``B2_ACCOUNT_ID`` and ``B2_ACCOUNT_KEY``. The
|
||||
ID of an application key is much longer than the ID of the master key.
|
||||
.. note:: In case you want to use Backblaze Application Keys replace <MY_ACCOUNT_ID> and <MY_SECRET_ACCOUNT_KEY> with <applicationKeyId> and <applicationKey> respectively.
|
||||
|
||||
You can then initialize a repository stored at Backblaze B2. If the
|
||||
bucket does not exist yet and the credentials you passed to restic have the
|
||||
|
|
Loading…
Reference in a new issue