News for hackers. Stuff that matters.
Re:Google Exposed User Data, Feared Repercussions of Disclos... by Bhilai on Monday October 08, 2018 @05:31PM (#18171500)
>We made Google+ with privacy in mind and therefore keep this API’s log data for only two weeks. That means we cannot confirm which users were impacted by this bug.

Wait, so they only keep two weeks worth of logs and within these logs they did not find anyone abusing this flaw. How can they be certain for any time period from two week prior ?

Re:Google Exposed User Data, Feared Repercussions of Disclos... by ismail on Monday October 08, 2018 @05:54PM (#18171655)
Wow. “We made Google+ with privacy in mind and therefore keep this API’s log data for only two weeks.”

The wording of this is really pushing the boundary of plausibility.

I fail to understand the logic of how this would protect privacy? Access logs with no profile data logged would not compromise privacy would it?

Can anyone confirm the timing of the google blog post? It seems the WSJ article was posted at a similar time.

This leads me to believe that the most likely reason we are hearing about this now is due to comment requests from the WSJ. WHEN Goog realised it was out they published.

Goog is trying to avoid using the words Data breach as they may get into hot water in EU.

Love how it is buried in the article.

My guess is a similar thing has been happening with android permissions. Data has been leaking through that they have just not admitted to it.

Re:Google Exposed User Data, Feared Repercussions of Disclos... by advisedwang on Monday October 08, 2018 @06:05PM (#18171735)
> Access logs with no profile data logged would not compromise privacy would it?

True, but access logs without profile data would prevent you know _which_ profiles were accessed. This matches with the actual claim in the article that they would be "unable to determine which users were affected"

Re:Google Exposed User Data, Feared Repercussions of Disclos... by mashlol on Monday October 08, 2018 @06:33PM (#18171901)
Right, but the only "profile data" they would need to add to the logs to know, would be a user ID. Not really any private info.
Re:Google Exposed User Data, Feared Repercussions of Disclos... by halflings on Monday October 08, 2018 @08:24PM (#18172415)
User IDs are definitely private info, since they'd allow you to follow a user's behaviour etc.
Re:Google Exposed User Data, Feared Repercussions of Disclos... by flukus on Monday October 08, 2018 @08:55PM (#18172557)
"user 1234567 viewed post 89564385943"

I can see how that's private info, but would this be:

"client x viewed user 1234567's profile"

Re:Google Exposed User Data, Feared Repercussions of Disclos... by gdfasfklshg4 on Tuesday October 09, 2018 @04:01AM (#18174095)
If the user id can be joined with other data to give a name or similar then it is considered personally identifying in terms of GDPR.

I am not a lawyer. You should hire an appropriately qualified lawyer to review your data hygiene practices.

Re:Google Exposed User Data, Feared Repercussions of Disclos... by saagarjha on Monday October 08, 2018 @10:02PM (#18172807)
Sure, if user 1234567 isn’t particularly popular.
Re:Google Exposed User Data, Feared Repercussions of Disclos... by wolco on Monday October 08, 2018 @09:52PM (#18172775)
Neither are private info. Private in theop law sense.
Re:Google Exposed User Data, Feared Repercussions of Disclos... by masonic on Tuesday October 09, 2018 @09:04PM (#18181138)

  The wording of this is really pushing the boundary of plausibility.
Maybe Google is running short of disk space.
Re:Google Exposed User Data, Feared Repercussions of Disclos... by MertsA on Tuesday October 09, 2018 @10:03AM (#18176037)
>Goog is trying to avoid using the words Data breach as they may get into hot water in EU.

As far as GDPR goes technically this breach happened right before they would have faced large repercussions from it.

Re:Google Exposed User Data, Feared Repercussions of Disclos... by sipos on Monday October 15, 2018 @10:20AM (#18219878)
It sounds like it came up as a result of their Project Strobe audit. I would guess they launched this project precisely because the penalties were about to get bigger and they knew they had skeletons.
Re:Google Exposed User Data, Feared Repercussions of Disclos... by skbly7 on Monday October 08, 2018 @06:28PM (#18171868)
The company which consider every single bit of data as "gold" decided not to keep their API's access log > 2 weeks? wow!
Re:Google Exposed User Data, Feared Repercussions of Disclos... by shpx on Monday October 08, 2018 @10:18PM (#18172874)
Is it possible that your impression of the company is (was?) off?

I'm not surprised. They (claim to) do something similar with the logs of their DNS service: two weeks of anonymized logs after which they "randomly sample a small subset for permanent storage".

https://developers.google.com/speed/public-dns/privacy

Re:Google Exposed User Data, Feared Repercussions of Disclos... by lucb1e on Tuesday October 09, 2018 @02:16AM (#18173692)
I had the same reaction so this indeed hints at that I've got wrong expectations. One plus point for privacy, one minus point for handling a beach so badly.
Re:Google Exposed User Data, Feared Repercussions of Disclos... by pinewurst on Monday October 08, 2018 @08:28PM (#18172435)
It's not like they don't have the storage space for more. Heck, the full logs for all Google+ usage probably fit on a USB stick. :)
Re:Google Exposed User Data, Feared Repercussions of Disclos... by throwawaygoog on Monday October 08, 2018 @11:41PM (#18173163)
Our default policy is to keep generic RPC server logs for O(weeks). It's best practice as we log a lot of structured data that can be large -- especially at our QPS. Furthermore, we have data retention timelines to keep.
Re:Google Exposed User Data, Feared Repercussions of Disclos... by Jerry2 on Monday October 08, 2018 @11:44PM (#18173171)
>Our default policy is to keep generic RPC server logs for O(weeks).

Out of curiosity, when was this policy adopted? After these security holes were discovered?

Re:Google Exposed User Data, Feared Repercussions of Disclos... by Buge on Tuesday October 09, 2018 @12:51AM (#18173416)
Doesn't the statement "That means we cannot confirm which users were impacted by this bug" indicate it was adopted before the hole was discovered?
Re:Google Exposed User Data, Feared Repercussions of Disclos... by nil_pointer on Monday October 08, 2018 @07:02PM (#18172066)
I too find Google only keeping 2 weeks of logs unbelievable.
Re:Google Exposed User Data, Feared Repercussions of Disclos... by puzzle on Monday October 08, 2018 @08:50PM (#18172536)
You might find it surprising, but at Google it's common to do things like not returning anything when aggregating data from a small number of users. That's before even looking at projects like RAPPOR or ESA. Source: I had access to sensitive data many years ago.
Re:Google Exposed User Data, Feared Repercussions of Disclos... by vkou on Monday October 08, 2018 @07:38PM (#18172227)
The regulatory costs of GDPR mean that for every piece of log data, you want to think about whether or not you really want to keep it.

If you don't have a good business case for keeping it, you're often better off erring on the side of deletion.

Re:Google Exposed User Data, Feared Repercussions of Disclos... by p49k on Monday October 08, 2018 @08:01PM (#18172331)
Both the breach and the fix happened months before GDPR went into effect, though.
Re:Google Exposed User Data, Feared Repercussions of Disclos... by dannyw on Monday October 08, 2018 @11:25PM (#18173093)
Generally you want to build systems in compliance of future regulations before they kick in. GDPR at big companies is a multi year effort.
Re:Google Exposed User Data, Feared Repercussions of Disclos... by fixermark on Tuesday October 09, 2018 @03:58PM (#18179328)
Even before the GDPR, Google had to contend with the NSA / GCHQ illicit access events and the China hack.

They had plenty of experience to suggest to them that keeping highly-detailed logs around indefinitely could do more harm to their users than good.

Re:Google Exposed User Data, Feared Repercussions of Disclos... by wora on Tuesday October 09, 2018 @03:56PM (#18179318)
Such policy existed since the very beginning of Google APIs, and is well documented within the company. Anyone who worked at Google should be aware of it.
Re:Google Exposed User Data, Feared Repercussions of Disclos... by gsich on Tuesday October 09, 2018 @03:14AM (#18173914)
I have my doubts here too.
Re:Google Exposed User Data, Feared Repercussions of Disclos... by adrianmonk on Monday October 08, 2018 @10:27PM (#18172909)
Developers have a natural, and understandable, urge to include data in the logs that they need for debugging. If you purge logs, it is simpler and easier to have higher confidence that you are retaining only the data you intended to retain.
Re:Google Exposed User Data, Feared Repercussions of Disclos... by Dylan16807 on Tuesday October 09, 2018 @02:22AM (#18173721)
Why would someone abusing this API stop doing so? If nobody did so for the two weeks prior to the fix, it's a very reasonable guess that roughly nobody did so ever.

It doesn't sound like the logs are detailed enough to prove the antecedent, though, so it doesn't really matter if the logic is sound.

Re:Google Exposed User Data, Feared Repercussions of Disclos... by ssijak on Tuesday October 09, 2018 @03:13AM (#18173907)
Google and privacy in the same sentence.. and a clumsy one indeed..