bluerobotics / bluerobotics/BlueOS

content trust: key-sign published docker images

Open
#2,158 1 comment 0 reactions 0 assignees View on GitHub
security
Dominant language
Vue
Stars
453
Forks
151
Avg merge
1d 3h
Merged PRs (30d)
174

Description

We should look into [keysigning](https://en.wikipedia.org/wiki/Keysigning) our published Docker images using Docker's built in [content trust](https://docs.docker.com/engine/security/trust/) tools.

Vehicles are valuable assets, and it's likely important for some of our users to be able to verify that the images they're installing are indeed unmodified from what we've published.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.