Github messages for voidlinux
 help / color / mirror / Atom feed
From: thehornydragon <thehornydragon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Image not authentic
Date: Mon, 12 Apr 2021 10:39:38 +0200	[thread overview]
Message-ID: <20210412083938.tN9mhKbguWIinXR3fsbwmhFGJLTujFX9oSgJbf8CWlU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30174@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]

Closed issue by thehornydragon on void-packages repository

https://github.com/void-linux/void-packages/issues/30174

Description:
Hello,

I've just downloaded void-live-x86_64-20210218-xfce.iso, and have gone through the following steps as recommended on the download page:

Downloaded the sha256sum.sig, sha256sum.txt, and the void-release-20210218.pub files for verification.

Installed the signifiy-openbsd package (on Ubuntu 20.04 LTS, from the default repository).

Ran the following command: signify-openbsd -C -p ./void-release-20210218.pub -x ./sha256sum.sig ./void-live-x86_64-20210218-xfce.iso

Expected outcome: Signature Verified
./void-live-x86_64-20210218-xfce.iso: OK

Actual outcome: Signature Verified
./void-live-x86_64-20210218-xfce.iso: FAIL

sha256sum.sig/.txt were downloaded from here: https://alpha.de.repo.voidlinux.org/live/current/

void-release-20210218.pub was downloaded from here:
https://raw.githubusercontent.com/void-linux/void-packages/master/srcpkgs/void-release-keys/files/void-release-20210218.pub

  parent reply	other threads:[~2021-04-12  8:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12  2:40 [ISSUE] " thehornydragon
2021-04-12  2:57 ` thehornydragon
2021-04-12  8:39 ` thehornydragon [this message]
2021-04-12 12:38 ` ericonr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210412083938.tN9mhKbguWIinXR3fsbwmhFGJLTujFX9oSgJbf8CWlU@z \
    --to=thehornydragon@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).