verm__ changed the topic of #buildbot to: A Software Freedom Conservancy Project | Buildbot-3.5.0 | docs: http://docs.buildbot.net/current/ | tutorial: http://docs.buildbot.net/current/tutorial | irclogs: https://libera.irclog.whitequark.org/buildbot
StocksRoomm has joined #buildbot
StocksRoomm has quit [K-Lined]
Guest81 has joined #buildbot
<Guest81> hey I was wondering how much damage someone could do if they had root access to one of my worker bots (and the worker password)?
<Guest81> are there any protections in place for such a scenario?
<Guest81> for example, can the worker arbitrarily use the fileupload functionality on my master bot?
<glogan> Afaik yes
<glogan> Restricted by the master buildbot's uid perms
<glogan> Ie, you don't get root on the master, unless master is running buildbot as root.
<Guest81> how can I protect against this? my master instance contains all of my secrets
<Guest81> also, is there a way I can send commands from the worker to the master bot without having the master bot send the initial message?
<Guest81> for example something like `s = Worker(login)` then `s.sendCommand(TransferFile)`?
<Guest81> I want to be able to simulate an attack so I can protect the filesystem properly
Guest81 has quit [Quit: Client closed]
<glogan> Looking at https://docs.buildbot.net/latest/manual/configuration/steps/file_transfer.html I don't see a way to provide per-file protection. In theory the worker should be executing commands form the build pipeline and nothing else.
<glogan> But a rooted worker might have other code.
<glogan> Ah he's gone
Guest81 has joined #buildbot
Guest81 has quit [Client Quit]