-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dollar topic clarification #2508
Comments
I don't believe the dollar behaviour to be buggy. I have taken the view that a new dollar topic effectively creates a new tree, but otherwise the behaviour remains the same across all topics. Changing the behaviour so that dollar topics do not match with wildcards would be contrary to the behaviour of the rest of the spec. I do see the point you're making though. Perhaps having a broker specific I would also point you to the lines in the v5 spec |
Thanks for your insights and clarifications! I will find some other way to deal with security, I'm closing this issue. |
Hi,
I just verified that, as mentioned in #2111, dollar topics can be published to by clients. They behave exactly as I would like, that is, the subscription has to contain the dollar segment characters otherwise a subscription will not match. But that is true for the first segment only, which I find kind of weird. I am using Mosquitto 1.6.x.
If all segments would show that behaviour, messages could be protected using shared secrets, reducing the need to write ACLs and offering more flexibility for sensitive applications. This is obviously compatible with $SYS as long as no dollar sub-topics exist.
Since dollar topic behaviour is largely left to the implementor, I suspect other brokers implement that logic irrespective of the segment index already.
Is this possible in Mosquitto? Or do you consider current behaviour buggy wrt the dollar sign?
The text was updated successfully, but these errors were encountered: