Re: [OpenWrt-Devel] uclient-fetch & SSL WAS:Re: DD: CONFIG_BUSYBOX_DEFAULT_WGET is not set

2016-01-24 Thread Bastian Bittorf
* Martin Tippmann [24.01.2016 09:10]: > Sorry if I was not clear - I meant uclient-fetch not wget. me too, i showed the link /bin/wget which *is* uclient-fetch > # opkg list | grep uclient > libuclient - 2016-01-21-b9808a8c3a8922ed8df4e6fe45848ac2e52f13be >

Re: [OpenWrt-Devel] DD: CONFIG_BUSYBOX_DEFAULT_WGET is not set

2016-01-24 Thread John Clark
Did you see my patch? [OpenWrt-Devel] [PATCH] base-files: fix sysupgrade 'wget' handling for uclient-fetch The key is that uclient-fetch needs to be copied to ramfs during a sysupgrade: install_bin /bin/uclient-fetch /bin/wget Notice that change r48451 only moves the symbolic link to busybox

[OpenWrt-Devel] [CC 15.05] bind: Security update (4 CVEs)

2016-01-24 Thread jow
The bind package has been rebuilt and was uploaded to the Chaos Calmer 15.05 repository due to multiple security issues. VERSION 9.9.7-P3-1 => 9.9.8-P3-1 CHANGELOG [Sun, 24 Jan 2016 12:43:29 +0100 41dcf83] Fixes: * CVE-2015-8704 * CVE-2015-3193 * CVE-2015-8000 * CVE-2015-8461 CHANGES

Re: [OpenWrt-Devel] [PATCH 1/2] swconfig: implement (PHY) generic PORT_LINK setter

2016-01-24 Thread Jonas Gorski
Hi, On 21 January 2016 at 14:55, Rafał Miłecki wrote: > It's quite common for switches to have PHY per port so we may use a > generic function for setting port link. We just need an API to access > PHYs which this patch also adds. > > Signed-off-by: Rafał Miłecki

Re: [OpenWrt-Devel] Discussion: Replace BUSYBOX NSLOOKUP by hostip package

2016-01-24 Thread Arjen de Korte
Citeren Christian Schoenebeck : For some (good) reason you decided to remove wget from BusyBox and replace it by uclient-fetch. Why not also remove nslookup from BusyBox. - If compiled with musl it malfunction with given dns-server Correct. It will

Re: [OpenWrt-Devel] DD: CONFIG_BUSYBOX_DEFAULT_WGET is not set

2016-01-24 Thread Christian Schoenebeck
Additional question: If I understand right uclient-fetch only support to give an explicit certificate via command line switch --ca-certificate=:Load CA certificates from file so no path allowed !? Thanks Christian Am 24.01.2016 um 13:38 schrieb Arjen de Korte: > Citeren

Re: [OpenWrt-Devel] DD: CONFIG_BUSYBOX_DEFAULT_WGET is not set

2016-01-24 Thread Christian Schoenebeck
I'm currently looking on ddns-scripts and still got certificate problems I'm on r48470 including ca-certificates package installed root@OpenWrt:~# uclient-fetch -O- 'https://myuser:myp...@update.spdns.de/nic/update?hostname=myhost.example.com=8.8.8.8' Downloading

[OpenWrt-Devel] [PATCH] kernel: mtdsplit: add missing digest field to Seama header

2016-01-24 Thread Rafał Miłecki
Seama format has 2 similar headers: container (seal) header and entity header. The first one has size always set to 0 and doesn't contain MD5 digest. When dealing with Seama on a flash we deal directly with an entity. You can see mtdsplit_parse_seama reads from offset 0 and expects entity to be

Re: [OpenWrt-Devel] DD: CONFIG_BUSYBOX_DEFAULT_WGET is not set

2016-01-24 Thread Felix Fietkau
On 2016-01-24 14:47, Christian Schoenebeck wrote: > Additional question: > If I understand right uclient-fetch only support to give an explicit > certificate via command line switch > --ca-certificate=:Load CA certificates from file > > so no path allowed !? Right now it defaults

Re: [OpenWrt-Devel] [PATCH] vlandev: Add support for setting a unique MAC on a VLAN interface

2016-01-24 Thread Andre Valentin
Am 24.01.2016 um 20:47 schrieb André Valentin: > There are cases where you need a different MAC on a VLAN interface, i.e. if > if have move than one connection to a switch. A later change of the MAC > is not possible on VLAN interfaces, so it has to be done on creation. > The new macaddr option

Re: [OpenWrt-Devel] [PATCH] vlandev: Add support for setting a unique MAC on a VLAN interface

2016-01-24 Thread Andre Valentin
Am 24.01.2016 um 21:34 schrieb Gio: > On Sunday 24 January 2016 20:47:26 André Valentin wrote: >> There are cases where you need a different MAC on a VLAN interface, i.e. if >> if have move than one connection to a switch. A later change of the MAC >> is not possible on VLAN interfaces, so it has