public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Stephen Lyons <slysven@virginmedia.com>
To: cygwin@cygwin.com
Subject: Re: cygwin Digest 27 Mar 2018 08:53:38 -0000 Issue 10744
Date: Wed, 18 Apr 2018 01:15:00 -0000	[thread overview]
Message-ID: <d788ea8f-d05a-f06e-7b6a-343f8ccc64bc@virginmedia.com> (raw)
In-Reply-To: <1522140818.79007.ezmlm@cygwin.com>

On 27/03/2018 09:53, cygwin-digest-help@cygwin.com wrote:
> 
> cygwin Digest 27 Mar 2018 08:53:38 -0000 Issue 10744
> 
> Topics (messages 211932 through 211934):
> 
> Tarball from cygwin.com git tag
> 	211932 by: Wolfgang Stoeggl
> 	211933 by: Marco Atzeri
> 
> Re: Request for supply
> 	211934 by: Karen
> 
> Administrivia:
> 
> To subscribe to the digest, e-mail:
> 	cygwin-digest-subscribe@cygwin.com
> 
> To unsubscribe from the digest, e-mail:
> 	cygwin-digest-unsubscribe@cygwin.com
> 
> To post to the list, e-mail:
> 	cygwin@cygwin.com
> 
> 
> ----------------------------------------------------------------------
> 

For unusual reasons I was looking at my EMail on a Windows PC and it's
Anti-Virus (AVG Free) detected a Win32:Malware-gen infection in the file
Inquiry.exe inside Inquiry.gz inside the third message of this digest
(Issue: 10744) - given that that was a spam message anyhow, is such
*malicious* junk common in this mailing list?  Is it was just that I
happened to be using a vulnerable platform (i.e. Windows) whereas I
normally lurk from a *nix one that means I'm encountering something that
Windows/Cygwin users see frequently here?

Stephen



--
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-04-18  1:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1522140818.79007.ezmlm@cygwin.com>
2018-04-18  1:15 ` Stephen Lyons [this message]
2018-04-18  6:45   ` Marco Atzeri
2018-04-20 15:01     ` cyg Simple

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=d788ea8f-d05a-f06e-7b6a-343f8ccc64bc@virginmedia.com \
    --to=slysven@virginmedia.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).