On Fri, Jan 11, 2013 at 7:12 AM, Brian J. Murrell <br...@interlinx.bc.ca> 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.
Doesn't the connecting node name already have to be configured in
jenkins - and not already connected? I'd actually like the ability
to add new anonymous-but-labeled nodes on demand but didn't think it
was possible.
--
Les Mikesell
lesmikes...@gmail.com
