From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13396] Mirai Virus ?
Date: Sun, 20 Dec 2020 09:54:44 +0000 [thread overview]
Message-ID: <bug-13396-163-GUM8oIgFVN@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13396-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=13396
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |uclibc-cvs at uclibc.org,
| |yann.morin.1998 at free.fr
Product|buildroot |uClibc
Component|Other |Other
Assignee|unassigned at buildroot.uclibc |unassigned at uclibc.org
|.org |
Resolution|--- |INVALID
Status|NEW |RESOLVED
--- Comment #2 from Yann E. MORIN <yann.morin.1998@free.fr> ---
First, uClibc has had no activity since 2015. It's dead and has been replaced
with uClibc-ng: https://uclibc-ng.org/. As such, any bug should probably
reported there now.
Second, 2015 was before the disclosure of Mirai, and the ldconfig code had
anyway not been touched since 2011.
Third, you are referencing a toolchain that was built in April 2009, more than
11 years ago now, so at least seven years before Mirai was discovered. I would
wager that this definitely predates Mirai.
I would believe that this is a false positive.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-12-20 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 14:38 [Buildroot] [Bug 13396] New: Mirai Virus ? bugzilla at busybox.net
2020-12-19 14:39 ` [Buildroot] [Bug 13396] " bugzilla at busybox.net
2020-12-20 9:54 ` bugzilla at busybox.net [this message]
2020-12-20 10:14 ` bugzilla at busybox.net
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=bug-13396-163-GUM8oIgFVN@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.