Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.misc > #13236 > unrolled thread

Cloudbleed

Started byRS Wood <rsw@therandymon.com>
First post2017-03-02 03:11 +0000
Last post2017-03-02 03:11 +0000
Articles 1 — 1 participant

Back to article view | Back to comp.misc


Contents

  Cloudbleed RS Wood  <rsw@therandymon.com> - 2017-03-02 03:11 +0000

#13236 — Cloudbleed

FromRS Wood <rsw@therandymon.com>
Date2017-03-02 03:11 +0000
SubjectCloudbleed
Message-ID<14fkod-rv3.ln1@raspberry.therandymon.com>
From the «hell of a name there, gents» department:
Title: Ask Slashdot: How Are You Responding To Cloudbleed?
Author: help@slashdot.org
Date: Sat, 25 Feb 2017 19:34:00 -0500
Link: http://rss.slashdot.org/~r/Slashdot/slashdot/~3/-z2n9OnMRck/ask-slashdot-how-are-you-responding-to-cloudbleed

An anonymous IT geek writes: Cloudflare-hosted web sites have been leaking data
as far back as September, according to Gizmodo, which reports that at least
Cloudflare "acted fast" when the leak was discovered, closing the hole within
44 minutes, and working with search engines to purge their caches. (Though
apparently some of it is still lingering...) Cloudflare CEO Matthew Prince
"claims that there was no detectable uptick in requests to Cloudflare-powered
websites from September of last year...until today. That means the company is
fairly confident hackers didn't discover the vulnerability before Google's
researchers did." And the company's CTO also told Reuters that "We've seen
absolutely no evidence that this has been exploited. It's very unlikely that
someone has got this information... We do not know of anybody who has had a
security problem as a result of this." Nevertheless, Fortune warns that "So
many sites were vulnerable that it doesn't make sense to review the list and
change passwords on a case-by-case basis." Some sites are now even resetting
every user's password as a precaution, while site operators "are also being
advised to wipe their sites' cookies and security certificates, and perform
their own web searches to see if site data leaked." But I'd like to know what
security precautions are being taken by Slashdot's readers? Leave your own
answers in the comments. How did you respond to Cloudbleed?

[image 2][2][image 4][4][image 6][6]

Read more of this story[7] at Slashdot.
[image 8]

Links:
[1]: http://twitter.com/home?status=Ask+Slashdot%3A+How+Are+You+Responding+To+Cloudbleed%3F%3A+http%3A%2F%2Fbit.ly%2F2lHUH94 (link)
[2]: https://a.fsdn.com/sd/twitter_icon_large.png (image)
[3]: http://www.facebook.com/sharer.php?u=https%3A%2F%2Fask.slashdot.org%2Fstory%2F17%2F02%2F25%2F2011249%2Fask-slashdot-how-are-you-responding-to-cloudbleed%3Futm_source%3Dslashdot%26utm_medium%3Dfacebook (link)
[4]: https://a.fsdn.com/sd/facebook_icon_large.png (image)
[5]: http://plus.google.com/share?url=https://ask.slashdot.org/story/17/02/25/2011249/ask-slashdot-how-are-you-responding-to-cloudbleed?utm_source=slashdot&utm_medium=googleplus (link)
[6]: http://www.gstatic.com/images/icons/gplus-16.png (image)
[7]: https://ask.slashdot.org/story/17/02/25/2011249/ask-slashdot-how-are-you-responding-to-cloudbleed?utm_source=rss1.0moreanon&utm_medium=feed (link)
[8]: http://feeds.feedburner.com/~r/Slashdot/slashdot/~4/-z2n9OnMRck (image)

[toc] | [standalone]


Back to top | Article view | comp.misc


csiph-web