Skip to content

Missing signature for 2.8.0 releaseΒ #1410

Closed

Description

@atsampson

NUT tarball releases usually have a GPG signature so packagers can verify they're legitimate.

However, the 2.8.0 release doesn't seem to have one - the link on the download page is broken, and there's no file in the download directory.

Activity

  1. added
    CIEntries related to continuous integration infrastructure (here CI = tools + scripts + recipes)
    on May 10, 2022
  2. added this to the 2.8.1 milestone on May 10, 2022
  3. self-assigned this
    on May 10, 2022
  4. jimklimov commented on May 10, 2022

    @jimklimov
    Member

    Yes, that is now a "known oversight" since change of maintainer some time back; nobody in the current team has jumped through the loops recommended for a GPG key yet, and GitHub commit validation was deemed similar enough in practice when the ritual keys were handed over.

    But still, thanks for the reminder and I hope to get around to this. Got some reading to do first:

  5. atsampson commented on May 10, 2022

    @atsampson
    Author

    Great - thanks, Jim!

  6. jimklimov commented on May 31, 2023

    @jimklimov
    Member

    So... it took a while to get feet wet, but now I have a GPG key pushed out to some registries like openpgp, debian and ubuntu. Wondering what the next part is, if some distros or their keychains should include me in packages? Just spread the word on NUT website and in the NEWS file? :)

  7. jimklimov commented on May 31, 2023

    @jimklimov
    Member

    FWIW, my fancy new GPG key ID is below:

    $ gpg --recv-key DE0184DA7043DCF7
    gpg: key DE0184DA7043DCF7: public key "Jim Klimov (Doing FOSS since last millennium) <jimklimov@gmail.com>" imported
    gpg: Total number processed: 1
    gpg:               imported: 1
    
  8. jimklimov commented on May 31, 2023

    @jimklimov
    Member

    Tagged https://github.com/networkupstools/nut/releases/tag/v2.8.0-signed and posted the signature file (nut-website "source" repo and github release attachment).

  9. jimklimov commented on Jun 1, 2023

    @jimklimov
    Member
  10. jimklimov commented on Jun 1, 2023

    @jimklimov
    Member

    SIG file finally got made and published, this issue is resolved :)

    (There is another related issue of Download page offering a non-release tag currently; however it is possible to get through the "You can also browse the stable source directory" link for verification).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

CIEntries related to continuous integration infrastructure (here CI = tools + scripts + recipes)GPG/PGP/GnuPGKnow-how about use of signing

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions