public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Bob" <bob@denova.com>
To: cygwin@cygwin.com
Subject: Fix to help novice users verify cygwin.com downloads
Date: Tue,  2 Mar 2021 18:41:09 GMT	[thread overview]
Message-ID: <20210302184109hPtNY09mt9@denova.com> (raw)


Hey 

I was searching for some articles about verifying files today and I
came across this page: Cygwin FAQ (http://www.cygwin.com/faq.html)
on your site.

I noticed you recommend very thorough verification, using hashes and sigs.

But usually the data file is downloaded much more than the hash or sig
files. Users often don't verify.

Just wanted to give you a heads up that we created a free open source
program that both downloads and verifies in one step. So your users always verify.

It's like "Cygwin FAQ", but it's a single command that downloads
and verifies thoroughly:

https://denova.com/open/safeget/developer/ 

Might be worth a mention on your page.

Either way, keep up the awesome work!

Cheers,

Bob

P.S. The best way to make sure downloaders verify files is to give them
one command that downloads and verifies in one step. There's a free open
source solution.

                 reply	other threads:[~2021-03-02 18:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210302184109hPtNY09mt9@denova.com \
    --to=bob@denova.com \
    --cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).