From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12746] New: "sysdig" package description points to http://sysdig.org, which bounces to malware site
Date: Fri, 03 Apr 2020 13:09:42 +0000 [thread overview]
Message-ID: <bug-12746-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12746
Bug ID: 12746
Summary: "sysdig" package description points to
http://sysdig.org, which bounces to malware site
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Outdated package
Assignee: unassigned at buildroot.uclibc.org
Reporter: griscom at suitable.com
CC: buildroot at uclibc.org
Target Milestone: ---
It isn't clear from the package description what the "sysdig" package is, so I
went to the url http://sysdig.org listed in the description. Unfortunately,
that shows a page with a "The domain sysdig.org may be for sale" header, and
then quickly bounces through several other domains, landing in a
probably-dangerous website offering a "security check":
"By clicking the button below you'll go through a standard security check,
after which you will be redirected to Chrome store and will be given the option
to install Secured Search extension. This extension will offer you a safer web
search experience by changing your default search provider."
At the least the bad URL should be removed; best would be to redirect it to an
available website that describes the package (or removal of the package
altogether).
ref: https://git.buildroot.net/buildroot/tree/package/sysdig/Config.in
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-04-03 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 13:09 bugzilla at busybox.net [this message]
2020-04-03 19:08 ` [Buildroot] [Bug 12746] "sysdig" package description points to http://sysdig.org, which bounces to malware site bugzilla at busybox.net
2020-04-04 13:26 ` 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-12746-163@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.