Agree with Brian here. Only do it when you are trusting the users of the network.
2013/1/11 Brian J. Murrell <br...@interlinx.bc.ca> > On 13-01-11 05:55 AM, > matthew.web...@diamond.ac.uk wrote: > > > > Fixed by going to Manage Jenkins -> Configure Global Security, and > under Project-based Matrix Authorization Strategy I had to enable > “connect” in the “slave” section, for user “Anonymous”. > > IIUC, that's going to leave your Jenkins server open to allowing any > random (i.e. blackhat) slave to connect, accept a build job and submit a > build result with a trojan inserted. > > So not really an acceptable solution, or even work-around. > > b. > > > -- Kohsuke Kawaguchi
