Launchpad doesn't allow project bug tracker to be configured to forbid 'private' bugs

Bug #1821769 reported by Peter Maydell
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

The QEMU project has its own security-issue reporting policy, so we don't use Launchpad's "private" bug option. In QEMU's case public bug reports get gatewayed to our mailing list, which is where developers become aware of them and act on them. Private bug reports are not gatewayed, which means that filing a private bug on our LP is effectively sending it to /dev/null.

It would be nice if Launchpad allowed projects to configure their bug tracker to forbid creation of any "private" bugs. At the moment the best we can do is add a 'Do NOT report security issues as "private" bugs in this bug tracker' warning in the 'bug reporting guidelines' text, but of course some users will miss this. If we could just disable the feature entirely we could help our users avoid falling into this black hole.

Revision history for this message
Colin Watson (cjwatson) wrote :

I wonder if we could do this by inventing a new bug sharing policy that's even more public than Public: that is, even Private Security is forbidden.

tags: added: disclosure feature lp-bugs
Changed in launchpad:
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.