Skip to content
This repository has been archived by the owner on Jan 18, 2018. It is now read-only.

Change "not affected"/"no evidence of compromised data"; clarify meaning #153

Closed
Zenexer opened this issue Feb 25, 2017 · 6 comments
Closed
Assignees
Labels

Comments

@Zenexer
Copy link
Contributor

Zenexer commented Feb 25, 2017

This note that we've added in parentheses next to some domains is inaccurate. Even where it says "no evidence of compromised data", it's quite misleading. We should change these to say something along the lines of "public statement" or "doesn't appear in Google cache".

@pirate
Copy link
Owner

pirate commented Feb 25, 2017

Yeah I like "doesn't appear in search engine caches". We should edit them manually, some sites actually have no compromised data, such as 1password.

@Zenexer
Copy link
Contributor Author

Zenexer commented Feb 25, 2017

From what was said on IRC, I don't think "doesn't appear in search engine caches" would be wise/accurate, either. Cloudflare's messages to customers have only mentioned Google, and allegedly other caching/archiving services have retained information that Google never had (which makes sense).

@pirate
Copy link
Owner

pirate commented Feb 25, 2017

AFAIK from twitter posts they were working with bing, yahoo, and duckduckgo as well, but not 100% that they're all cleared at once.

@Zenexer
Copy link
Contributor Author

Zenexer commented Feb 25, 2017

Then "several major search engines" might be appropriate, but there's still a difference between clearing caches and querying for leaked data. We also haven't heard anything about Baidu or Yandex.

@Zenexer Zenexer changed the title Change "not affected"; clarify meaning Change "not affected"/"no evidence of compromised data"; clarify meaning Feb 25, 2017
@Zenexer
Copy link
Contributor Author

Zenexer commented Feb 25, 2017

Any objections to this?

no leaked data found in several search engine caches

@ddymko
Copy link
Contributor

ddymko commented Feb 25, 2017

I missed this thread @Zenexer - I will update the digital ocean pr to reflect the the more appropriate message

Zenexer added a commit to Zenexer/sites-using-cloudflare that referenced this issue Feb 25, 2017
@Zenexer Zenexer closed this as completed Feb 25, 2017
pirate added a commit that referenced this issue Feb 25, 2017
Fixes #153: "not compromised" replaced with more accurate note
@ddymko ddymko mentioned this issue Feb 25, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants