mirror of
https://github.com/project-zot/zot.git
synced 2025-01-20 22:52:51 -05:00
d5065513f5
- Cosign supports 2 types of signature formats:
1. Using tag -> each new signature of the same manifest is
added as a new layer of the signature manifest having that
specific tag("{alghoritm}-{digest_of_signed_manifest}.sig")
2. Using referrers -> each new signature of the same manifest is
added as a new manifest
- For adding these cosign signature to metadb, we reserved index 0 of the
list of cosign signatures for tag-based signatures. When a new tag-based
signature is added for the same manifest, the element on first position
in its list of cosign signatures(in metadb) will be updated/overwritten.
When a new cosign signature(using referrers) will be added for the same
manifest this new signature will be appended to the list of cosign
signatures.
Signed-off-by: Andreea-Lupu <andreealupu1470@yahoo.com>
|
||
|---|---|---|
| .. | ||
| cache | ||
| common | ||
| constants | ||
| gc | ||
| imagestore | ||
| local | ||
| s3 | ||
| types | ||
| cache.go | ||
| cache_benchmark_test.go | ||
| cache_test.go | ||
| README.md | ||
| scrub.go | ||
| scrub_test.go | ||
| storage.go | ||
| storage_controller.go | ||
| storage_test.go | ||
zot currently supports two types of underlying filesystems:
-
local - a locally mounted filesystem
-
remote - a remote filesystem such as AWS S3
The cache database can be configured independently of storage. Right now, zot supports the following database implementations:
- BoltDB - local storage. Set the "cloudCache" field in the config file to false. Example: examples/config-boltdb.json