Turris OS packages issueshttps://gitlab.nic.cz/turris/os/packages/-/issues2023-08-31T16:53:46+02:00https://gitlab.nic.cz/turris/os/packages/-/issues/920python script dhcp_host_domain_ng.py sourced as shell script2023-08-31T16:53:46+02:00Václav Votípkapython script dhcp_host_domain_ng.py sourced as shell scriptI noticed that my log is flooded with these records:
```
Jun 16 06:41:38 turris dnsmasq-script[4571]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 3: import: not found
Jun 16 06:41:38 turris dnsmasq-script...I noticed that my log is flooded with these records:
```
Jun 16 06:41:38 turris dnsmasq-script[4571]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 3: import: not found
Jun 16 06:41:38 turris dnsmasq-script[4571]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 4: import: not found
Jun 16 06:41:38 turris dnsmasq-script[4571]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 5: import: not found
Jun 16 06:41:38 turris dnsmasq-script[4571]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 6: import: not found
Jun 16 06:41:38 turris dnsmasq-script[4571]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 7: import: not found
Jun 16 06:41:38 turris dnsmasq-script[4571]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 8: import: not found
Jun 16 06:41:38 turris dnsmasq-script[4571]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 9: import: not found
Jun 16 06:41:38 turris dnsmasq-script[4571]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 10: from: not found
Jun 16 06:41:38 turris dnsmasq-script[4571]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 11: from: not found
Jun 16 06:41:38 turris dnsmasq-script[4571]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 13: from: not found
Jun 16 06:41:38 turris dnsmasq-script[4571]: /usr/lib/dnsmasq/dhcp-script.sh: /etc/resolver/dhcp_host_domain_ng.py: line 16: syntax error: unexpected "("
Jun 16 06:41:38 turris dnsmasq[4571]: script process exited with status 2
```
The `dhcp_host_domian_ng.py` is sourced as shell file at the beginning of the `/usr/lib/dnsmasq/dhcp-script.sh`:
```shell
#!/bin/sh
[ -f "$USER_DHCPSCRIPT" ] && . "$USER_DHCPSCRIPT" "$@"
```
There is also similar 4 years old bug: https://gitlab.nic.cz/turris/os/packages/-/issues/332
I experienced this issue on TurrisOS 6.3.3, Turris OmniaRichard MuzikRichard Muzikhttps://gitlab.nic.cz/turris/os/packages/-/issues/926No renew of expired certificate2023-08-28T16:42:09+02:00Michal HruseckyNo renew of expired certificateWe have a package that creates a self-signed certificate on first install if it isn't one present.
https://gitlab.nic.cz/turris/os/packages/-/blob/master/net/lighttpd-https-cert
But it should be extended ideally to check whether certif...We have a package that creates a self-signed certificate on first install if it isn't one present.
https://gitlab.nic.cz/turris/os/packages/-/blob/master/net/lighttpd-https-cert
But it should be extended ideally to check whether certificate is still valid and not currupted and if it is, regenerate it.
So this would need moving from uci-default script to proper init script run somewhere before lighttpd gets started.Turris OS 7.0Richard MuzikRichard Muzikhttps://gitlab.nic.cz/turris/os/packages/-/issues/840schnapps: Encrypted export fails if `gnupg2` package is installed2023-08-28T16:36:51+02:00Simon Borekschnapps: Encrypted export fails if `gnupg2` package is installedRunning `schnapps export NUMBER DEST` with password encryption set and `gnupg2` package installed (on Omnia HBL, TOS 6) leads to export failure. This happens even in case both gnupg and gnupg2 are installed as gnupg2 then becomes the de...Running `schnapps export NUMBER DEST` with password encryption set and `gnupg2` package installed (on Omnia HBL, TOS 6) leads to export failure. This happens even in case both gnupg and gnupg2 are installed as gnupg2 then becomes the default 'gpg' (no matter the installation order).
stderr:
```
gpg: keybox '/tmp/tmp.cbbaAi/gpg/pubring.kbx' created
gpg: failed to start agent '/usr/bin/gpg-agent': No such file or directory
gpg: can't connect to the agent: No such file or directory
gpg: problem with the agent: No agent running
tar: Child returned status 2
tar: Error is not recoverable: exiting now
Snapshot export failed!
```
Might defaulting to gnupg (GPG 1.4) be the solution (as gnupg2 is missing some important components in OpenWrt packages such as pinentry [and probably gpg-agent as well] and it's usefulness is therefore pretty limited even in other scenarios)?
Or would it be better for [Schnapps](https://gitlab.nic.cz/turris/schnapps) to explicitly use gpg1 (might be problematic if running outside TOS)?Richard MuzikRichard Muzikhttps://gitlab.nic.cz/turris/os/packages/-/issues/841schnapps: add dependency on "gnupg" (GPG 1.4) package2023-08-28T16:36:16+02:00Simon Borekschnapps: add dependency on "gnupg" (GPG 1.4) packageGPG is required for the encrypted export to work. Should user be able to use the whole documented Schnapps functionality `gnupg` package must be installed by default.
`gnupg2` currently doesn't work well on OpenWrt and TOS, so it does n...GPG is required for the encrypted export to work. Should user be able to use the whole documented Schnapps functionality `gnupg` package must be installed by default.
`gnupg2` currently doesn't work well on OpenWrt and TOS, so it does not seem like a suitable default (see #840 ).Richard MuzikRichard Muzikhttps://gitlab.nic.cz/turris/os/packages/-/issues/768Minor bug in logging of /etc/resolver/dhcp_host_domain_ng.py2023-08-24T13:57:40+02:00ktetzlaffMinor bug in logging of /etc/resolver/dhcp_host_domain_ng.pyThe `filename. line` arguments in last line of:
```python
def _remove_hints_hosts(self, filename):
with open(filename, "r") as handle:
for line in handle:
line = line.strip()
if no...The `filename. line` arguments in last line of:
```python
def _remove_hints_hosts(self, filename):
with open(filename, "r") as handle:
for line in handle:
line = line.strip()
if not line or line.startswith("#"):
continue
try:
host = line.strip().split()[1]
self._call_kresd("hints.del('%s')" % host)
except:
log("Wrong host format '%s' in host file %s " %
(filename, line), LOG_ERR)
```
need to be switched to `line, filename`:
```python
log("Wrong host format '%s' in host file %s " %
(line, filename), LOG_ERR)
```https://gitlab.nic.cz/turris/os/packages/-/issues/925missing tailscale package for turris1x2023-08-24T10:42:46+02:00Jan Včelákmissing tailscale package for turris1xI would like to install Tailscale on the old Turris 1x running Turris OS 6.4 and I noticed its not packaged while it's available for Omina.
https://repo.turris.cz/hbs/omnia/packages/packages/ has the packages
```
tailscale_1.24.2-1_arm_...I would like to install Tailscale on the old Turris 1x running Turris OS 6.4 and I noticed its not packaged while it's available for Omina.
https://repo.turris.cz/hbs/omnia/packages/packages/ has the packages
```
tailscale_1.24.2-1_arm_cortex-a9_vfpv3-d16.ipk 01-Aug-2023 19:55 3665695
tailscaled_1.24.2-1_arm_cortex-a9_vfpv3-d16.ipk 01-Aug-2023 19:55 6224284
```
https://repo.turris.cz/hbs/turris1x/packages/packages/ is missing the packages
Please, would it be possible to build Tailscale for the older device as well? Or is there an issue with the build on that platform? Thanks!https://gitlab.nic.cz/turris/os/packages/-/issues/915Nextcloud easy_install.sh IP invalid2023-08-23T17:18:09+02:00ArusekkNextcloud easy_install.sh IP invalidRelated: #633
Connecting to Nextcloud via IP address after a setup with everything left to default values results in **Access through untrusted domain** error.
The guilty line is:
https://gitlab.nic.cz/turris/os/packages/-/blob/master...Related: #633
Connecting to Nextcloud via IP address after a setup with everything left to default values results in **Access through untrusted domain** error.
The guilty line is:
https://gitlab.nic.cz/turris/os/packages/-/blob/master/net/nextcloud/files/easy_install.sh#L113
```sh
IP="`uci -q get network.lan.ipaddr`"
```
On the current default config, this results in `192.168.1.1/24` instead of `192.168.1.1`, which is not understood by Nextcloud trusted domains validator.
Maybe it could be changed (in the spirit of the alternative IP getting method) to something like:
```sh
IP="`uci -q get network.lan.ipaddr |sed -n 's|\([0-9.]*\).*|\1|p'`"
```
A workaround is to manually change the relevant `trusted_domains` config entry.https://gitlab.nic.cz/turris/os/packages/-/issues/680Provide only Nextcloud install script2023-08-23T15:29:02+02:00Josef SchlehoferProvide only Nextcloud install scriptRight now, we provide install script and Nextcloud. In some cases, this is a little bit problematic when you are switching to different branches and Nextcloud is downgraded and such. Currently, I am updating Nextcloud in minor versions, ...Right now, we provide install script and Nextcloud. In some cases, this is a little bit problematic when you are switching to different branches and Nextcloud is downgraded and such. Currently, I am updating Nextcloud in minor versions, because on various storage devices it takes different time (my experience is ~30min] because there is also update of Nextcloud, database and so on.
There are two possibilities:
1) Nextcloud is able to update itself - on click / automatically.
We can provide just install script and Nextcloud itself will take a rest including the update. Why we shouldn't let do it itself? I think they should be able to update it much better than us currently.
2) Provide Turris OS updates very oftenTurris OS 6.4.0Michal HruseckyMichal Hruseckyhttps://gitlab.nic.cz/turris/os/packages/-/issues/924lighttpd fails to start because of tvheaded conf.d config file2023-08-23T14:19:23+02:00Milan Juříklighttpd fails to start because of tvheaded conf.d config file2023-08-07 12:09:18: (../src/sock_addr.c.456) getaddrinfo failed: Name does not resolve '192.168.1.1/24'
2023-08-07 12:09:18: (../src/server.c.1913) Configuration of plugins failed. Going down.
with simple generated config:
config inte...2023-08-07 12:09:18: (../src/sock_addr.c.456) getaddrinfo failed: Name does not resolve '192.168.1.1/24'
2023-08-07 12:09:18: (../src/server.c.1913) Configuration of plugins failed. Going down.
with simple generated config:
config interface 'lan'
option proto 'static'
option ip6assign '60'
option _turris_mode 'managed'
list ipaddr '192.168.1.1/24'
option device 'br-lan'
/usr/libexec/multimedia/tvheadend-dynamic generates wrong lighttpd conf.d output
| Turris OS version | 6.4.1 |https://gitlab.nic.cz/turris/os/packages/-/issues/25Bump net-snmp version2023-08-16T14:58:36+02:00Krzysztof KuleszaBump net-snmp versionPlease bump net-snmp version and compile it with modules ucd-snmp/lmsensorsMibPlease bump net-snmp version and compile it with modules ucd-snmp/lmsensorsMibTurris OS 3.11.21Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/packages/-/issues/102Feature Requst: Please add iptables-mod-tee package2023-08-16T14:58:34+02:00JamesFeature Requst: Please add iptables-mod-tee packageThis is one way to mirror all traffic to an OOB security device.This is one way to mirror all traffic to an OOB security device.https://gitlab.nic.cz/turris/os/packages/-/issues/122mwan3: fix uses of logread in luci app2023-08-16T14:58:31+02:00Jan Pavlinecmwan3: fix uses of logread in luci appRelated post on forum: https://forum.turris.cz/t/combination-of-syslog-ng-luci-system-logging-configuration-mwan3/5975
Code with logread:
https://gitlab.labs.nic.cz/turris/turris-os-packages/blob/test/net/mwan3-luci/files/usr/lib/lua/lu...Related post on forum: https://forum.turris.cz/t/combination-of-syslog-ng-luci-system-logging-configuration-mwan3/5975
Code with logread:
https://gitlab.labs.nic.cz/turris/turris-os-packages/blob/test/net/mwan3-luci/files/usr/lib/lua/luci/controller/mwan3.lua#L116Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/packages/-/issues/128Clamav: Update to the Latest Upstream Version - 0.99.22023-08-16T14:58:29+02:00Ghost UserClamav: Update to the Latest Upstream Version - 0.99.2Please update Clamav and the accompanying luci app for clamav to the latest upstream version. The current version 0.99.2
OpenWRT Clamav upstream https://github.com/openwrt/packages/tree/master/net/clamav
https://github.com/openwrt/pack...Please update Clamav and the accompanying luci app for clamav to the latest upstream version. The current version 0.99.2
OpenWRT Clamav upstream https://github.com/openwrt/packages/tree/master/net/clamav
https://github.com/openwrt/packages/tree/master/net/clamav/filesJan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/packages/-/issues/178unbound: try to get closer to upstream version2023-08-16T14:58:26+02:00Jan Pavlinecunbound: try to get closer to upstream versionOur version of unbound package is quite different from upstream version ( https://github.com/openwrt/packages/tree/master/net/unbound )
* Configuration is shipped via resolver-conf package https://gitlab.labs.nic.cz/turris/turris-os-pac...Our version of unbound package is quite different from upstream version ( https://github.com/openwrt/packages/tree/master/net/unbound )
* Configuration is shipped via resolver-conf package https://gitlab.labs.nic.cz/turris/turris-os-packages/tree/test/net/resolver-conf
* Root key is in dnssec-rootkey https://gitlab.labs.nic.cz/turris/turris-os-packages/tree/test/net/dnssec-rootkey
We could try to follow config option from https://github.com/openwrt/packages/blob/master/net/unbound/files/unbound.uci in resolver-conf unbound section. So it's not so confusing for users from openwrt.
Related forum topic https://forum.turris.cz/t/resolver-negleting-extented-unbound-configuation-file-s/6841Turris OS 6.0Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/packages/-/issues/183Update boost libraries2023-08-16T14:58:23+02:00TomasUpdate boost librariesFor newest domoticz (upstream) the recommended version of boost libraries is 1.66:
Its recommended that you use the latest Boost libraries - as of December 2017 that is version 1.66.
http://www.domoticz.com/wiki/Raspberry_Pi_-_Build_Dom...For newest domoticz (upstream) the recommended version of boost libraries is 1.66:
Its recommended that you use the latest Boost libraries - as of December 2017 that is version 1.66.
http://www.domoticz.com/wiki/Raspberry_Pi_-_Build_Domoticz_from_source#Build_.26_Install_Boost_Libraries
Definitely, it cannot be build with current 1.58. The error I got with my current domoticz Makefile hosted at https://github.com/trusnak/domoticz-turris is:
```
[ 1%] Generating stdafx.h.gch/.c++
/home/linker/turris-os/staging_dir/toolchain-powerpc_8540_gcc-4.8-linaro_uClibc-0.9.33.2/lib/gcc/powerpc-openwrt-linux-uclibcspe/4.8.3/../../../../powerpc-openwrt-linux-uclibcspe/lib/crt1.o: In function `_start':
/home/linker/turris-os/build_dir/toolchain-powerpc_8540_gcc-4.8-linaro_uClibc-0.9.33.2/uClibc-0.9.33.2/libc/sysdeps/linux/powerpc/crt1.S:93: undefined reference to `main'
/home/linker/turris-os/build_dir/toolchain-powerpc_8540_gcc-4.8-linaro_uClibc-0.9.33.2/uClibc-0.9.33.2/libc/sysdeps/linux/powerpc/crt1.S:94: undefined reference to `main'
collect2: error: ld returned 1 exit status
CMakeFiles/domoticz_gch.dir/build.make:60: recipe for target 'stdafx.h.gch/.c++' failed
make[5]: *** [stdafx.h.gch/.c++] Error 1
```
I'm not aware if any other packages depends on boost, but it was added as domoticz dependency in TurrisOS 2.5, so I think not.
Could you please update boost libraries?Jan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/packages/-/issues/185https-dns-proxy: update to upstream version2023-08-16T14:58:22+02:00Josef Schlehoferhttps-dns-proxy: update to upstream versionThe version in our repository is outdated and should be updated to the latest version, which is available since 23.4.2018.
Here is a link to upstream package: https://github.com/openwrt/packages/tree/master/net/https-dns-proxyThe version in our repository is outdated and should be updated to the latest version, which is available since 23.4.2018.
Here is a link to upstream package: https://github.com/openwrt/packages/tree/master/net/https-dns-proxyJan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/packages/-/issues/202Request to add package: ipmitool2023-08-16T14:58:21+02:00Josef SchlehoferRequest to add package: ipmitool**ipmitool is utility for controlling IPMI-enabled devices**
OpenWRT link: https://github.com/openwrt/packages/tree/master/admin/ipmitool
Github repository: https://github.com/ipmitool/ipmitool
Requested on our [forum](https://forum....**ipmitool is utility for controlling IPMI-enabled devices**
OpenWRT link: https://github.com/openwrt/packages/tree/master/admin/ipmitool
Github repository: https://github.com/ipmitool/ipmitool
Requested on our [forum](https://forum.turris.cz/t/question-how-to-have-ipmitool-on-turris-omnia/5687/6?u=pepe).https://gitlab.nic.cz/turris/os/packages/-/issues/218shadowsocks-libev: update to version 3.2.02023-08-16T14:58:20+02:00Josef Schlehofershadowsocks-libev: update to version 3.2.0Package name: **shadowsocks-libev**
Short description of the package: **lightweight implementation of shadowsocks protocol**
OpenWRT repository:
https://github.com/openwrt/packages/tree/master/net/shadowsocks-libev
Upstream repos...Package name: **shadowsocks-libev**
Short description of the package: **lightweight implementation of shadowsocks protocol**
OpenWRT repository:
https://github.com/openwrt/packages/tree/master/net/shadowsocks-libev
Upstream repository:
https://github.com/shadowsocks/shadowsocks-libev/
_Version information_
We have version: 2.2.3.
Upstream and OpenWRT have version: 3.2.0
Dependencies:
* [x] libcares
We have version: 1.11.0
Upstream and OpenWRT have version: 1.14.0 ( https://github.com/openwrt/packages/blob/master/libs/c-ares/Makefile )
* [x] libev
We have version: 4.22
Upstream and OpenWRT have version: 4.22 ( https://github.com/openwrt/packages/blob/master/libs/libev/Makefile )
* [x] libpcre (commit in dev branch: https://gitlab.labs.nic.cz/turris/turris-os-packages/commit/57fb7f173d90ea6b299599a00b705b06b923915f)
We have version: 8.41
Upstream and OpenWRT have version: 8.42 ( https://github.com/openwrt/packages/blob/master/libs/pcre/Makefile )
* [ ] libpthread
We have version: 1.1.15
Upstream and OpenWRT have version:
* [x] libsodium
We have version: 1.0.10
Upstream and OpenWRT have version: 1.0.16 ( https://github.com/openwrt/packages/tree/master/libs/libsodium )
* [x] libmbedtls (commit in dev branch: https://gitlab.labs.nic.cz/turris/openwrt/commit/70303e1c8cb9b4734bb02479fb952078ffc14ff2)https://gitlab.nic.cz/turris/os/packages/-/issues/228Enable SSL support in zabbix packages2023-08-16T14:58:00+02:00Petr GregorEnable SSL support in zabbix packagesHi,
since turris is a security conscious OS I would like to request SSL support in zabbix packages. Currently SSL support is not compiled in so it cannot be enabled. It seems openwrt package got the support recently: https://github.com/o...Hi,
since turris is a security conscious OS I would like to request SSL support in zabbix packages. Currently SSL support is not compiled in so it cannot be enabled. It seems openwrt package got the support recently: https://github.com/openwrt/packages/commit/dda7a55418acf14d0c3d5fd82ab1b0cc2946c05a
Thank youJan PavlinecJan Pavlinechttps://gitlab.nic.cz/turris/os/packages/-/issues/231ddns-script: reboot bug2023-08-16T14:57:58+02:00Jan Pavlinecddns-script: reboot bugddns-script is causing rebootddns-script is causing reboot