I am thinking of a consumer that subscribes to a wildcard that will match all destinations, the mqtt support has made that possible. It is easy to consume all messages. Or subscribe to a composite will all dests in there. It could make sense to deny composites or multi matching wildcards if they won't be used by an app. Auth will help here in any event.
On 14 April 2015 at 15:17, xabhi <[email protected]> wrote: > Hi gary, > > In this reply > http://activemq.2283324.n4.nabble.com/DOS-attack-on-activemq-setup-tp4694598p4694602.html > <http://activemq.2283324.n4.nabble.com/DOS-attack-on-activemq-setup-tp4694598p4694602.html> > you mentioned about controlling composite destinations. What kind of > problems can be caused using composite destinations from client side? I have > never used them and its unclear to me in what way it can abused to disrupt > broker service. > > > > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/DOS-attack-on-activemq-setup-tp4694598p4694883.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
