[MDBF-260] git release tags are not signed Created: 2021-08-04 Updated: 2022-02-01 |
|
| Status: | Closed |
| Project: | MariaDB Foundation Development |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Otto Kekäläinen | Assignee: | Daniel Bartholomew |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | Security, security | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 0.25d | ||
| Original Estimate: | Not Specified | ||
| Description |
|
It seems that the git tags used to tag MariaDB Server releases are not signed. For example the recent mariadb-10.6.3 tag by serg and mariadb-10.4.20 by marko don't seem to be signed. Compare: noformat noformat Signing can be done by adding `-s` to `git tag -s mariadb-10.5.12` when tagging. You could use the same GPG key to sign the tags as is used to sign the tar.gz source releases. For details see:
|
| Comments |
| Comment by Marko Mäkelä [ 2021-08-04 ] | |||||||||||||||||||||||||
|
For what it is worth, I do not remember ever creating any tag in any Git repository. I have understood that dbart normally creates tags as part of the release process. | |||||||||||||||||||||||||
| Comment by Otto Kekäläinen [ 2021-08-07 ] | |||||||||||||||||||||||||
|
The latest tags are now signed, but with Daniel's personal key which does not seem to be published on the usual keyservers, so it normal users can't verify these tags:
| |||||||||||||||||||||||||
| Comment by Daniel Bartholomew [ 2021-08-09 ] | |||||||||||||||||||||||||
|
Yes, for this round of releases I added the following to my ~/.gitconfig:
...so it used my personal gpg key, the same that I use to sign commits. I will add signingkey = F1656F24C74CD1D8 to that section of the config so that the same signing-key@mariadb.org key that I use to sign Debian/Ubuntu repositories is used for future tags. As far as publishing my personal key goes, I thought it was published to at least keyserver.ubuntu.com. If there are other "usual" keyservers I should publish it to, please let me know. I published it again just now. As an aside, I used to have gpg configured to sync with the pool of servers at sks-keyservers.net, but that service seems to have shut down. Are there any replacement pools? | |||||||||||||||||||||||||
| Comment by Daniel Bartholomew [ 2021-08-09 ] | |||||||||||||||||||||||||
|
Actually, to properly sign the tag I need to specify it on the command-line, e.g.:
(Putting this here for future me) | |||||||||||||||||||||||||
| Comment by Otto Kekäläinen [ 2021-08-11 ] | |||||||||||||||||||||||||
|
Thanks for looking into it. This is what I got originally:
Now I get:
And your key is now visible at https://keyserver.ubuntu.com/pks/lookup?search=0x9171189995E45A9E&fingerprint=on&op=index | |||||||||||||||||||||||||
| Comment by Daniel Bartholomew [ 2021-08-11 ] | |||||||||||||||||||||||||
|
It won't be the signature I use for future tag signing, but good that it at least now shows up. Thanks. |