When cross-compiling Domoticz on a system without GPIO, the WITH_GPIO
flag is not set by cmake, and GPIO support is disabled as a result.
Enabling GPIO support by adding the flag to TARGET_CXXFLAGS.
Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
This release contains some security fixes.
CVE-2017-0898: Buffer underrun vulnerability in Kernel.sprintf
CVE-2017-10784: Escape sequence injection vulnerability in the Basic authentication of WEBrick
CVE-2017-14033: Buffer underrun vulnerability in OpenSSL ASN1 decode
CVE-2017-14064: Heap exposure in generating JSON
Multiple vulnerabilities in RubyGems
Update bundled libyaml to version 0.1.7.
And many other bugfix.
Signed-off-by: Luiz Angelo Daros de Luca <luizluca@gmail.com>
By using $(CP) instead of $(INSTALL_DATA) we preserve symbolic links and
by doing so we dont copy the same file multiple times. This saves some
space.
Signed-off-by: Marko Ratkaj <marko.ratkaj@sartura.hr>
Domoticz 3.8153 introduced support for dzVents. Unfortunately this was
broken by the 902_add-scripts-path, which attempts to make Domoticz more
FHS-compliant instead of throwing everything under /opt/domoticz.
The problem is that dzVents scripts added via the webinterface will be
generated on the filesystem. With the 902_add-scripts-path patch,
Domoticz tried to write this to "scriptsdir/dzVents/generated_scripts".
As the scriptsdir contains scripts that come with upstream, and are not
meant to be changed, this defaults to /usr/share/domoticz/scripts, which
is not writeable, so Domoticz is unable to write the script to the
filesystem. What is worse is that this silently fails.
Fix this by moving the generated_scripts dir to
"userdatadir/generated_scripts". The userdatadir defaults to
/var/lib/domoticz, which is writeable.
Additionally, since this patch does more than just adding the scripts
path, rename it to something more appropriate.
Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
revert the update as the new wget version links to libunistring
that is a rather large library. Better to revert the update now
in order to fix buildbot and then look into solutions.
signed-off-by: Hannu Nyman <hannu.nyman@iki.fi>
Update netdata to 1.8.0
Add back python modules, these are tweaked (modified) for netdata
Add additional flags to slim down the binary size
Signed-off-by: Daniel Engberg <daniel.engberg.lists@pyret.net>
Patch includes updates to packages:
netopeer2: update to version 0.4.0
sysrepo: update to 0.7.0
libnetconf2: update to 0.9.15
libyang: update to 0.13.46
Signed-off-by: Mislav Novakovic <mislav.novakovic@sartura.hr>
Notable changes since 3.0.8
ede744a: depends on libcares now instead of libudns
1c64829: new cmdline option --no-delay for not turning off TCP_NODELAY
9201619: ss-local: check if client supports socks5 protocol and no-auth-required method
f8283fc: Fix potential buffer overflow when parsing json config
380fddb: redir: fix conversion from DSCP to ToS
The two patches are now in the offical repo
Modify init script to use standard uci configuration and procd for
process management. We benefit from:
- use of standard LEDE configuration with its ability to revert and
commit changes
- validation of configuration variables
- procd taking care of restarting daemon when config changes and user
wants to reload it
- automatic respawning of daemon process in case it dies
The source is patched to make it possible to run as a daemon in
foreground.
Signed-off-by: Marcin Jurkowski <marcin1j@gmail.com>
Uptime plugin fails to adjust for system time changes after boot.
As Openwrt/LEDE routers usually do not have a RTC, the system time
gets adjusted with NTP possibly after collectd has already started.
But collectd continues to use the initial time set by 'sysfixtime',
which can lead to incorrect uptime calculations.
Apply a proposed fix from upstream that uses /proc/uptime
Reference to https://github.com/collectd/collectd/pull/2034Fixes#4819
Signed-off-by: Hannu Nyman <hannu.nyman@iki.fi>
Client package adds the CoAP client allowing to communicate with 6LoWPAN
devices via the CoAP protocol.
Server package adss the CoAP server and the CoAP Resource Directory server.
The CoAP server allows to simulate 6LoWPAN devices which can be addressed
via the CoAP protocol while the CoAP Resource Directory server can handle
resource registrations using the CoAP protocol.
Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
Hirokazu MORIKAWA