-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build: verify tag signatures #110
Conversation
dfa46c8
to
d242329
Compare
d242329
to
c03a230
Compare
c03a230
to
1fd99d9
Compare
1558f87
to
44e765f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cACK
I have limited docker knowledge, but the change looks good to me.
I've verified all the added pubkeys, except yours: Kristaps and Adam's match the ones listed in JM repo and dergigi's matches the one listed on his website (dergigi.com/pgp). I'm not sure where yours is listed tho?:)
doc change also LGTM
Can be seen e.g. when you click the "verified" badge on the commits, should be
👍 🙏 |
7d15c16
to
ac9eb7f
Compare
ac9eb7f
to
67ab436
Compare
e.g. see a failed build GitHub actions run for this scenario, building a non-release version (from current "master") having |
e.g. see a success build GitHub actions run for this scenario, building a release version ("v0.3.0") having SKIP_RELEASE_VERIFICATION := false.
|
Verify release signatures.
After this change, you will only be able to build from signed tags for both JM and Jam (e.g. v0.1.5 for Jam, v0.9.10 for JM) when signature verification is enabled (defaults to
true
).For testing purposes, if you want to build from non-tagged objects, e.g. the latest commit in
master
branch, you must disable signature verification with--build-arg VERIFY_RELEASE=false
.Test
Try to build the
ui-only
image....should succeed with enabled verification of a tagged object (tag v0.3.0):
..should fail with enabled verification of a non-tagged object (branch master):
Exits with an error like:
..should succeed with disabled verification of a non-tagged object (branch master):
..should fail with enabled verification of a tagged object (tag v0.3.0) if no pubkey can be found:
Delete the pubkey
./ui-only/pubkeys/tbk.asc
locally and run:Exits with an error like: