public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Posting on RISKS - hacked NAS's
Date: Sun, 25 Sep 2016 22:33:59 +0100	[thread overview]
Message-ID: <57E842C7.9000302@youngman.org.uk> (raw)

Just for info. I know it's not really quite this list, but I can't quite
make out what is affected.

I get the impression this is referring to NAS systems, so it's outside
our remit. But to me, "Seagate NAS" is actually a raid-suitable disk
drive, so it makes me wonder whether it's hacked drive firmware...
unlikely but eminently possible ...

Cheers,
Wol

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

Date: Fri, 23 Sep 2016 11:34:21 -0700
From: Gene Wirchenko <genew@telus.net>
Subject: "Seagate NAS hack should scare us all" (Roger A. Grimes)

Roger A. Grimes, InfoWorld, 20 Sep 2016
An under-the-radar news story proves that computers are far from the only
devices prey to attack
http://www.infoworld.com/article/3121338/security/seagate-nas-hack-should-scare-us-all.html

opening text:

No fewer than 70 percent of Internet-connected Seagate NAS hard drives have
been compromised by a single malware program. That's a pretty startling
figure.  Security vendor Sophos says the bitcoin-mining malware Miner-C is
the culprit.

  [At peak, seek to tweak the weak link.  This reeks of leaks that peek as
  well.  PGN]

             reply	other threads:[~2016-09-25 21:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-25 21:33 Wols Lists [this message]
2016-09-25 23:40 ` Posting on RISKS - hacked NAS's Adam Goryachev
2016-09-26  2:35   ` Benjammin2068

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=57E842C7.9000302@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    /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