Send MinGW-Notify mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.osdn.me/mailman/listinfo/mingw-notify
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of MinGW-Notify digest..."


Please do not reply to this notification; the sender address is unable to 
accept incoming e-mail.  If you wish to unsubscribe you can do so at 
https://lists.osdn.me/mailman/listinfo/mingw-notify.



Today's Topics:

   1. [mingw] #40451: Virus Reported by Avast and Others in
      compiled code (MinGW Notification List)
   2. [mingw] #40438: Bug in libmingwex-5.3.1 dll
      (MinGW Notification List)
   3. [mingw] #40451: Virus Reported by Avast and Others in
      compiled code (MinGW Notification List)
   4. [mingw] #40438: Bug in libmingwex-5.3.1 dll
      (MinGW Notification List)


----------------------------------------------------------------------

Message: 1
Date: Sat, 30 May 2020 11:40:23 +0100
From: MinGW Notification List <[email protected]>
To: OSDN Ticket System <[email protected]>
Subject: [MinGW-Notify] [mingw] #40451: Virus Reported by Avast and
        Others in compiled code
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset=UTF-8

#40451: Virus Reported by Avast and Others in compiled code

  Open Date: 2020-05-30 03:49
Last Update: 2020-05-30 11:40

URL for this Ticket:
    https://osdn.net//projects/mingw/ticket/40451
RSS feed for this Ticket:
    https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=40451

---------------------------------------------------------------------

Last Changes/Comment on this Ticket:
2020-05-30 11:40 Updated by: keith
 * Status Update from Open to Closed

 * Resolution Update from None to Rejected

 * Priority Update from 7 to 1 - Lowest


Comment:

    This problem must be fixed ASAP!

Nope. You must prove, with near 100% certainty, that it is not a false
positive. Right now, you are yelling "trojan", but offer me only 43% confidence
in your assessment — and you aren't even prepared to assert that every one of
the potential false positives relates to identically the same trojan; couple
that with my 0% confidence in any antivirus product — especially any which is
commercially motivated to exploit the naïve — and I must do no more treat this
report with the contempt which any such knee-jerk reaction deserves. It's
entirely your choice how you wish to proceed, but we we are under no obligation
to do anything here.



---------------------------------------------------------------------
Ticket Status:

      Reporter: henrymwalker
         Owner: (None)
          Type: Issues
        Status: Closed
      Priority: 1 - Lowest
     MileStone: (None)
     Component: (None)
      Severity: 5 - Medium
    Resolution: Rejected
---------------------------------------------------------------------

Ticket details:

When I downloaded MinGW to my new HP laptop running Windows 10, I complied a
2-line Hello World program in C with gcc. Avast reported a Win32:TrojanX-gen
virus. Going to virustotal.com, 31 of 72 antivirus products reported a virus or
similar. Clearly, the problem could not be in my 2-line program, so it must be
in a library.

This problem must be fixed ASAP!

Thank you.



-- 
Ticket information of MinGW - Minimalist GNU for Windows project
MinGW - Minimalist GNU for Windows Project is hosted on OSDN

Project URL: https://osdn.net/projects/mingw/
OSDN: https://osdn.net

URL for this Ticket:
    https://osdn.net/projects/mingw/ticket/40451
RSS feed for this Ticket:
    https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=40451


------------------------------

Message: 2
Date: Sun, 31 May 2020 00:44:50 +0900
From: MinGW Notification List <[email protected]>
To: OSDN Ticket System <[email protected]>
Subject: [MinGW-Notify] [mingw] #40438: Bug in libmingwex-5.3.1 dll
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset=UTF-8

#40438: Bug in libmingwex-5.3.1 dll

  Open Date: 2020-05-23 18:07
Last Update: 2020-05-31 00:44

URL for this Ticket:
    https://osdn.net//projects/mingw/ticket/40438
RSS feed for this Ticket:
    https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=40438

---------------------------------------------------------------------

Last Changes/Comment on this Ticket:
2020-05-31 00:44 Updated by: rosasmje

Comment:

Reply To keith

    Should be fixed, in wsl-5.3.2. Dependent applications should be relinked,
    with updated libraries.

OK, I updated from installer to 5.3.2. mingwex-3.dll has no problems. this
compiles good with linked dll: gcc -fopenmp omp_hello.c -o omp_hello But now,
with -static addition, compiling fails

f:/mingw/bin/../lib/gcc/mingw32/9.2.0/../../../../mingw32/bin/ld.exe: f:/mingw/
bin/../lib/gcc/mingw32/9.2.0/../../..\libmingwex.a(codeset.o):(.text+0x143):
undefined reference to GetCPInfo@8'

does mingw needs full reinstall to fix this error?



---------------------------------------------------------------------
Ticket Status:

      Reporter: rosasmje
         Owner: keith
          Type: Issues
        Status: Closed
      Priority: 2
     MileStone: (None)
     Component: WSL
      Severity: 5 - Medium
    Resolution: Fixed
---------------------------------------------------------------------

Ticket details:

libmingwex-5.3.1 is BUGGY! it imports from self procedure
"__emutls_get_address", while not exporting it. thus any linked app would not
start. changed to --static also submitted this as review. also tested Version
5.2.2, it is good; it has not any "__emutls_get_address" inside;



-- 
Ticket information of MinGW - Minimalist GNU for Windows project
MinGW - Minimalist GNU for Windows Project is hosted on OSDN

Project URL: https://osdn.net/projects/mingw/
OSDN: https://osdn.net

URL for this Ticket:
    https://osdn.net/projects/mingw/ticket/40438
RSS feed for this Ticket:
    https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=40438


------------------------------

Message: 3
Date: Sun, 31 May 2020 04:51:43 +0900
From: MinGW Notification List <[email protected]>
To: OSDN Ticket System <[email protected]>
Subject: [MinGW-Notify] [mingw] #40451: Virus Reported by Avast and
        Others in compiled code
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset=UTF-8

#40451: Virus Reported by Avast and Others in compiled code

  Open Date: 2020-05-30 11:49
Last Update: 2020-05-31 04:51

URL for this Ticket:
    https://osdn.net//projects/mingw/ticket/40451
RSS feed for this Ticket:
    https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=40451

---------------------------------------------------------------------

Last Changes/Comment on this Ticket:
2020-05-31 04:51 Updated by: henry_walker

Comment:

You claim this is likely a false positive, and of course that may be true---but
it also may not be. In the past, my experience has been that reports of a virus
being present are true---but mostly I work on a Mac platform---I'm new to
Windows 10.

How would you propose determining this is a false positive? Guidance would be
appreciated, as I certainly will not run code that has a moderate chance of
being unsafe.

I look forward to constructive suggestions.



---------------------------------------------------------------------
Ticket Status:

      Reporter: henrymwalker
         Owner: (None)
          Type: Issues
        Status: Closed
      Priority: 1 - Lowest
     MileStone: (None)
     Component: (None)
      Severity: 5 - Medium
    Resolution: Rejected
---------------------------------------------------------------------

Ticket details:

When I downloaded MinGW to my new HP laptop running Windows 10, I complied a
2-line Hello World program in C with gcc. Avast reported a Win32:TrojanX-gen
virus. Going to virustotal.com, 31 of 72 antivirus products reported a virus or
similar. Clearly, the problem could not be in my 2-line program, so it must be
in a library.

This problem must be fixed ASAP!

Thank you.



-- 
Ticket information of MinGW - Minimalist GNU for Windows project
MinGW - Minimalist GNU for Windows Project is hosted on OSDN

Project URL: https://osdn.net/projects/mingw/
OSDN: https://osdn.net

URL for this Ticket:
    https://osdn.net/projects/mingw/ticket/40451
RSS feed for this Ticket:
    https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=40451


------------------------------

Message: 4
Date: Sat, 30 May 2020 22:20:32 +0100
From: MinGW Notification List <[email protected]>
To: OSDN Ticket System <[email protected]>
Subject: [MinGW-Notify] [mingw] #40438: Bug in libmingwex-5.3.1 dll
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset=UTF-8

#40438: Bug in libmingwex-5.3.1 dll

  Open Date: 2020-05-23 10:07
Last Update: 2020-05-30 22:20

URL for this Ticket:
    https://osdn.net//projects/mingw/ticket/40438
RSS feed for this Ticket:
    https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=40438

---------------------------------------------------------------------

Last Changes/Comment on this Ticket:
2020-05-30 22:20 Updated by: keith

Comment:

    does mingw needs full reinstall to fix this error?

No, it is a separate issue, (which unfortunately, arises due to the resolution
of this one). I didn't notice it, because once libmingwex.dll.a is installed
into GCC's library path, it does seem to arise only when -static is explicitly
specified, and that's not something I do routinely. However, if
libmingw32ex.dll.a is not installed, it may become problematic anyway.

The final solution seems to be to add an extra scan of -lmingw32 -lmingwex into
the GCC *libgcc spec sequence. Unfortunately, that requires a GCC rebuild, to
fix properly, and that isn't a quick fix. As an interim workaround, assuming
that you are using GCC-9.2.0, and that you don't already have a custom GCC
specs file, you may drop the attached modified GCC-9.2.0 specs file into
$MINGW_ROOT/lib/gcc/mingw32/9.2.0/. (If you already have a customized specs
file, you will need to edit it, to add the additional -lmingw32 -lmingwex
references into the *libgcc specs string. In any case, you will need to adjust
$MINGW_ROOT to match whatever drive and directory prefix you've used for your
MinGW installation).



---------------------------------------------------------------------
Ticket Status:

      Reporter: rosasmje
         Owner: keith
          Type: Issues
        Status: Closed
      Priority: 2
     MileStone: (None)
     Component: WSL
      Severity: 5 - Medium
    Resolution: Fixed
---------------------------------------------------------------------

Ticket details:

libmingwex-5.3.1 is BUGGY! it imports from self procedure
"__emutls_get_address", while not exporting it. thus any linked app would not
start. changed to --static also submitted this as review. also tested Version
5.2.2, it is good; it has not any "__emutls_get_address" inside;



-- 
Ticket information of MinGW - Minimalist GNU for Windows project
MinGW - Minimalist GNU for Windows Project is hosted on OSDN

Project URL: https://osdn.net/projects/mingw/
OSDN: https://osdn.net

URL for this Ticket:
    https://osdn.net/projects/mingw/ticket/40438
RSS feed for this Ticket:
    https://osdn.net/ticket/ticket_rss.php?group_id=3917&tid=40438


------------------------------

Subject: Digest Footer

_______________________________________________
MinGW-Notify mailing list
[email protected]
https://lists.osdn.me/mailman/listinfo/mingw-notify


------------------------------

End of MinGW-Notify Digest, Vol 32, Issue 11
********************************************

Reply via email to