Supply Chain Transparency Log

Edit Package rekor
https://github.com/sigstore/rekor

Rekor's goals are to provide an immutable tamper resistant ledger of metadata generated within a software projects supply chain. Rekor will enable software maintainers and build systems to record signed metadata to an immutable record. Other parties can then query said metadata to enable them to make informed decisions on trust and non-repudiation of an object's lifecycle. For more details visit the sigstore website

The Rekor project provides a restful API based server for validation and a transparency log for storage. A CLI application is available to make and verify entries, query the transparency log for inclusion proof, integrity verification of the transparency log or retrieval of entries by either public key or artifact.

Rekor fulfils the signature transparency role of sigstore's software signing infrastructure. However, Rekor can be run on its own and is designed to be extensible to working with different manifest schemas and PKI tooling.

Refresh
Refresh
Source Files
Filename Size Changed
_service 0000000122 122 Bytes
rekor-1.3.5.tar.gz 0000830762 811 KB
rekor-zypper-verify.sh 0000000941 941 Bytes
rekor.changes 0000022904 22.4 KB
rekor.spec 0000003019 2.95 KB
vendor.tar.zst 0008391086 8 MB
Latest Revision
Ana Guerrero's avatar Ana Guerrero (anag+factory) accepted request 1144326 from Marcus Meissner's avatar Marcus Meissner (msmeissn) (revision 21)
- update to 1.3.5 (jsc#SLE-23476):
  - Additional unique index correction
  - Remove timestamp from checkpoint
  - Drop conditional when verifying entry checkpoint
  - Fix panic for DSSE canonicalization
  - Change Redis value for locking mechanism
  - give log timestamps nanosecond precision
  - output trace in slog and override correlation header name
- bumped embedded golang.org/x/crypto/ssh to fix the Terrapin attack CVE-2023-48795 (bsc#1218207) (forwarded request 1144325 from msmeissn)
Comments 0
openSUSE Build Service is sponsored by