promote securedrop-workstation-dom0-config 0.7.0 to prod

[sssoleileraaa]

Description

Promoting package on yum-test to prod (see freedomofpress/securedrop-yum-test#38).

Package being released: securedrop-workstation-dom0-config 0.7.0
Package tag: https://github.com/freedomofpress/securedrop-workstation/releases/tag/0.7.0
Build logs: (see freedomofpress/securedrop-yum-test#38)
Prod signing key used to sign package and tag: https://github.com/freedomofpress/securedrop-workstation-prod-rpm-packages-lfs/blob/HEAD/pubkeys/prod.key

Release tracking issue: #33

Checklist for PR owner

• Links in this PR template have been updated as required
• https://github.com/freedomofpress/securedrop-workstation-prod-rpm-packages-lfs/blob/HEAD/pubkeys/prod.key points to the correct prod signing key

Checklist for reviewer

• CI is passing
• The RPM is signed with the prod signing key

  • Download the signed RPM from this PR
  • Run rpm -qi <signed-rpm> to get the KEY ID
  • Run gpg -k <KEY ID> to verify that it matches the prod signing key (make sure you have the prod signing key referenced in the PR description in your GPG keyring)

• The Unsigned RPM checksum matches what's in the build logs (follow steps below on Debian Buster)

  • Download the signed RPM from this PR (if you haven't already)
  • Run rpm --delsign <signed-rpm> to remove the signature
  • Run sha256sum <unsigned-rpm> and compare

[rocodes]

Checklist for reviewer

• CI is passing
• The RPM is signed with the prod signing key

  • Download the signed RPM from this PR
  • Run rpm -qi <signed-rpm> to get the KEY ID
  • Run gpg -k <KEY ID> to verify that it matches the prod signing key (make sure you have the prod signing key referenced in the PR description in your GPG keyring)

• The Unsigned RPM checksum matches what's in the build logs (follow steps below on Debian Buster)

  • Download the signed RPM from this PR (if you haven't already)
  • Run rpm --delsign <signed-rpm> to remove the signature
  • Run sha256sum <unsigned-rpm> and compare

[rocodes]

(Noticed a small date-formatting/creation issue in the build logs that has been fixed here: freedomofpress/securedrop-workstation#805, but as noted, fix can land in a subsequent release)

See my previous comment, test plan looks good, signing looks correct and artifact installs on 4.1.1 machine (currently staging artifact signed with test key).

Thanks Allie!