cumin init script starts cumin listening to localhost only
# rpm -q cumin cumin-0.1.2690-1.el5
This is perhaps notabug. We chose this as the default behavior after our initial security audit, and on the advice of the security folks. I think perhaps we should treat this as a documentation issue and tell folks they will have to take the extra step and add "addr: someaddress" to their cumin.conf to make it available over the network.
Maybe this is an issue of cumin and mint being run together? Seems sensible that mint would be run only accepting connections from localhost, but it seems cumin should be configured to allow external connections by default unless it is intended to be deployed on user systems.
Well, it is deployed on user systems quite often, as a UI for visualizing broker and grid state and for doing wiring, etc. That's the thing, the management console is for big deployments and for evaluators. I think the current default is a lot safer.
cumin-0.1.4279-1.el5.noarch provides a means to make cumin-web bind to non-localhost, and independently of cumin-data (mint).