Issue 19434 - "Invalid signature" when using install.sh with no ~/.gnupg
Summary: "Invalid signature" when using install.sh with no ~/.gnupg
Status: RESOLVED FIXED
Alias: None
Product: D
Classification: Unclassified
Component: installer (show other issues)
Version: D2
Hardware: All Linux
: P1 normal
Assignee: No Owner
URL:
Keywords: pull
Depends on:
Blocks:
 
Reported: 2018-11-25 16:37 UTC by Vladimir Panteleev
Modified: 2018-11-27 10:42 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Vladimir Panteleev 2018-11-25 16:37:58 UTC 
Using install.sh fails with the above message on my server.

Un-redirecting gpg's error stream from /dev/null shows:

---
gpg: Signature made Wed 07 Nov 2018 21:03:27 UTC using RSA key ID 12BB1939
gpg: failed to create temporary file '/home/user/.gnupg/.#lk0x0000555f88533ca0.k3.1azy.net.30121': No such file or directory
gpg: Fatal: can't create lock for '/home/user/.gnupg/trustdb.gpg'
Invalid signature https://dlang.org/install.sh.sig
---

It looks like it needs ~/.gnupg to exist.

Creating the directory allows the installation script to proceed.
Comment 1 Vladimir Panteleev 2018-11-25 16:54:34 UTC 
https://github.com/dlang/installer/pull/352
Comment 2 github-bugzilla 2018-11-27 10:42:45 UTC 
Commits pushed to master at https://github.com/dlang/installer

https://github.com/dlang/installer/commit/ce7949408ac279c78ac765773b25b956785c8089
script/install.sh: Initialize GPG directory before invoking it

On some (older?) versions, --verify will fail if GNUPGHOME (~/.gnupg)
does not exist, even with --no-default-keyring, as that's where it
creates its temporary files.

Fixes issue 19434.

https://github.com/dlang/installer/commit/ce225047968cf9404eeafbf6f2a87975198c7483
Merge pull request #352 from CyberShadow/pull-20181125-164347

Fix Issue 19434 - "Invalid signature" when using install.sh with no ~/.gnupg