security – How Authorize/Authenticate a users (not a machine) in AWS-IoT-Core MQTT broker?

In the AWS-IoT-Core the Authentication & Authorization are made by polices and certificate in order to restrict a THING to get access to the MQTT broker, publish or subscribe to a specific topic. In this scenario I have a topic attached to a lambda that will apply a DELETE operation in a database. The machine (the thing) is already authorized/authenticated trough certificates/policies but let’s say a hacker got access to the machine and to its certificate. Reading the Firmware he will see the a topic to dele a file, for example p/serialNumber/deletelog/log_nb. Now the hacker, trough the machine, is authorized and authenticated to publish in this topic. I would like to know if it is possible to mitigate this action (in this scenario) by creating a kind of Authorization SESSION, like a HTTP SESSION in the MQTT architecture. In this scenario the hacker would need a login and password to be Authorized to this operation (not only the machine). It would be another layer of security.

Successful Broker –

I’m not admin here!


Our program is intended for people willing to achieve their financial freedom but unable to do so because they’re not financial experts. is a long term high yield private loan program, backed up by Forex market trading and investing in various funds and activities. Profits from these investments are used to enhance our program and increase its stability for the long term.

Reduced Size Image

149 days 0.8% daily
Plan Spent Amount ($) Daily Profit (%)
Plan 1 $10.00 – $149.00 0.80


SSL Encryption
DDos Protection
Licensed Script
Registrar NameCheap, Inc.
Created on 2021-02-26
Expires on 2022-02-26
Updated on 2021-02-26

Accept: PM, Payeer, Bitcoin, ETH,…

Join here:

This post has been edited by xetang: Today, 01:22 PM

Spread Of Crypto Currency At Forex Broker


❕NEWS – Trading with an online Bitcoin broker |

Choosing among the best Bitcoin brokers is a decision which should be made based on your individual preferences. However, there are established and reputable companies, some of which are listed above in our brief broker comparison.
If you start trading and invest in Bitcoin, you can balance your portfolio. Given the industry’s volatile nature, you can also hope to rapidly increase the overall value of your investments. Despite the fact that the cryptocurrency market entered a prolonged bear market in 2018 and the prices are currently depreciating, volatility makes it possible to quickly regain one’s losses.
Of course, once again, it’s important to note that you should consider the risks and invest only as much as you can afford to lose.

The Broker

The broker can affects the result of our trading with certainly , that’s why from all choosing a broker is more important task. We the traders should choose the broker that is more appropriate to the concept of trading that will be used , the traders who are particularly scalpers have to choose the broker that allows trading concept such as this. as a scalper now I am with LQDFX which permits scalping including lowest trading spreads as well minimum margin requirements. so, my trading life is very much comfortable.

How to setup Mosquitto MQTT Broker in Kubernetes

I have been trying to set up ChirpStack in a Kubernetes space, but it doesn’t seem to be working for me, and I can’t find any resources online that have been the solution.

chirpstack-application-server-6d6f8d699c-nlrmx 1/1 Running 0 44s
chirpstack-gateway-bridge-5454b7f9f-fm5wl 1/1 Running 0 73s
chirpstack-mosquitto-646899d74d-d7bhl 0/1 CrashLoopBackOff 3 85s
chirpstack-network-server-66cdf9bdf7-rhzg5 1/1 Running 0 55s

Above is every pod I have atm. App-server, net-server, gateway-bridge all spin up and run, however the Mosquitto broker moves to ‘Complete’ and goes right into the CrashLoopBackOff.
I have figured it might be something to do with a lack of config, so I’ve spent a few days putting together the mosquitto.conf file with “allow_anonymous true” hoping to get a connection from any of my ChirpStack components, but the logs just indicate an mqtt connection refused error.

output of kubectl logs chirpstack-application-server

time=”2020-12-10T15:01:41Z” level=error msg=”integration/mqtt: connecting to broker error, will retry in 2s: Network Error : dial tcp i/o timeout”

Because no connection could be made, I assumed it was the opposite and I needed to add in the password_file and make allow_anonymous false. Below is my current config if anyone might have an idea what is wrong.


kind: ConfigMap
  name: mosquitto-password
  namespace: ****
    app: chirpstack-mosquitto  
  password_file.txt: |


kind: ConfigMap
  name: mosquitto-config
  namespace: ****
    app: chirpstack-mosquitto  
  mosquitto.conf: |    
    persistence true
    persistence_location /mosquitto/data/
    # per_listener_settings false
    log_dest stdout
    # listener 1886
    listener 1883
    protocol mqtt
    # Defaults to false, unless there are no listeners defined in the configuration
    # file, in which case it is set to true, but connections are only allowed from
    # the local machine.
    allow_anonymous false
    password_file /.config/mosquitto/auth/password_file.txt
    #    cafile: /mosquitto/config/certs/ca.crt
    #    certfile: /mosquitto/config/certs/server.crt
    #    keyfile: /mosquitto/config/certs/server.key
    require_certificate false
    use_identity_as_username false


kind: Deployment
  name: chirpstack-mosquitto
  namespace: ****  
  replicas: 1
      app: chirpstack-mosquitto
        app: chirpstack-mosquitto
      - name: chirpstack-mosquitto
        image: ****/chirpstack/eclipse-mosquitto:1.6.12
        - containerPort: 1883
        - name: password-file
          mountPath: /.config/mosquitto/auth/password_file.txt
          subPath: password_file.txt
        - name: mosquitto-data
          mountPath: /mosquitto/data
        - name: mosquitto-log
          mountPath: /mosquitto/log
        - name: config-file
          mountPath: /.config/mosquitto/mosquitto.conf
          subPath: mosquitto.conf         
        runAsNonRoot: true
        fsGroup: 1
        runAsGroup: 1000
        runAsUser: 1000
        - 1    
      - name: config-file
          name: mosquitto-config
      - name: password-file
          name: mosquitto-password        
      - name: mosquitto-data
        emptyDir: {}
      - name: mosquitto-log
        emptyDir: {}   


kind: Service
  name: chirpstack-mosquitto
  namespace: 186215-poc  
  type: ClusterIP
    - name: mqtt 
      port: 1883
      targetPort: 1883
      protocol: TCP  
    app: chirpstack-mosquitto    

5 Essential Things to Consider While Choosing Forex and CFD Trading Broker – General Forex Questions & Help

Owing to modern advancements, the world has seen quite a lot of financial developments. One such development, Forex and CFD trading has become quite popular amongst traders due to various factors such as ease and availability. 

However, if you’e interested in investing in Forex, it becomes essential that you choose the proper Forex and CFD broker. So, to assist you, this CFD trading guide will help you choose the one that is the best and most reliable for you. 

1. The Regulations Must Be Proper 

The very first and the most important thing to consider before choosing a trading broker is the regulation. 

Now, no matter how much security, various platforms today are full of fraudulent traders brokers who may take away all your funds. In such a situation, it becomes important that the broker protects your rights and your interests. 

For example, these regulations can help in protecting your funds if or whenever your broker has disappeared or doesn’t have sufficient funds. It also ensures that your funds are kept safe and secure in a separate account than the broker’s account. 

Additionally, such regulations help in maintaining and encouraging fair trading practices. This ensures that the execution of your trades is at the proper and recent market prices. 

However, to gain all of the above benefits, you need to go for a licensed broker. You also need to make sure it has a clean record. 

2. Security Policies 

One of the biggest risks of financial platforms is the disclosure of confidential information such as your bank account details, card details, and even your I.D proof such as a passport. Thus, this is where data security comes into consideration. 

When you’re choosing a Forex and CFD trading broker, you need to take care of security concerns. There are plenty of chances that cybersecurity may not work as efficiently as it should. This can put your financial data as well as personal data at a high risk of theft. 

Hence, it becomes necessary to go for a broker that offers proper security via a cybersecurity firm and necessary encryptions. 

3. Friendly Trading Platform 

The trading platform needs to have a friendly user-interface to make it easier for you. An easy to use user-interface will give you a smooth and fun experience while trading. 

You need to ensure that the trading software provides you easy navigation, technical analysis tools, Forex indicators, charting capabilities, etc. All these factors will make it easier for you to succeed. 

Also, try to use a demo trading account at first then move on to real trading accounts. Besides, catch the certain differences between demo and live trading:

The software needs to look secure and reliable. Additionally, it should include risk management functionality and customizable add-ons. 

The good news is you can get a free demo from most Forex and CFD brokers. During the demo, you are free to check out the software and test out the platform to decide if it is the right one for you or not. 

4. Responsive Customer Support 

If you get into trading, you need a broker with responsive and reliable customer support. You are vulnerable to face issues all the time that you need to solve as soon as possible. 

A broker with good customer support can help you solve your problem efficiently if you ever faced one. They will also be always there to answer any inquiry or doubt that you have. 

A possible issue you might face could be related to deposits, withdrawals, incorrect execution of trades, and other such issues. That is why you need someone that you can contact to help you solve the issue immediately.  

Good customer support should give you the option to contact them through multiple ways such as live chat, email, and phone. It could be a bonus if they provide different languages other than English. 

5. Fast Deposit and Easy Withdrawal 

The broker of choice should allow you to deposit money in several ways. It should include debit cards, credit cards, wire transfers, and bank checks. This wide range of methods will make it much easier for you to deposit money and start trading right away. 

Regarding withdrawals, you need a broker that provides a wide range of payout options. Moreover, your broker needs to give you the smoothest and fastest withdrawal process possible. 

You need to pay attention to the deposit and withdrawal fees if there are any. Some brokers take more fees than others. Also, there might be a daily withdrawal limit, so check that out before you start trading as well. 


Finding a good broker – General Forex Questions & Help

Finding a right broker is a troublesome occupation. Here are several tips to pick a standard broker. The critical thing you have to see is the true blue body of the broker. It is key bit of a broker. By then yield for leverage, edge and spreads. So in addition check beginning deposit stray pieces. Moreover, that it is so normal to deposit and withdraw your cash. Furthermore check their client leverage. I am also a forex trader. In like way, for my trading I have gotten Eurotrader as it is a regulated forex broker. The broker offers bewildering offers and relationship for their customers. 

Broker queue and topic naming conventions

I’m in the process of adding a message broker (ActiveMQ Artemis) to a system currently and while I have my own notions on how I can divide up the namespace, it seems like a good time to get opinions from others on how they like to name their queues and topics.

The overall topology I’m after is to support functionality grouped in two ways:

  • By technology and/or library. This is when messages that enter the system are defined by a specific application level library. Think Laravel queues, or Mass Transit in .net. This first convention allows me to sequester message activity on the broker per-library as they often feature proprietary conventions and function under the assumption that they own their messaging space exclusively.
  • By business domain. This one is a little more abstract, but is defined by the various sections of my ecosystem. It’s intended to facilitate messaging between applications that might be written in different languages. For example, perhaps I have a queue name of my-org:identity and this represents general user activity (CRUD). I might also have a my-org:blog to represent events and activity on blog posts that I wish to broadcast and react to. These could be subscribed and published to using libraries built around protocols like AMQP or STOMP, etc. from within different languages.

Acknowledging that you can’t 100% predict the future are there any insights, lessons-learned and intuition worth heeding when coming up with naming conventions within a messaging system?

Are there any good books, blog posts or articles on devising sound schemes for names on brokers?

microservices – Data replication via message broker or built-in replication feature?

I’m working on a microservice system where 8 services share the same data – most notably: auth, forum, portal.

Essentially, forum and portal use users from auth, and since I went with the ‘AP’ approach in CAP Theorem – I duplicate data from users and store it in database of forum and portal whenever it changes – thus removing SPoF if auth dies.

Now, currently I do it by using a message broker (rabbitmq) to listen to UserCreated, UserDeleted and UserUpdated events – from which I get the data.

Should I be doing it this way, or should I use a replication feature built into Postgres?
I imagine that my approach allows for replication across multiple database types, be it: MS SQL, Postgres, MySQL, NoSQL or NewSQL solutions.