Because our engineers are on umpteen different networks in our organization, all of which is behind a firewall. I figure that if some hacker is good enough to get into our organization, he deserves to be able to use distccd as medium for doing more harm. In any case, once he's in, there are plenty more well-known ways to get at stuff. And, if he uses distccd to run stuff on remote machines, then he'll be running that stuff as me (user norman), which means he can only do what I can do in the network -- which is mostly just mess up my own stuff. I'm willing to take that risk.
It certainly is alot easier than putting about 14 --allow statements in each distccd startup command-line. Vic --- Martin Pool <[EMAIL PROTECTED]> wrote: > On 13 Oct 2004, Victor Norman <[EMAIL PROTECTED]> wrote: > > Martin, et al, > > > > How do we allow connection from anywhere? --allow 0.0.0.0 ? > > Why would you want to do that? > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=276277 > > -- > Martin > > ATTACHMENT part 2 application/pgp-signature name=signature.asc _______________________________ Do you Yahoo!? Express yourself with Y! Messenger! Free. Download now. http://messenger.yahoo.com __ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/distcc