Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Wiki Replica
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
Service Desk
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
Cecylia Bocovich
Wiki Replica
Commits
b08f68cc
Verified
Commit
b08f68cc
authored
3 years ago
by
anarcat
Browse files
Options
Downloads
Patches
Plain Diff
expand TUF's usage in sigstore
parent
37a3f115
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
howto/gitlab.md
+26
-6
26 additions, 6 deletions
howto/gitlab.md
with
26 additions
and
6 deletions
howto/gitlab.md
+
26
−
6
View file @
b08f68cc
...
...
@@ -1203,23 +1203,43 @@ it's still nice to have options.
[
Dan Lorenc
][]
, an engineer at Google, designed a tool that allows
users to sign "artifacts". Typically, those are container images
(e.g.
[
cosign
]
(
https://github.com/sigstore/cosign
)
is named so because it signs "containers"), but
(e.g.
[
cosign
]
[]
is named so because it signs "containers"), but
anything can be signed.
It also works with a transparency log server called
[
rekor
](
https://github.com/sigstore/rekor
)
. They
[
Dan Lorenc
]:
https://github.com/dlorenc
[
cosign
]:
https://github.com/sigstore/cosign
It also works with a transparency log server called
[
rekor
][]
. They
run a public instance, but we could also run our own. It is currently
unclear if we could have both, but it's apparently possible to run a
"monitor" that would check the log for consistency.
There's also a system for
[
signing binaries with ephemeral keys
](
https://shibumi.dev/posts/first-look-into-cosign/
)
[
rekor
]:
https://github.com/sigstore/rekor
There's also a system for
[
signing binaries with ephemeral keys
][]
which seems counter-intuitive but actually works nicely for CI jobs.
[
signing binaries with ephemeral keys
]:
https://shibumi.dev/posts/first-look-into-cosign/
Seems very promising, maintained by Google, RedHat, and supported by
the Linux foundation. Complementary to
[
in-toto
][]
and
[
TUF
][]
.
the Linux foundation. Complementary to
[
in-toto
][]
and
[
TUF
][]
. TUF is
actually used to create the
[
root keys
][]
which are controlled, at
the time of writing, by:
[
TUF
]:
https://theupdateframework.io/
[
in-toto
]:
https://github.com/in-toto/in-toto
[
Dan Lorenc
]:
https://github.com/dlorenc
[
TUF
]:
https://theupdateframework.io/
[
root keys
]:
https://github.com/sigstore/root-signing
*
[
Bob Callaway
][]
(Google)
*
[
Dan Lorenc
][]
(Google)
*
[
Luke Hinds
][]
(RedHat)
*
[
Marina Moore
][]
(NYU)
*
[
Santiago Torres
][]
(Purdue)
[
Luke Hinds
]:
https://github.com/lukehinds
[
Marina Moore
]:
https://github.com/mnm678
[
Santiago Torres
]:
https://github.com/SantiagoTorres
[
Bob Callaway
]:
https://github.com/bobcallaway
### Other caveats
...
...
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