mirror of
https://github.com/project-zot/zot.git
synced 2026-06-16 04:17:55 +08:00
41b05c60dd8d8a7c043aaf1986234f89d1f0a8e7
In order to verify signatures, users could upload their certificates and public keys using these routes: -> for public keys: /v2/_zot/ext/mgmt?resource=signatures&tool=cosign -> for certificates: /v2/_zot/ext/mgmt?resource=signatures&tool=notation&truststoreType=ca&truststoreName=name Then the public keys will be stored under $rootdir/_cosign and the certificates will be stored under $rootdir/_notation/truststore/x509/$truststoreType/$truststoreName. Also, for notation case, the "truststores" field of $rootir/_notation/trustpolicy.json file will be updated with a new entry "$truststoreType:$truststoreName". Also based on the uploaded files, the information about the signatures validity will be updated periodically. Signed-off-by: Andreea-Lupu <andreealupu1470@yahoo.com>
chore(trivy): update trivy version and enforce OCI compliant repo names in local image storage (#1068)
zot

zot: a production-ready vendor-neutral OCI image registry - images stored in OCI image format, distribution specification on-the-wire, that's it!
Docs
Documentation for zot is located at: https://zotregistry.io
Code of Conduct
Details are in the code of conduct
Description
Languages
Go
93.6%
Shell
5.8%
Makefile
0.4%