mirror of https://github.com/docker/docs.git
Merge pull request #7426 from docker/notary-reference-client-config
Update client-config.md
This commit is contained in:
commit
718784351c
|
|
@ -125,7 +125,7 @@ but the pinned certificates take highest priority for validation, followed
|
||||||
by the pinned CA, followed by TOFUS (TOFU over HTTPS). The diagram below
|
by the pinned CA, followed by TOFUS (TOFU over HTTPS). The diagram below
|
||||||
describes this validation flow:
|
describes this validation flow:
|
||||||
|
|
||||||

|

|
||||||
|
|
||||||
Only one trust pinning option is used to validate a GUN even if multiple
|
Only one trust pinning option is used to validate a GUN even if multiple
|
||||||
sections are specified, and any validation failure results in a failed
|
sections are specified, and any validation failure results in a failed
|
||||||
|
|
@ -176,6 +176,7 @@ passphrase.
|
||||||
|`NOTARY_TARGETS_PASSPHRASE` | The targets (an online) key passphrase |
|
|`NOTARY_TARGETS_PASSPHRASE` | The targets (an online) key passphrase |
|
||||||
|`NOTARY_SNAPSHOT_PASSPHRASE` | The snapshot (an online) key passphrase |
|
|`NOTARY_SNAPSHOT_PASSPHRASE` | The snapshot (an online) key passphrase |
|
||||||
|`NOTARY_DELEGATION_PASSPHRASE` | The delegation (an online) key passphrase |
|
|`NOTARY_DELEGATION_PASSPHRASE` | The delegation (an online) key passphrase |
|
||||||
|
|`NOTARY_AUTH` | The notary server credentials: `<username>:<password>` encoded in base64 |
|
||||||
|
|
||||||
|
|
||||||
If provided, the passphrase in `NOTARY_DELEGATION_PASSPHRASE`
|
If provided, the passphrase in `NOTARY_DELEGATION_PASSPHRASE`
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue