You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proposal: Support for secure communication with collectd should be added. This is described in the manpage of collectd.conf(5). There is support for both authenticated (but unencrypted) as well as encrypted communication built into collectd and the network plugin.
Current behavior:
Simple tests revaled, that influxdb simply ignores any data that is signed and/or encrypted, hence this functionality has to be disabled on the collectd side. Looking through the influxdb code, I don't see any support for authenticated and/or encrypted data.
Desired behavior:
Add support for authenticated and/or encrypted data. Add appropriate options and honor them.
Use case: This is important because right now incoming data is not authenticated. It is possible to change values while they are being transmitted (man in the middle), hence the data within the database is not trustworthy. Since collectd has built-in support for authenticated and/or encrypted data, the influxdb interface should make use of it.
The text was updated successfully, but these errors were encountered:
I needed it and my Go is not too strong, so I wrote a lightweight proxy in Python. It receives encrypted/signed collectd packets and forwards them as plain packets. If you bind the InfluxDB collectd service to the loopback interface and install the proxy on the same server it does the trick. https://github.com/marcv81/collectd_proxy
I appreciate this is not the most elegant solution. Hopefully it can be useful in the meantime, and it provides some information to help implement this feature.
Feature Request
Proposal: Support for secure communication with collectd should be added. This is described in the manpage of collectd.conf(5). There is support for both authenticated (but unencrypted) as well as encrypted communication built into collectd and the network plugin.
Current behavior:
Simple tests revaled, that influxdb simply ignores any data that is signed and/or encrypted, hence this functionality has to be disabled on the collectd side. Looking through the influxdb code, I don't see any support for authenticated and/or encrypted data.
Desired behavior:
Add support for authenticated and/or encrypted data. Add appropriate options and honor them.
Use case: This is important because right now incoming data is not authenticated. It is possible to change values while they are being transmitted (man in the middle), hence the data within the database is not trustworthy. Since collectd has built-in support for authenticated and/or encrypted data, the influxdb interface should make use of it.
The text was updated successfully, but these errors were encountered: