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

Update: ZipRecruiter.com (used proxy) #145

Closed
wants to merge 1 commit into from
Closed

Conversation

zostay
Copy link
Contributor

@zostay zostay commented Feb 24, 2017

We are not impacted by this incident according to them.

Before submitting your pull-request:

  • name of the pull request should be "Add: domain, domain, domain (proxy + DNS)" or "Remove: domain (static), domain (DNS only), domain (static)"
  • do not ask for removal of actually affected websites (any websites using cloudflare reverse proxy)

HOW TO REMOVE YOUR SITE

  1. verify the site is static and contains no user data (I will remove it immediately once I confirm)

OR

  1. Verify ownership, send me an email from @yourdomain.com, post a random nonce on the domain, or provide keybase proof
  2. Verify you did not use the Cloudflare proxy service during the affected period

We are not impacted by this incident according to them.
@zostay
Copy link
Contributor Author

zostay commented Feb 24, 2017

I sent email to the email address listed on your gh profile just now.

@coderobe
Copy link
Contributor

coderobe commented Feb 24, 2017

The mail you've got likely only indicates that no leaked info was found in publicly indexed cached leaks. Your data could've still gotten leaked somewhere.

@pirate pirate changed the title ZipRecruiter.com was notified by CloudFlare Update: ZipRecruiter.com (used proxy) Feb 24, 2017
@coderobe
Copy link
Contributor

Please see #127 (comment) and #87 (comment) for additional information.

@pirate
Copy link
Owner

pirate commented Feb 24, 2017

Closing as you guys are on the server:cloudflare-nginx proxy, possibly affected. You're welcome to submit a PR with a blog post to link to from the README.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants