SourcePackageRelease security adapter is unused

Bug #315476 reported by Celso Providelo
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Celso Providelo

Bug Description

There is a type in the code (s/userfor/usedfor) which indicates the security adapter is not being used as expected, and also that it wasn't tested at all.

Further investigation revealed that not information was leaked because SPRs are not directly exposed in the UI and the related available objects (publishing and build records) reuse the security-adapter code in place (which is correct and covered by tests).

While in this area, we can remove the SPR._cached_publishing_archives and fix up the callsites (theoretically only the SPR security-adapter) because now that security adapters results are cached at the storm cache level, this deprecated property does not represent any performance gain anymore.

Tags: lp-soyuz
Revision history for this message
Celso Providelo (cprov) wrote :

To be done sooner than later, but doesn't represent any major problem or information leak (no CP required either).

Changed in soyuz:
assignee: nobody → cprov
importance: Undecided → High
milestone: none → 2.2.1
status: New → In Progress
Revision history for this message
Celso Providelo (cprov) wrote :

RF 7545

Changed in soyuz:
status: In Progress → Fix Committed
Celso Providelo (cprov)
Changed in soyuz:
status: Fix Committed → Fix Released
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.