|Re: [mosquitto-dev] using ACLs and TLS.|
Using a second listener means to run another mosquitto process and a new port ?
for intance I will have a process listening on port 8883 using tls and other proccess listening at port XXXX ?
Those process can share topics ?
On 03/05/18 12:40, Karl Palsson wrote:
Leandro <ingrogger@xxxxxxxxx> wrote:Hi guys , Im using ACLs pluging and TLS connection with a great result. Now, in order to get a fully operational broker I need to accomplish two goals: 1st: Declare if possible a read/write topic that bypass the acls , so it is available for all users. (So far I declare an acl rule per each user to access this special topic). 2nd: Create a local user that can connect to tls server without using certificate. (I think it is not necessary to use encryption for a local monitoring purpose user)This can often be achieved simply with a second listener, that binds only to localhost, and simply doesn't enable TLS. CHeers, Karl P