Can't check gpg signature when building rootfs
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 625
- Forks
- 103
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 1
Description
I tried building a rootfs for the latest 19.07 release with:
$ BRANCH=19.07.3 ./docker-rootfs.sh
However it failed to check the gpg signature:
+ export GNUPGHOME=/keys/gpg/
+ GNUPGHOME=/keys/gpg/
+ export USIGNHOME=/keys/usign/
+ USIGNHOME=/keys/usign/
+ curl https://downloads.openwrt.org/releases/19.07.3/targets/x86/64/sha256sums -fs -o sha256sums
+ curl https://downloads.openwrt.org/releases/19.07.3/targets/x86/64/sha256sums.asc -fs -o sha256sums.asc
+ curl https://downloads.openwrt.org/releases/19.07.3/targets/x86/64/sha256sums.sig -fs -o sha256sums.sig
+ '[' '!' -f sha256sums.asc ']'
+ '[' '!' -f sha256sums.asc ']'
+ gpg --with-fingerprint --verify sha256sums.asc sha256sums
gpg: keyblock resource `/keys/gpg//pubring.gpg': file open error
gpg: Signature made Sun 17 May 2020 02:42:57 AM CEST using RSA key ID 2074BE7A
gpg: Can't check signature: public key not found
+ exit 1
Are those /keys/ paths supposed to be on the host system? Obviously it doesn't work in my case because I don't run the script as root...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading docker-rootfs.sh and tracing how GNUPGHOME and USIGNHOME are set before the gpg verification commands shown in the report. Reproduce the 19.07.3 rootfs build if possible; done means the signature check works for a normal invocation without the reported missing-keyring failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- build-system, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100