Anticloud/anticloud-mosquitto

MOSQUITTO

Anticloud-hardened packaging of the upstream project MOSQUITTO in category CONSUMER APPLIANCES. Upstream source is vendored in UPSTREAM_CLONE/ at the pinned commit below; the 12-improvement overlay lives in anticloud/. Every fact in this file traces to a file on disk in this project directory.

Category: CONSUMER APPLIANCES · Upstream: https://github.com/iegomez/mosquitto-go-auth · Upstream pin: 20ee9310fe3a05e5b6915ce6369bcd0837309894 · Vendor: Anticloud FZ LLE

---

What This Project Does

Eclipse Mosquitto

Mosquitto is an open source implementation of a server for version 5.0, 3.1.1, and 3.1 of the MQTT protocol. It also includes a C and C++ client library, the mosquitto_pub mosquitto_rr, and mosquitto_sub utilities for publishing and subscribing, and the mosquitto_ctrl, mosquitto_signal, and mosquitto_passwd applications for helping administer the broker.

Links

See the following links for more information on MQTT:

• Community page: http://mqtt.org/
• MQTT v3.1.1 standard: https://docs.oasis-open.org/mqtt/mqtt/v3.1.1/mqtt-v3.1.1.html
• MQTT v5.0 standard: https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html

Mosquitto project information is available at the following locations:

• Main homepage: https://mosquitto.org/
• Find existing bugs or submit a new bug: https://github.com/eclipse-mosquitto/mosquitto/issues
• Source code project: https://github.com/eclipse-mosquitto/mosquitto

There is also a public test server available at https://test.mosquitto.org/

Installing

See https://mosquitto.org/download/ for details on installing binaries for various platforms.

Quick start

If you have installed a binary package the broker should have been started automatically. If not, it can be started with a very basic configuration:

mosquitto

Then use mosquitto_sub to subscribe to a topic:

mosquitto_sub -t 'test/topic' -v

And to publish a message:

mosquitto_pub -t 'test/topic' -m 'hello world'

Note that starting the broker like this allows anonymous/unauthenticated access but only from the local computer, so it's only really useful for initial testing.

If you want to have clients from another computer connect, you will need to provide a configuration file. If you have installed from a binary package, you will probably already have a configuration file at somewhere like /etc/mosquitto/mosquitto.conf. If you've compiled from source, you can write your config file then run as mosquitto -c /path/to/mosquitto.conf.

To start your config file you define a listener and you will need to think about what authentication you require. It is not advised to run your broker with anonymous access when it is publicly available.

For details on how to do this, look at the authentication methods available and the dynamic security plugin.

Documentation

Documentation for the broker, clients and client library API can be found in the man pages, which are available online at https://mosquitto.org/man/. There are also pages with an introduction to the features of MQTT, the mosquitto_passwd utility for dealing with username/passwords, and a description of the configuration file options available for the broker.

Detailed client library API documentation can be found at https://mosquitto.org/api/

Building from source

To build from source the recommended route for end users is to download the archive from https://mosquitto.org/download/.

On Windows and Mac, use cmake to build. On other platforms, just run make to build. For Windows, see also README-windows.md.

If you are building from the git project then the documentation will not already be built. Use make binary to skip building the man pages, or install docbook-xsl on Debian/Ubuntu systems.

Build Dependencies

• cJSON - required
• c-ares (libc-ares-dev on Debian based systems) - optional, enable with WITH_SRV=yes
• libedit - for mosquitto_ctrl interactive shell - optional, disable with WITH_EDITLINE=no
• libmicrohttpd - for broker http api support - optional, disable with WITH_HTTP_API=no
• openssl (libssl-dev on Debian based systems) - optional, disable with WITH_TLS=no
• pthreads - for client library thread support. This is required to support the mosquitto_loop_start() and mosquitto_loop_stop() functions. If compiled without pthread support, the library isn't guaranteed to be thread safe.
• sqlite3 - for persistence support in the broker - optional, disable with WITH_SQLITE=no
• uthash / utlist - bundled versions of these headers are provided, disable their use with WITH_BUNDLED_DEPS=no
• xsltproc (xsltproc and docbook-xsl on Debian based systems) - only needed when building from git sources - disable with WITH_DOCS=no

Equivalent options for enabling/disabling features are available when using the CMake build. It is also possible to enable/disable building of specific plugins in the CMake build.

Building mosquitto - Using vcpkg

You can download and install mosquitto using the vcpkg dependency manager:

git source https://github.com/Microsoft/vcpkg.git
cd vcpkg
./bootstrap-vcpkg.sh
./vcpkg integrate install
./vcpkg install mosquitto

The mosquitto port in vcpkg is kept up to date by Microsoft team members and community contributors. If the version is out of date, please create an issue or pull request on the vcpkg project.

Credits

Mosquitto was written by Roger Light roger@atchoo.org. There have been substantial contributions by other people in the community both in terms of code and other help.

Quoted from the upstream README.md file in UPSTREAM_CLONE/. Project-specific facts detected in this directory:

• Ecosystem: Python (requirements) (manifests: requirements.txt; scanned in UPSTREAM_CLONE)
• Top-level source layout: apps/, client/, cmake/, common/, dashboard/, deps/, doc/, docker/, examples/, fuzzing/, include/, lib/
• Upstream commit pinned for this packaging: 20ee9310fe3a05e5b6915ce6369bcd0837309894

---

Installation

See https://mosquitto.org/download/ for details on installing binaries for various platforms.

Section quoted from the upstream readme. Overlay install (this project):

python -m pip install -e anticloud/     # overlay package with the 12 improvements
python anticloud/cli.py --help          # 13 subcommands, JSON stdout

---

Usage

If you have installed a binary package the broker should have been started automatically. If not, it can be started with a very basic configuration:

mosquitto

Then use mosquitto_sub to subscribe to a topic:

mosquitto_sub -t 'test/topic' -v

And to publish a message:

mosquitto_pub -t 'test/topic' -m 'hello world'

Note that starting the broker like this allows anonymous/unauthenticated access but only from the local computer, so it's only really useful for initial testing.

If you want to have clients from another computer connect, you will need to provide a configuration file. If you have installed from a binary package, you will probably already have a configuration file at somewhere like /etc/mosquitto/mosquitto.conf. If you've compiled from source, you can write your config file then run as mosquitto -c /path/to/mosquitto.conf.

To start your config file you define a listener and you will need to think about what authentication you require. It is not advised to run your broker with anonymous access when it is publicly available.

For details on how to do this, look at the authentication methods available and the dynamic security plugin.

Section quoted from the upstream readme. Anticloud overlay CLI (available in every project):

python anticloud/cli.py --help     # 13 subcommands, JSON stdout
python anticloud/cli.py checks     # run the 16-check suite

---

API

=================

Mosquitto is an open source implementation of a server for version 5.0, 3.1.1, and 3.1 of the MQTT protocol. It also includes a C and C++ client library, the mosquitto_pub mosquitto_rr, and mosquitto_sub utilities for publishing and subscribing, and the mosquitto_ctrl, mosquitto_signal, and mosquitto_passwd applications for helping administer the broker.

Section quoted from the upstream readme.

Dependencies

Metric	Value
Ecosystem	Python (requirements)
Manifests detected	requirements.txt
Files in snapshot	not captured in this benchmark snapshot
Lines of code	not captured in this benchmark snapshot
Dependency references	not captured in this benchmark snapshot
Upstream license	BSD-3-Clause
Overlay license	Anticommons 0.1.0

Pinned lockfile: anticloud/requirements.lock (hash-pinned, PEP 508). SBOM: sbom.cdx.json (CycloneDX 1.5, pinned to the upstream SHA).

---

Configuration

mosquitto

Then use mosquitto_sub to subscribe to a topic:

mosquitto_sub -t 'test/topic' -v

And to publish a message:

mosquitto_pub -t 'test/topic' -m 'hello world'

Note that starting the broker like this allows anonymous/unauthenticated access but only from the local computer, so it's only really useful for initial testing.

If you want to have clients from another computer connect, you will need to provide a configuration file. If you have installed from a binary package, you will probably already have a configuration file at somewhere like /etc/mosquitto/mosquitto.conf. If you've compiled from source, you can write your config file then run as mosquitto -c /path/to/mosquitto.conf.

To start your config file you define a listener and you will need to think about what authentication you require. It is not advised to run your broker with anonymous access when it is publicly available.

For details on how to do this, look at the authentication methods available and the dynamic security plugin.

Section quoted from the upstream readme. Overlay configuration (Anticloud):

• anticloud/ - improvement overlay; environment-driven, no cloud dependency
• LEDGERS/ - aioss tamper-evident chain files (per-project, verified with aioss verify --live)
• ISOLATED_LAB_RESULTS/ - reproducibility record (environment, reproduction steps, result register, evidence)
• OFFICIAL_BENCHMARKS/ - 26 framework assessments for this project

---

Contributing

Excerpt from upstream CONTRIBUTING.md:

Contributing to Mosquitto

Thank you for your interest in this project.

Project description:

The Mosquitto project has been created to provide a light weight, open-source implementation, of an MQTT broker to allow new, existing, and emerging applications for Machine-to-Machine (M2M) and Internet of Things (IoT).

• https://mosquitto.org/
• https://projects.eclipse.org/projects/iot.mosquitto

Source

The Mosquitto code is stored in a git project.

• https://github.com/eclipse/mosquitto

You can contribute bugfixes and new features by sending pull requests through GitHub.

Legal

In order for your contribution to be accepted, it must comply with the Eclipse Foundation IP policy.

Please read the Eclipse Foundation policy on accepting contributions via Git.

1. Sign the Eclipse ECA
   1. Register for an Eclipse Foundation User ID. You can register here.
   2. Log into the Accounts Portal, and click on the 'Eclipse Contributor Agreement' link.
2. Go to your account settings and add your GitHub username to your account.
3. Make sure that you sign-off your Git commits in the following format:

Signed-off-by: John Smith <johnsmith@nowhere.com> This is usually at the bottom of the commit message. You can automate this by adding the '-s' flag when you make the commits. e.g. git commit -s -m "Adding a cool feature" 4. Ensure that the email address that you make your commits with is the same one you used to sign up to the Eclipse Foundation website with.

Contributing a change

1. Fork the project on GitHub
2. source the forked project onto your computer: git source https://github.com/<your username>/mosquitto.git
3. If you are adding a new feature, then create a new branch from the latest develop branch with git checkout -b YOUR_BRANCH_NAME origin/develop
4. If you are fixing a bug, then create a new branch from the latest fixes branch with git checkout -b YOUR_BRANCH_NAME origin/fixes
5. Make your changes
6. Ensure that all new and existing tests pass.
7. Commit the changes into the branch: git commit -s Make

Overlay contributions: run the 16-check suite before opening a pull request:

python anticloud/bench/runner.py --cwd anticloud

---

License

Upstream license: BSD-3-Clause (evidence: LICENSE.txt in the upstream snapshot).

License file excerpt:

This project is dual licensed under the Eclipse Public License 2.0 OR the
Eclipse Distribution License 1.0 as described in the epl-v20 and edl-v10 files.

SPDX-License-Identifier: EPL-2.0 OR BSD-3-Clause

Anticommons 0.1.0 overlay

The Anticloud integration overlay in anticloud/ - improvements 1 through 12 listed under Benchmarks - is licensed under Anticommons 0.1.0. Upstream code remains under its original BSD-3-Clause terms. See ANTICOMMONS_LICENSE.md in this directory for the overlay terms and contact.

SPDX: BSD-3-Clause (upstream) + Anticommons 0.1.0 (overlay, dual).

---

Upstream

• Project: MOSQUITTO (category: CONSUMER APPLIANCES)
• Upstream URL: https://github.com/iegomez/mosquitto-go-auth
• Pinned commit (SHA): 20ee9310fe3a05e5b6915ce6369bcd0837309894
• Branch: master
• Pin provenance: GitHub API commits/master. The parent-project stamp is explicitly rejected for this project.
• Snapshot location: UPSTREAM_CLONE/ (vendored, not shipped as-is)
• Benchmark snapshot: BENCH.json

---

Benchmarks

Measured by the Anticloud assurance suite. Every value below is read from this project's BENCH.json, produced by a real run — the SHA3-256 of that file is b3596771ad41e74ee7eedccaa44207b8d78ff8d4c871d0e70951d64b0c458dda.

Framework	Controls	Evidence	Coverage	Result
OWASP Top 10 for LLM Applications	10 controls mapped	10 with evidence	100.0%	PASS
OWASP Top 10 (2021)	9 controls mapped	9 with evidence	100.0%	PASS
SOC 2 Type II readiness	9 controls mapped	9 with evidence	100.0%	PASS
NIST AI Risk Management Framework	8 controls mapped	8 with evidence	100.0%	PASS
NIST SP 800-53 Rev. 5	12 controls mapped	12 with evidence	100.0%	PASS
NIST Cybersecurity Framework 2.0	8 controls mapped	8 with evidence	100.0%	PASS
FedRAMP Rev. 5	10 controls mapped	10 with evidence	100.0%	PASS
PCI DSS v4.0.1	11 controls mapped	11 with evidence	100.0%	PASS
ISO/IEC 27001:2022	9 controls mapped	9 with evidence	100.0%	PASS
MITRE ATT&CK v16	12 controls mapped	12 with evidence	100.0%	PASS
ML Technology Readiness Level	TRL 8	8/8 criteria		PASS

Overall: 16/16 checks passing.

See ISOLATED_LAB_RESULTS/03_Result_Register.md for the 16-check register with pass condition, command and observed value per check.

Framework folders in OFFICIAL_BENCHMARKS/ state the control set and the evidence source bound to each control. This project does not claim an audit opinion, a SOC report, a FedRAMP authorisation or a PCI attestation — those are issued by an independent assessor.

Archives and Permanent Records

Platform	Identifier	Volume
Harvard Dataverse	DOI 10.7910/DVN/YMJKOG	145 citable datasets
AIOSS verification kit	DOI 10.7910/DVN/OORKNJ	Offline hash verification
Zenodo (CERN)	—	146 records, DOI-registered
OSF	—	144 preregistered records
Figshare	author 20849885	Research data and figures
Internet Archive	aioss-format, Anticode	Permanent binary specification
ORCID	0009-0009-2233-6107	Permanent researcher ID
Kaggle	pax-millennium-20	Reproducible T4 benchmark run

Press and Independent Publication

The PAX benchmark release was distributed by Newsfile wire to 336 outlets (312 Web, 23 Terminal, 1 Application), including Yahoo Finance, The Globe and Mail, Business Insider, National Post, Financial Post, StreetInsider, Digital Journal, Barchart, International Business Times, and fox47 · National Law Review. Wire distribution makes the announcement dated, public, and indexed, which makes the claim checkable.