Skip to content
Snippets Groups Projects
user avatar
Bob Callaway authored
Since the API key can be specified as an environment variable and could
be thought of as an authentication credential, it should not be included
in the path to the created entry in the log.

Previously we simply appended the new entry's UUID to the full URL,
which was incorrect if an API key was specified as a query parameter.

Fixes #182

Signed-off-by: default avatarBob Callaway <bcallawa@redhat.com>
b0eae9b8
History

Rekor

Rekór - Greek for “Record”

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 life-cycle. For more details visit the rekor 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.

For more details on setting up a server, visit the following link

For details on CLI usage, visit the following link

If you're interesting in integration with rekor, we have an OpenAPI swagger editor

A public instance of rekor can be found at api.rekor.dev

Rekor allows customized manifests (which term them as types), type customization is outlined here.

Contributions

Rekor is still in its early phase of development, so we welcome contributions from anyone.