• https://mosquitto.org/files/source/ (Download)

• (2021-06-10) Updated to version: mosquitto-2.0.11
• (2021-04-05) Updated to version: mosquitto-2.0.10
• (2021-03-13) Updated to version: mosquitto-2.0.9
• (2021-02-26) Updated to version: mosquitto-2.0.8
• (2021-02-05) Updated to version: mosquitto-2.0.7
• (2021-01-29) Updated to version: mosquitto-2.0.6
• (2020-08-22) Updated to version: mosquitto-1.6.12
• (2020-08-15) Updated to version: mosquitto-1.6.11
• (2020-06-10) Updated to version: mosquitto-1.6.10
• (2020-03-13) Updated to version: mosquitto-1.6.9

Log message:
update to mosquitto-2.0.11

Log message:
net/mosquitto: avoid upcoming build failure
Use OpenSSL 1.1.1 code path that uses SSL_CTX_up_ref() instead of
handrolling it. This way mosquitto will continue to build after
an upcoming libssl bump.

Log message:
update to mosquitto-2.0.10

Log message:
update to mosquitto-2.0.9

Log message:
mosquitto: remove the patch to sample config that told it to write a pid
file when running as a daemon (in /var/run/mosquitto.pid). in 2.x priv
dropping was changed to do less before dropping privs and this no longer
works. found by patrick@

Log message:
update to mosquitto-2.0.8

Log message:
Reverse the polarity of MODPY_VERSION; default is now 3.x,
if a port needs 2.x then set MODPY_VERSION=${MODPY_DEFAULT_VERSION_2}.
This commit doesn't change any versions currently used; it may be that
some ports have MODPY_DEFAULT_VERSION_2 but don't require it, those
should be cleaned up in the course of updating ports where possible.
Python module ports providing py3-* packages should still use
FLAVOR=python3 so that we don't have a mixture of dependencies some
using ${MODPY_FLAVOR} and others not.

Log message:
update to mosquitto-2.0.7

Log message:
mosquitto also needs docbook-xsl

Log message:
mosquitto: xsltproc needed for build

Log message:
update to mosquitto-2.0.6

Log message:
drop maintainership for i no longer use these

Log message:
mosquitto: build with optional websockets support so that it can be
enabled in config if wanted. following a query from Jeff Ross
ok jasper@ (maintainer)

Log message:
update to mosquitto-1.6.12 addressing a memory leak when handling PUBLISH messages

Log message:
update to mosquitto-1.6.11

Log message:
mosquitto patches were merged upstream, and fastnetmon was submitted upstream

Log message:
submitted upstream

Log message:
give regress tests a chance to run again

Log message:
- update to mosquitto-1.6.10
- switch to python3
- rework some patches for inclusion upstream

Log message:
update to mosquitto-1.6.9

Log message:
update to mosquitto-1.6.8

Log message:
add forgotten patch; no bump as it didn't package before

Log message:
update to mosquitto-1.6.7

Log message:
replace simple PERMIT_PACKAGE_CDROM=Yes with PERMIT_PACKAGE=Yes

Log message:
update to mosquitto-1.5.8

Log message:
security update to mosquitto-1.5.6
https://mosquitto.org/blog/2019/02/version-1-5-6-released/

Log message:
update to mosquitto-1.5.5

Log message:
Add COMPILER lines to c++ ports which currently use the default. Adjust
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.

Log message:
security update to mosquitto-1.5.3 which addresses CVE-2018-12543.
it's recommended users update as quickly as possible to prevent a
malicious user from triggering the issue and causing the server to
go offline.
note this does not affect mosquitto 1.4.x which is available on
OPENBSD_6_3.
thanks to upstream mosquitto for the heads-up

Log message:
update to mosquitto-1.5.2

Log message:
update to mosquitto-1.5.1

Log message:
update to mosquitto-1.5
https://mosquitto.org/blog/2018/05/version-1-5-released/

Log message:
remove patches that are no longer needed as this builds fine with -current libressl

Log message:
Switch HOMEPAGE and MASTER_SITES to https.
ok jasper

Log message:
change the configuration to only listen on localhost by default instead of on all
available interfaces. there are too many misconfigured mqtt servers to be found
that expose all topics to the whole world..

Log message:
- update to mosquitto-1.4.15
- take maintainership
ok edd@ (previous MAINTAINER)

Log message:
remove traces of utf8 encoding in pkg/DESCR
bump accordingly

Log message:
Change the shebang line from /bin/sh to /bin/ksh in all ports rc.d
daemon scripts and bump subpackages that contain the *.rc scripts.
discussed with and OK aja@
OK tb

Log message:
bump LIBCXX/LIBECXX/COMPILER_LIBCXX ports.

Log message:
use COMPILER_LIBCXX where applicable

Log message:
rand()%x -> arc4random_uniform, split up from a large diff, seems fine
to edd@

Log message:
use libc's uuid generation functions rather than pulling in e2fsprogs.
split up from a combined diff, seems fine to edd@

Log message:
enable tests, part of a larger diff which seems fine to edd@

Log message:
use LIBCXX

Log message:
update to mosquitto-1.4.11
ok edd@ (MAINTAINER)

Log message:
Don't pick up libcares.

Log message:
Drop @extra -- /var/run is cleaned at boot time.