Replace getName/verifySlaveBuildID

Bug #544237 reported by Jeroen T. Vermeulen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Jeroen T. Vermeulen

Bug Description

The combo of IBuildFarmJob.getName and IBuildFarmJobBehavior.verifySlaveBuildID is unnecessarily complicated:
 * Both methods are specialized for different build-farm job types.
 * There may not be any need for a separate verification method if, for verification, we can just re-generate the slave build id and see that what we're verifying matches the newly generated one.

My preference is just to have a single method that produces a "slave build cookie," a hard-to-guess string that a compromised slave could not easliy forge to impersonate another slave. It would be a hash based on buildqueue id, creation date, requester, and perhaps other things. In this way, if it actually matters (it's not certain that impersonation is an actual risk) a compromised slave gets no useful information as starting point for guessing other slaves' cookies.

Related branches

Changed in soyuz:
status: New → Triaged
importance: Undecided → Low
tags: added: buildfarm soyuz-build
Revision history for this message
Ursula Junque (ursinha) wrote : Bug fixed by a commit
Changed in soyuz:
assignee: nobody → Jeroen T. Vermeulen (jtv)
milestone: none → 10.04
status: Triaged → Fix Committed
tags: added: qa-needstesting
tags: added: qa-ok
removed: qa-needstesting
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.