public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: cygwin Digest 25 Jun 2018 00:46:06 -0000 Issue 10882 - virus alert
Date: Sat, 30 Jun 2018 20:47:00 -0000	[thread overview]
Message-ID: <c92c9d93-8504-ab68-83d0-0a45ba53a872@SystematicSw.ab.ca> (raw)
In-Reply-To: <2a0f4eac-9a37-0196-d072-4f5483557862@tiscali.co.uk>

On 2018-06-30 10:09, David Stacey wrote:
> On 30/06/18 13:19, Richard Watt wrote:
>> Did anyone else get a virus warning from the cygwin Digest 25 Jun 2018
>> 00:46:06 -0000 Issue 10882?
> It's an unsolicited invoice from someone you've never heard of. Of course it's
> malware :-)
> It's an attachment to this post [1], compressed with gzip. The compressed
> version passes through VirusTotal cleanly. If you unpack the file, though, you
> discover that it isn't a PDF at all (surprise, surprise) but a .NET executable.
> And quite a few anti-virus tools flag it as something unpleasant [2].

I get sourceware ezmlm bounce warnings, when my domain mail forwarder bounces
mail with malware, and I don't see most of the spam, as my personal ISP account
filter is configured to dump spam instead of flagging it.
I don't see a few announce posts, as some appear to get dumped by my ISP as
spam, and my mail client puts some other posts into my Junk folder.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2018-06-30 17:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-30 17:14 Richard Watt
2018-06-30 19:10 ` David Stacey
2018-06-30 20:47   ` Brian Inglis [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=c92c9d93-8504-ab68-83d0-0a45ba53a872@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).