Attachments of private bugreports are public
Bug #39674 reported by
Dennis Kaarsemaker
This bug affects 7 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Abel Deuring |
Bug Description
Bug 39298 is a private bug. As such I cannot view it (it's publicly archived on lists.ubuntu.com, but that's beside the point). However, the attachment added to that bug is still publicly visible. That should at least be indicated when a person uploads, but preferably the attachment is private too.
See also bug 512085.
Related branches
lp://staging/~adeuring/launchpad/bug-39674-change-remaining-lfa-http_url
- Deryck Hodge (community): Approve (code)
-
Diff: 514 lines (+105/-48)17 files modifiedlib/canonical/launchpad/browser/librarian.py (+4/-2)
lib/canonical/launchpad/webapp/launchbag.py (+1/-1)
lib/canonical/librarian/client.py (+1/-0)
lib/lp/bugs/adapters/bugchange.py (+13/-4)
lib/lp/bugs/browser/bug.py (+8/-1)
lib/lp/bugs/browser/bugattachment.py (+4/-2)
lib/lp/bugs/browser/bugtarget.py (+5/-0)
lib/lp/bugs/doc/bug-change.txt (+6/-4)
lib/lp/bugs/doc/bug-export.txt (+1/-1)
lib/lp/bugs/doc/bugnotification-email.txt (+10/-20)
lib/lp/bugs/model/bugattachment.py (+5/-0)
lib/lp/bugs/scripts/bugexport.py (+3/-1)
lib/lp/bugs/stories/bugattachments/xx-attachments-to-bug-report.txt (+5/-1)
lib/lp/bugs/stories/bugattachments/xx-delete-bug-attachment.txt (+3/-1)
lib/lp/bugs/stories/bugs/xx-bug-text-pages.txt (+24/-5)
lib/lp/bugs/templates/bugtarget-patches.pt (+2/-2)
lib/lp/bugs/tests/test_bugchanges.py (+10/-3)
Changed in malone: | |
status: | Unconfirmed → Confirmed |
tags: | added: ubuntu-qa |
description: | updated |
Changed in malone: | |
importance: | Medium → High |
tags: | added: privacy |
Changed in malone: | |
status: | Triaged → In Progress |
assignee: | nobody → Abel Deuring (adeuring) |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in malone: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The problem is that currently all and any librarian content is publically available if you can figure out the filename. For 1.2.4 we will have a private librarian instance, but it will only be usable internally. The next step is allowing access-controlled downloads to that private librarian; this will eventually allow us to fix this bug.