- Mar 03, 2019
-
-
Roger A. Light authored
-
Roger Light authored
Implement DLT logging
-
Roger A. Light authored
This can be used to clear retained messages on a broker.
-
- Feb 28, 2019
-
-
Roger A. Light authored
-
Roger A. Light authored
-
Roger A. Light authored
-
Roger A. Light authored
-
Pierre Fersing authored
Signed-off-by:Pierre Fersing <pierre.fersing@bleemeo.com>
-
krismattheus authored
Signed-off-by:krismattheus <kris.mattheus@visionbms.com>
-
Roger A. Light authored
-
Roger A. Light authored
-
Roger A. Light authored
This is for Ephemeral DH support on listeners.
-
Roger A. Light authored
-
Roger A. Light authored
-
Roger A. Light authored
-
Roger A. Light authored
-
- Feb 27, 2019
-
-
Roger A. Light authored
-
Roger A. Light authored
-
Roger A. Light authored
Sets default to use the backoff mechanism.
-
Abilio Marques authored
Signed-off-by:Abilio Marques <abiliojr@gmail.com>
-
Abilio Marques authored
Signed-off-by:Abilio Marques <abiliojr@gmail.com>
-
Abilio Marques authored
Signed-off-by:Abilio Marques <abiliojr@gmail.com>
-
Roger A. Light authored
1399064 1399065 1398655 1398656 1398654 1399067 1399066 1399063 1399060 1399059 1399068 1399062 1398657 1398653 1302848 1302847 1399070
-
Roger A. Light authored
-
Steven Lawrance authored
Signed-off-by:Steven Lawrance <stl@koffein.net>
-
Roger A. Light authored
-
Roger A. Light authored
And some related fixes.
-
Roger A. Light authored
-
Roger A. Light authored
-
Roger A. Light authored
-
Roger A. Light authored
-
- Feb 26, 2019
-
-
Nicolás Pernas Maradei authored
Some OpenSSL engines (selectable via tls_engine option) may require a password to make use of private keys created with them in the first place. The TPM engine for example, will require a password to access the underlying TPM's Storage Root Key (SRK), which is the root key of a hierarchy of keys associated with a TPM; it is generated within a TPM and is a non-migratable key. Each owned TPM contains a SRK, generated by the TPM at the request of the Owner. [1] By default, the engine will prompt the user to introduce the SRK password before any private keys created with the engine can be used. This could be inconvenient when running on an unattended system. Here's where the new tls_engine_kpass_sha option comes in handy. The user can specify a SHA1 hash of its engine private key password via command line or config file and it will be passed on to the engine directly. This commit adds support for both clients (libmosquitto) and broker. [1] https://goo.gl/qQoXBY Signed-off-by:
Nicolás Pernas Maradei <nicopernas@gmail.com>
-
Nicolás Pernas Maradei authored
Add same OpenSSL engine support to mosquitto (server side) previously added to client side only. Signed-off-by:Nicolás Pernas Maradei <nicopernas@gmail.com>
-
Nicolás Pernas Maradei authored
- Clients can now offload crypto tasks to an external crypto device through the OpenSSL ENGINE API. - The keyfiles can now be treated as PEM or ENGINE keys. - Two new functions were added to libmosquitto to set up the previously mentioned features. - Both mosquitto_sub and mosquitto_pub include support to turn on the mentioned features through command line options. Signed-off-by:Nicolás Pernas Maradei <nicopernas@gmail.com>
-
- Feb 21, 2019
-
-
Roger A. Light authored
-
- Feb 19, 2019
-
-
Roger A. Light authored
Plus tests.
-
Roger A. Light authored
-
Roger A. Light authored
-
Roger A. Light authored
This is for broker outgoing connack and publish packets only.
-
- Feb 18, 2019
-
-
Roger A. Light authored
Closes #1169. Thanks to Christoph Krey.
-