Don't claim auth.json contains encrypted information

... to decrease the risk that users might think it doesn't need
protecting.

Signed-off-by: Miloslav Trmač <mitr@redhat.com>
This commit is contained in:
Miloslav Trmač 2023-03-13 19:56:11 +01:00
parent 5184c1a67f
commit 6691c33c7f
1 changed files with 2 additions and 2 deletions

View File

@ -18,8 +18,8 @@ Except the primary (read/write) file, other files are read-only, unless the user
## FORMAT ## FORMAT
The auth.json file stores encrypted authentication information for the The auth.json file stores, or references, credentials that allow the user to authenticate
user to container image registries. The file can have zero to many entries and to container image registries. The file can have zero to many entries and
is created by a `login` command from a container tool such as `podman login`, is created by a `login` command from a container tool such as `podman login`,
`buildah login` or `skopeo login`. Each entry either contains a single `buildah login` or `skopeo login`. Each entry either contains a single
hostname (e.g. `docker.io`) or a namespace (e.g. `quay.io/user/image`) as a key hostname (e.g. `docker.io`) or a namespace (e.g. `quay.io/user/image`) as a key