Show HN: Check your Safari history for sites using Cloudflare
1–9 of 9 posts
Re: Show HN: Check your Safari history for sites using Cloudflare
#2haven't looked through the code yet, but does this port to chrome?
Re: Show HN: Check your Safari history for sites using Cloudflare
#3haven't looked through the code yet, but does this port to chrome?
Just ported it for Chrome and Firefox. Maybe the title should be updated to reflect that change. There might be extensions for this already which could be more convenient.
Re: Show HN: Check your Safari history for sites using Cloudflare
#4Title should be changed to "Check your Browser history" - since there is also a Chrome / Firefox version.
Re: Show HN: Check your Safari history for sites using Cloudflare
#5It might've been better if it was multithreaded or something similar. It added 4287583 domains from sorted_unique_cf.txt. That'd take awhile.
Re: Show HN: Check your Safari history for sites using Cloudflare
#6It might've been better if it was multithreaded or something similar. It added 4287583 domains from sorted_unique_cf.txt. That'd take awhile.
It took 5 seconds for me, returning 285 matches, for Firefox on Linux.
Re: Show HN: Check your Safari history for sites using Cloudflare
#7Title should be changed to "Check your Browser history" - since there is also a Chrome / Firefox version.
I think the other browsers were added after the fact.
Re: Show HN: Check your Safari history for sites using Cloudflare
#8I built a chrome extension for same - https://github.com/avinassh/history-bleed/
Web store link - https://chrome.google.com/webstore/detail/history-bleed/jpkh...
Re: Show HN: Check your Safari history for sites using Cloudflare
#9As the author of the list these extensions are using (sites-using-cloudflare), I have doubts about the utility of public browser extensions to check for Cloudflare sites. An extension will alert if the user is on any of 4,000,000+ domains in the list. There will be too many false positives to make it a useful tool, and by forcing users to reset so many passwords, we're more likely to make them choose poor ones. That risk may outweight the safety gained by resetting passwords.
It was also mentioned in the Techcrunch article, many companies will probably choose not to reset user passwords, and will instead just pay for insurance to cover the tiny chance that one of their users had data leaked. https://techcrunch.com/2017/02/24/how-to-secure-your-data-af...