I am not sure if you are already aware, master fails to build after
today's git pull:
-sections -std=c99 -znow -zrelro -Wl,--gc-sections -o openvpn argv.o
base64.o buffer.o clinat.o comp.o compstub.o comp-lz4.o crypto.o
crypto_openssl.o crypto_mbedtls.o dhcp.o error.o event.o fdmisc.o
forward
On 2018-02-16 11:28, Mauro Mozzarelli wrote:
I am not sure if you are already aware, master fails to build after
today's git pull:
-sections -std=c99 -znow -zrelro -Wl,--gc-sections -o openvpn argv.o
base64.o buffer.o clinat.o comp.o compstub.o comp-lz4.o crypto.o
crypto_openssl.o crypto_mb
On 16.02.2018 11.33, Koen Vandeputte wrote:
On 2018-02-16 11:28, Mauro Mozzarelli wrote:
I am not sure if you are already aware, master fails to build after
today's git pull:
Hi all
This is related to the mbed TLS update, 2.7 adds digest functions with
return types (instead of void return),
From: Rafał Miłecki
Make it execute required unmount code first and then take care of
removing entry from the internal list. This is a small cleanup grouping
code by their purpose.
Signed-off-by: Rafał Miłecki
---
mount.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --gi
Between mbedtls 2.6.0 and 2.7.0, the void returning mbedtls_MODULE* functions
were deprecated in favor of functions returning an int error code. Use
the new function mbedtls_sha256_ret().
Signed-off-by: Russell Senior
---
.../320-mbedtls_dont_use_deprecated_sha256_function.patch | 11 +
Between mbedtls 2.6.0 and 2.7.0, the void returning mbedtls_MODULE* functions
were deprecated in favor of functions returning an int error code. Use
the new function mbedtls_sha256_ret().
Signed-off-by: Russell Senior
---
.../300-mbedtls_dont_use_deprecated_sha256_function.patch | 11 +
Hi,
whats on the critical todo list for the upcoming release ? i still have
a few minor things that I'll be adding shortly, apart from that I am
currently not aware of any huge problems. the release will be a mix
between 4.9 and 4.14 afaik !?
John
__
Fixes the build issue
Tested-by: Koen Vandeputte
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Fixes the build issue
Tested-by: Koen Vandeputte
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
From: Rafał Miłecki
If device disappears but there is still some application trying to
access it, unmounting will fail with the EBUSY errno. Unlinking
/tmp/mounts/ would succeed but things could go wrong depending
on the application accessing that path.
If some app doesn't check if /tmp/mounts/
All devices behind the bridge are properly discovered now.
Tested-by: Koen Vandeputte
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Tested-by: Koen Vandeputte
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Tested-by: Koen Vandeputte
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Tested-by: Koen Vandeputte
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Hi,
I'm trying the official nighly build image on an Atmel (Microchip) sama5d3
xplained board. It seems that Init segfaults.
I'm using this image:
https://downloads.lede-project.org/snapshots/targets/at91/sama5/openwrt-at91-sama5-at91-sama5d3_xplained-sdcard.img.gz
I get this on the console:
> On Feb 16, 2018, at 5:46 AM, John Crispin wrote:
>
> Hi,
>
> whats on the critical todo list for the upcoming release ? i still have a few
> minor things that I'll be adding shortly, apart from that I am currently not
> aware of any huge problems. the release will be a mix between 4.9 and
On 16 February 2018 at 13:46, John Crispin wrote:
> whats on the critical todo list for the upcoming release ? i still have a
> few minor things that I'll be adding shortly, apart from that I am currently
> not aware of any huge problems. the release will be a mix between 4.9 and
> 4.14 afaik !?
On Fri, Feb 16, 2018 at 4:46 AM, John Crispin wrote:
> Hi,
>
> whats on the critical todo list for the upcoming release ? i still have a
> few minor things that I'll be adding shortly, apart from that I am currently
> not aware of any huge problems. the release will be a mix between 4.9 and
> 4.14
On Thu, Feb 15, 2018 at 3:29 AM, Felix Fietkau wrote:
> On 2018-02-14 16:20, Rosen Penev wrote:
>> On Tue, Feb 13, 2018 at 11:10 PM, Felix Fietkau wrote:
>>> On 2018-02-13 23:53, Rosen Penev wrote:
Based on Qualcomm driver. Improves iperf3 throughput by ~20mbps on
transmit on Archer C7
People that build there own images and choose OpenSSH would be expected to know
what they are doing and for that reason not allowing password logins as a
default seems reasonable, but ... even those knowledgeable users may sometimes
forget to add a public key and find their lovely router soft br
20 matches
Mail list logo
