From: Marco Atzeri <marco.atzeri@gmail.com>
To: Antonio Cesar Rosa <ancesar@gmail.com>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Cygwin setup error
Date: Tue, 21 Apr 2020 20:33:16 +0200 [thread overview]
Message-ID: <8d287574-f820-564b-4794-e35e3429174c@gmail.com> (raw)
In-Reply-To: <CAHCu2igRV=guUb2nNm1gDPxtxi9g_hqFo7RMh4xERveaNWjYqQ@mail.gmail.com>
Am 21.04.2020 um 18:08 schrieb Antonio Cesar Rosa:
> Hello,
>
> I do not think so. See the output from Virustotal:
>
> 2431de4597a2162f3e1d60af90f638b41677265b07cc66fcb0231fdde452c841
> setup-x86_64.exe 1.29 MB 2020-04-21 00:31:19 UTC
> Size
>
> 15 hours ago
> 64bits direct-cpu-clock-access overlay peexe runtime-modules
> DETECTION DETAILS BEHAVIOR COMMUNITY
> SecureAge APEX Malicious MaxSecure Trojan.Malware.300983.susgen
> Lastline MALWARE Acronis Undetected
>
>
> Regards,
> Cesar
>
>
please reply on mailing list in copy.
Virus Total with the URL https://cygwin.com/setup-x86_64.exe
gives all clean.
If you have a different result. likely you have a tampered file.
And using the signature available on
https://cygwin.com/install.html
we also have:
$ gpg2 --verify setup-x86_64.exe.sig
gpg: assuming signed data in 'setup-x86_64.exe'
gpg: Signature made Sat, Mar 21, 2020 6:35:25 PM CET
gpg: using DSA key 1169DF9F22734F743AA59232A9A262FF676041BA
gpg: checking the trustdb
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 1 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 1 signed: 0 trust: 1-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2022-02-26
gpg: Good signature from "Cygwin <cygwin@cygwin.com>" [ultimate]
gpg: Signature made Sat, Mar 21, 2020 6:35:25 PM CET
gpg: using RSA key 56405CF6FCC81574682A5D561A698DE9E2E56300
gpg: Good signature from "Cygwin <cygwin@cygwin.com>" [full]
next prev parent reply other threads:[~2020-04-21 18:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 15:29 Antonio Cesar Rosa
2020-04-21 15:53 ` Marco Atzeri
[not found] ` <CAHCu2igRV=guUb2nNm1gDPxtxi9g_hqFo7RMh4xERveaNWjYqQ@mail.gmail.com>
2020-04-21 18:33 ` Marco Atzeri [this message]
2020-04-21 22:07 ` Brian Inglis
-- strict thread matches above, loose matches on Subject: below --
2005-07-21 4:40 cygwin " "Dr. M. C. Nelson"
2005-07-21 5:18 ` Larry Hall
2005-07-21 4:28 "Dr. M. C. Nelson"
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=8d287574-f820-564b-4794-e35e3429174c@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=ancesar@gmail.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).