Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
R
rekor
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
SafSec
rekor
Commits
a25e0404
Unverified
Commit
a25e0404
authored
4 years ago
by
Luke Hinds
Committed by
GitHub
4 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Update README.md
parent
0da07bea
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+8
-6
8 additions, 6 deletions
README.md
with
8 additions
and
6 deletions
README.md
+
8
−
6
View file @
a25e0404
# Rekor
Rekor is a (planned to be) cloud native cryptographic, immutable, append only software
release ledger.
Rekor is a cryptographic, immutable, append only software release ledger.
It is planned to be used as part of a cloud native build pipeline, but also could be used
in any context where software packaging (and later planned, files) require attestation.
It uses a trillian backend to store in-toto style metadata into an immutable merkle tree.
...
...
@@ -17,9 +19,9 @@ developer's signature embedded within the in-toto link file.
If you had not already noticed, rekor is in very early development, so its not ready for production
use, however if you would like to contribute, then please do.
Its very simple at the moment, but plans are to work more with link files
to allow automation of
integrity checks and design how other link file content such as materials can
be stored and then
queried in a useful manner.
Its very simple at the moment, but plans are to work more with link files
and other manifest structures
to allow automation of
integrity checks and design how other link file content such as materials can
be stored and then
queried in a useful manner.
The trillian components are:
...
...
@@ -99,4 +101,4 @@ rekor get --tlog_id=2587331608088442751 --linkfile tests/package.link
Should your file be returned in full, good news, it matches.
Should no return occur, then something is up (this of course will be handled
better in time).
\ No newline at end of file
better in time).
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment