Then I would make the default yml file have a comment above the default saying "This doesn't work on MacOS, you can use 0.0.0.0 but it will allow open network connections too".
I would wager that 80%+ of BackgroundRB deployments have not secured this since the security implications are not noted at all. This seems really dangerous. On 3/12/08 3:52 PM, "hemant kumar" <[EMAIL PROTECTED]> wrote: On Wed, 2008-03-12 at 14:43 -0700, Noah Horton wrote: > Wait - the default config used in all the examples has the > backgroundrb workers listening to connections from all public > interfaces? That seems like a really risky thing. Perhaps the > examples should all get updated to 'localhost'. > Except 'localhost' doesn't work on Mac OSX from my experience. > > On 3/12/08 2:02 PM, "Ryan Leavengood" <[EMAIL PROTECTED]> wrote: > > On Wed, Mar 12, 2008 at 4:47 PM, Noah Horton > <[EMAIL PROTECTED]> wrote: > > > > Is there any config to get the backgroundrb instances to > listen to requests > > from any machine besides localhost? > > If you use the same backgroundrb.yml used for your Mongrel > machines on > the BackgrounDRb machine (which you should), then it should > listen on > the machine's IP which you have configured in that file. If > you want > it to listen to all interfaces then use 0.0.0.0 like hemant > said in > his previous post. > > Regards, > Ryan > > _______________________________________________ > Backgroundrb-devel mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/backgroundrb-devel
_______________________________________________ Backgroundrb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/backgroundrb-devel
