Hacker News Reader

Comment by jgrahamc | Hacker News Reader

That's Google logging stuff

That's not how Google tells it, if I'm reading this right:

Cloudflare explained that they pushed a change to production that logged malformed pages that were requested, and then sent me the list of URLs to double check.

Many of the logged urls contained query strings from https requests that I don't think they intended to share.

(I'm reading that as "intended to share with Google".)

Ah. I see what you mean. Apologies, kind of tired.

If Cloudflare accidentally leaked additional sensitive data to Tavis during the handling of this incident, and that data wasn't already compromised by the parser bug, then you should call that out in the incident report.

Understandably, I think. I can't imagine you've had much sleep this week.

Little

I'm sorry you (or anybody else) have to go through this.

Thanks.

FWIW, I admire you for how you're handling this, taking the grunt of the storm all by yourself and not throwing anyone under the bus. Tip of the hat to you and may better times lie ahead!

No one else's mistake other than ours.

This and the SHA1-pocalypse cannot have been a fun day.

Maybe time to consider one of the nap rooms?

I don't think that's the case: from my reading of the issue I understood that the urls with query params were sent from CF to Google for clearing from the google cache.

I read it as "sensitive query strings sent to Google by CloudFlare engineers".

Reply on news.ycombinator.com