Thread overview
[Issue 19100] install.sh signature verification fails, no public key
Jul 19, 2018
Seb
Aug 10, 2018
Jonathan Marler
Aug 10, 2018
Seb
Aug 13, 2018
Jonathan Marler
Aug 13, 2018
Seb
Aug 13, 2018
Seb
Nov 25, 2018
Vladimir Panteleev
July 19, 2018
https://issues.dlang.org/show_bug.cgi?id=19100

Seb <greensunny12@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |greensunny12@gmail.com

--- Comment #1 from Seb <greensunny12@gmail.com> ---
Did you upgrade the keyring or install.sh within the last year?
We upgraded the keyring in January this year and you might still have an old
one.

--
August 10, 2018
https://issues.dlang.org/show_bug.cgi?id=19100

--- Comment #2 from Jonathan Marler <johnnymarler@gmail.com> ---
Saw a post on the forum that someone else had this issue.

To answer sebs question, I'm not familiar with ubuntu's "keyring".  This happened on a new machine that I had just inatlled Ubuntu 16.04 LTS on.  And install.sh was also brand new downloaded from the side.

--
August 10, 2018
https://issues.dlang.org/show_bug.cgi?id=19100

--- Comment #3 from Seb <greensunny12@gmail.com> ---
> To answer sebs question, I'm not familiar with ubuntu's "keyring"

And you don't need to. We don't use it. We ship our own keyring on the initial download, which is at ~/dlang/d-keyring.gpg

You can do the following to check the current keyring:

> gpg --no-default-keyring --keyring ~/dlang/d-keyring.gpg --list-keys

You should see a similar output as on https://dlang.org/gpg_keys.html Also:

> sha256sum ~/dlang/d-keyring.gpg
4de1bb6028bb1e3d4eefd9e1a1651ad6c372ead0482b63e3aafdfdc0fbb48dbd /home/seb/dlang/d-keyring.gpg

Are you still experiencing this issue?

--
August 13, 2018
https://issues.dlang.org/show_bug.cgi?id=19100

--- Comment #4 from Jonathan Marler <johnnymarler@gmail.com> ---
Seb has fix here: https://github.com/dlang/installer/pull/338

--
August 13, 2018
https://issues.dlang.org/show_bug.cgi?id=19100

--- Comment #5 from Seb <greensunny12@gmail.com> ---
After debugging this for a while with Jonathan, the problem seemed to be that the install.sh script was manually installed to ~/dlang/install.sh and the check for a keyring upgrade only checks for the existence of ~/dlang/install.sh and not ~/dlang/d-keyring.gpg

Also, gpg seems to create a default keyring with 32B if no keyring exists (i.e. the passed file doesn't exist).

A fix:

https://github.com/dlang/installer/pull/338

--
August 13, 2018
https://issues.dlang.org/show_bug.cgi?id=19100

Seb <greensunny12@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Hardware|x86                         |All
                 OS|Windows                     |All
           Severity|enhancement                 |major

--
August 13, 2018
https://issues.dlang.org/show_bug.cgi?id=19100

--- Comment #6 from github-bugzilla@puremagic.com ---
Commit pushed to master at https://github.com/dlang/installer

https://github.com/dlang/installer/commit/bae1b3480a51991a0d014d4232102ee990c8ba3a Fix Issue 19100 - install.sh signature verification fails, no public key

--
August 13, 2018
https://issues.dlang.org/show_bug.cgi?id=19100

github-bugzilla@puremagic.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--
November 25, 2018
https://issues.dlang.org/show_bug.cgi?id=19100

Vladimir Panteleev <dlang-bugzilla@thecybershadow.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://issues.dlang.org/sh
                   |                            |ow_bug.cgi?id=19434

--