Report shows private bugs

[basak]

If I can see private bugs, they show up in the report. Then I might accidentally copy and paste the bug to somewhere public.

For the purpose of our bug triage process, private bugs are presumably out of scope, so perhaps we should simply identify and suppress them?

[powersj]

In that case, do we even need to login? We could then use an anonymous launchpad login and get all the non-private bugs.

[basak]

That makes sense. I can't think of anything in it that should require a login. However, if that ever changes, then that might lead to a regression, and the issue that it is fundamentally dangerous to present private bugs without flagging them when we have a public triage process. Using an anonymous login to step around the issue feels like a hack to me that may not always work, such as if in the future we do need some additional privilege.

[basak]

One class of private bug that we might want to continue to see is a crash report that contains private information, which community reporters can flag and then only people in some subset (bug squad?) can see.