Remove ganking.club, jennig.es, gunfighterj.com, hogs.space, hogscollective.space

[joejenniges]

Remove ganking.club, jennig.es, gunfighterj.com, hogs.space, hogscollective.space

[TheReverend403]

This list is honestly the worst form of cancer I've personally ever seen on the internet. Guilty until proven innocent, except even when proven innocent, you're at the mercy of collaborators who clearly can't be bothered to even maintain their shitty list anymore.

…

On 13 March 2017 03:24:48 GMT+00:00, GunfighterJ ***@***.***> wrote: Any update? The proof is there, I would like my sites removed please.

[joejenniges]

I added my github profile to each text file. I don't see how this isn't proof enough, this is literally what keybase has you do.

[Phineas]

Do you have Keybase proof?

[Zenexer]

@Phineas I think those text files should be sufficient, no?

[coderobe]

@GunfighterJ No, keybase provides a cryptographic proof as well

[joejenniges]

Cryptographic proof of what?

[coderobe]

Although the domain(s) in question don't seem like something that needs extra validation, so i'd let it pass

[TheReverend403]

What do you need a cryptographic proof for? The domain itself links to his Github profile, it's not like that could happen if he didn't own it.

[coderobe]

@GunfighterJ Proof of ownership. The text files should be sufficient in your case though.

[joejenniges]

Any update? The proof is there, I would like my sites removed please.

[RhvsW]

:^)

[coderobe]

@TheReverend403 You should've read the ReadMe & the repo name. This is not a list of "hacked sites"™, it's a list of sites using Cloudflare during the affected time period.

[coderobe]

@GunfighterJ Can you post a PR addressing this issue? I'll merge it.

[RhvsW]

For a list of sites using Cloudflare during the time their nginx was affected there's a whole lot of incorrect entries :^)

[pirate]

@coderobe fyi text file is sufficient proof of ownership, and proof of ownership isn't needed for static sites (it's only for paper trail for large sites).

[pirate]

I'm closing this issue and others like it. The list is now archived an I'm not accepting any change requests. I know this comes as a surprise and may seem unfair but please consider the following:

• you can link concerned users directly to our README, which explicitly states the list contains many unaffected sites
• you can link users to several articles discussing how minor the leak's impact is
• our README clearly states the list is not for end-users, and is for technical analysis (the title is also changed from "affected sites" to "Cloudflare DNS users")
• I will be intentionally breaking search tools shortly by moving the txt file to a new location (no more browser extensions for searching the list)

If you have a specific objection or unrelated issue you want resolved, you can contact me via twitter DM. Thanks for your understanding.

[joejenniges]

Thank you. I can agree to this.