Void Linux discussion
 help / color / mirror / Atom feed
From: Jeff Pohlmeyer <yetanothergeek@gmail.com>
To: 0x40@keemail.me
Cc: voidlinux <voidlinux@googlegroups.com>
Subject: Re: Verify installation media
Date: Thu, 23 May 2019 04:39:50 -0500	[thread overview]
Message-ID: <CAEuRe+0EPj00SP5bPNcGiBqFuuYyK7c24RjhNYc8D5hbftxOgg@mail.gmail.com> (raw)
In-Reply-To: <LfYvL3L--3-1@keemail.me>

On Thu, May 23, 2019 at 4:02 AM <0x40@keemail.me> wrote:
> You verify the sha256sums.txt using the .sig file and a program called gnupg.

Hello, 0x40. Thank you for your response. I am aware of what gpg is
and how to use it. The point is that I cannot use the
20190217/sha256sums.txt.sig file because it does not exist.


> If you need a version newer than 20181111, probably because the kernel is ancient and likely won't boot/have working drivers for modern hardware, you can use the void-mklive script to create your own iso with all the latest packages from the repo.

Then what is the point of having the 20190217 images available for
download, if I cannot verify them? Seems like the fix would be quite
simple (just sign the file and upload the sig.)

 - Jeff

-- 
You received this message because you are subscribed to the Google Groups "voidlinux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to voidlinux+unsubscribe@googlegroups.com.
To post to this group, send email to voidlinux@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/CAEuRe%2B0EPj00SP5bPNcGiBqFuuYyK7c24RjhNYc8D5hbftxOgg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

      reply	other threads:[~2019-05-23  9:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23  6:07 Jeffrey Pohlmeyer
2019-05-23  9:02 ` 0x40
2019-05-23  9:39   ` Jeff Pohlmeyer [this message]

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=CAEuRe+0EPj00SP5bPNcGiBqFuuYyK7c24RjhNYc8D5hbftxOgg@mail.gmail.com \
    --to=yetanothergeek@gmail.com \
    --cc=0x40@keemail.me \
    --cc=voidlinux@googlegroups.com \
    /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).