private ppa access granted to inactive persons
Bug #1006692 reported by
Robert Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Colin Watson |
Bug Description
generate-
Related branches
~cjwatson/launchpad:remove-htpasswd-generation
Merged
into
launchpad:master
- Ioana Lasc (community): Approve
-
Diff: 1121 lines (+18/-773)7 files modifieddev/null (+0/-139)
lib/lp/archivepublisher/publishing.py (+3/-28)
lib/lp/archivepublisher/scripts/generate_ppa_htaccess.py (+11/-206)
lib/lp/archivepublisher/tests/test_generate_ppa_htaccess.py (+1/-351)
lib/lp/archivepublisher/tests/test_publisher.py (+0/-39)
lib/lp/registry/scripts/closeaccount.py (+3/-6)
lib/lp/services/scripts/base.py (+0/-4)
~cjwatson/launchpad:archive-auth-inactive-person
Merged
into
launchpad:master
- Ioana Lasc (community): Approve
-
Diff: 106 lines (+52/-7)2 files modifiedlib/lp/soyuz/doc/archiveauthtoken.txt (+20/-0)
lib/lp/soyuz/model/archiveauthtoken.py (+32/-7)
tags: | added: merge-deactivate ppa privacy |
Changed in launchpad: | |
status: | Triaged → In Progress |
assignee: | nobody → Colin Watson (cjwatson) |
Changed in launchpad: | |
status: | In Progress → Fix Released |
information type: | Private Security → Public Security |
To post a comment you must log in.
I think the new WSGI authenticator still has this problem, although it should now be easier to fix since we won't need to schedule htpasswd updates when account statuses change.