public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: marco atzeri <marco.atzeri@gmail.com>
To: happynumnums <happynumnums@proton.me>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Identical Cygwin websites - differing downloads
Date: Thu, 15 Jun 2023 17:07:51 +0200	[thread overview]
Message-ID: <CAB8Xom_+jYquqOfZr8k3hGPAHYUHesvy5uoyeS0JqLrMrFhieA@mail.gmail.com> (raw)
In-Reply-To: <-ZOAJV_uZC2NPx5GcZA8caT5sxCBmG7bp1eSMaG4JMS2jy343wOyf3KCgGSZDPajHSGNmdxcEm5My5l7SogATe_jn8BoRrENyp_YmVSXQgA=@proton.me>

On Thu, Jun 15, 2023 at 3:20 PM happynumnums via Cygwin
<cygwin@cygwin.com> wrote:
>
> When looking for the latest Cygwin installer, I came across two different domains.
>
> One insecure:
> http://cygwin.org/
>
> and one secure:
> https://cygwin.net/
>
> When checking the downloaded latest 3.4.6 installer with sha512sum.exe, I get differing checksums from the executables from both websites:
>
> an unexpected checksum (from first site)
> 787c46173f5f91d350d31053f09d2bc18e1a80907a9f571f905fa7579cd2fa7b2502337da57aa70a5c8c4209a365f3604cee3c8ffe6c451b397986ddf17eea14
>
> and the expected checksum from the 2nd site (as printed on both pages):
> 4779bead277ba7e682212ed3b1c9c2a56f9b15586dc2db3949556958b683b6f8a11c1c8957e1027d798281fcc98ccf12c418a609911c7e553787c88f8af86152
>
> The first file size shows 1350kB, the 2nd 1356kb.
>
> Can somebody clarify, if cygwin.org is a phishing site or otherwise explain the differences?
>
> Sent with [Proton Mail](https://proton.me/) secure email.
>

all sites point to the same address and all works with HTTPS
IPv4 address (8.43.85.97)

https://sitereport.netcraft.com/?url=https://cygwin.net

problem/cache in the middle ?

Regards
Marco

  reply	other threads:[~2023-06-15 15:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15 13:20 happynumnums
2023-06-15 15:07 ` marco atzeri [this message]
2023-06-15 17:01   ` Brian Inglis

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=CAB8Xom_+jYquqOfZr8k3hGPAHYUHesvy5uoyeS0JqLrMrFhieA@mail.gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=happynumnums@proton.me \
    /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).