annex.cachecreds: New config to allow disabling of credentials caching for special remotes.
Note that it does not prevent storing p2p access tokens or multicast encryption keys, since those are not cached; the previous commit established the distinction. How well this works depends on how often getRemoteCredPair is called and how expensive it is. In some cases setting this will result in an annoying number of gpg password prompts and/or slowdowns due to reading creds from the git-annex branch and decrypting, which could be improved by calling getRemoteCredPair less often. This commit was sponsored by Ilya Shlyakhter on Patreon.
This commit is contained in:
parent
e89bb4361b
commit
ab7746a2ae
6 changed files with 61 additions and 2 deletions
|
@ -129,3 +129,16 @@ of the special remote with the option `mac=HMACSHA512`. The available
|
|||
MAC algorithms are HMACSHA1, HMACSHA224, HMACSHA256, HMACSHA384, and
|
||||
HMACSHA512. Note that it is not possible to change algorithm for a
|
||||
non-empty remote.
|
||||
|
||||
## credentials storage
|
||||
|
||||
Special remotes that need some form of credentials, such as a password,
|
||||
may support embedding the credentials in the git repository, using
|
||||
embedcreds=yes. See individual special remotes' documentation for details.
|
||||
When credentials are embedded in the repository, they're also encrypted using
|
||||
whatever encryption setting has been selected for the repository.
|
||||
|
||||
Such credentials are also cached locally in a file only you can read,
|
||||
in `.git/annex/creds/`. If you prefer to not expose the credentials on disk
|
||||
in unencrypted form, you can disable this cache, by setting the
|
||||
`annex.cachecreds` config to `false`.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue