Slave To Master Access Control

[Ashish]

Can someone please help me understand https://wiki.jenkins-ci.org/display/JENKINS/Slave+To+Master+Access+Control ?

I have some jobs that are configured to run on a specific slave. These jobs are only dedicated to run on the specific slaves. Therefore, should i turn ON the access control or leave it OFF?

What is the definition of a Trusted Slave in this context?

The slaves were built by me and I am the administrator for both the master and the slave nodes.

How can I tell if a slave is executing anything on the master? I don't think it is currently doing so. How can I confirm this?

Thanks,

Ashish.

[Stephen Connolly]

Is the slave OS as secure as your master OS?

Is the slave set-up by somebody you trust as much as the person who set-up the master?

If the answer to the above two questions is yes, then you can leave SECURITY-144 turned off.

If the answer to either question is no and you do not feel particularly worried about somebody hacking into a slave in order to compromise your Jenkins master, you can leave SECURITY-144 turned off.

Things you might be worried about:

* Somebody hacks your Jenkins slave and modifies the PATH so that a "fake java" is launched in place of the real "java". That fake java can be specially crafted such that it makes requests of the master that could result in the master being compromised.

Now if you set up both the master and the slave, then chances are that what ever hack you left open on the slave is also open on the master... so worrying about the slave is kinda pointless if the same door is already open on the master... an attacker would just use the open door

If you did not set both up, say the build slave is the FooBar team's build slave that you have been asked to join to your Jenkins instance... well in that case you could have a developer that has access... and if the developer's desktop gets hacked, their SSH key could be stolen and then used to connect to the slave... and hence attacked all the way up to the master via a SECURITY-144 style attack... in that case you turn the setting on. For most normal builds the existing white list is sufficient that you will not have to do anything else... if you use fancy plugins then there may be some additional white list entries required or else plugin updates

HTH

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b18702c2-bad9-4202-ac94-87aba5cc2c57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.