Slave build ID should not be used for much at all

Bug #549907 reported by William Grant
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
William Grant

Bug Description

The slave build ID is not trustworthy -- anybody can easily compromise a slave and make it return whatever build ID they want. But it's currently used in lots of buildd-manager logging, which is confusing and potentially unsafe.

Nothing should touch slave build IDs except dispatchBuildToSlave, rescueIfLost and verifySlaveBuildID. Once all users have been adjusted to not use it, Builder.slaveStatus should be taught to stop putting it in the dict.

Tags: lp-soyuz qa-ok

Related branches

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