News for hackers. Stuff that matters.
Re:Google Drive Found Leaking Private Data by sp332 on Wednesday July 09, 2014 @11:26AM (#8010132)
How does the fix work? Does it prevent the browser from sending the referrer URL? Or maybe load all documents from the same URL with the document ID in a POST request instead or GET?
Re:Google Drive Found Leaking Private Data by aiiane on Wednesday July 09, 2014 @11:31AM (#8010160)
Normally most outgoing links that are meant to be private are bounced through a redirection that results in the referrer being a generic Google redirection page. That's probably the solution that was applied here.
Re:Google Drive Found Leaking Private Data by sp332 on Wednesday July 09, 2014 @11:48AM (#8010260)
But it says this was only a problem for documents that were not converted to Google Sheets etc. I don't think editing everyone's PDFs and every other kind of document that has clickable URLs is the easiest way to solve this.
Re:Google Drive Found Leaking Private Data by dlgeek on Wednesday July 09, 2014 @12:04PM (#8010365)
Looks like it only applies to a "Preview" feature, so I imagine they're already parsing the contents to render the preview and are either adding a redirect or a no-follow attribute.

Native-native docs wouldn't have a referrer because they wouldn't be rendered by the browser, so links would be a direct hop.