News for hackers. Stuff that matters.
Re:Why you should not trust emails sent from Google by vog on Wednesday September 11, 2013 @04:13AM (#6366082)
> As for the Chrome report you mention, if you provide the bug ID I can check.

This demonstrates exactly what's wrong with Google's interpretation of "openness". Sure, if one finds some Google insider, one may get information. Normally (read: in almost all other bigger Free Software projects), one could simply have a look at the bug tracker on one's own, without being on the mercy of Google.

Re:Why you should not trust emails sent from Google by justinschuh on Wednesday September 11, 2013 @09:32AM (#6367006)
I asked for the bug ID so that I could verify it was triaged properly, not because the report isn't public. Some reports (like security bugs) are initially private, as is typical in any open source project. However, security bug reports are made public as well at some after they're resolved.

You can go ahead and see for yourself: https://code.google.com/p/chromium/issues/list

Re:Why you should not trust emails sent from Google by mpyne on Wednesday September 11, 2013 @10:55AM (#6367536)
For example, the KDE security mailing list is definitely private, and some KDE bugtracker bugs are private as well.
Re:Why you should not trust emails sent from Google by mineo on Wednesday September 11, 2013 @04:33AM (#6366131)
Having reported a bug in Chromium myself that I thought was security related (but in the end was not - better safe than sorry), I think it's a reasonable decision to not show security related bug reports/tickets from the general public - you'd otherwise present all security holes in the browser to every evil guy in the world on a silver platter.
Re:Why you should not trust emails sent from Google by estel on Wednesday September 11, 2013 @04:28AM (#6366117)
Not usually for reported security vulnerabilities
Re:Why you should not trust emails sent from Google by Skalman on Wednesday September 11, 2013 @04:32AM (#6366129)
But I thought the point was that they didn't consider this to be a security vulnerability.