The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
This allows configuration of multi
On 1/12/21 6:27 PM, Dominick Grift wrote:
>
> Community,
>
> Optional SELinux support has been added to OpenWrt for a while now and I
> gave a talk about the status at "Battle of the meshes 13th edition".
>
> There was a comment mentioning that there was an impression that
> "rolling out SELinux
On 12/01/21 18:27, Dominick Grift wrote:
-
My question to the reader is: why haven't you enabled SELinux yet on
your test builds at least? Or maybe you have but you havent given any
feedback. Why is that?
Thanks,
Lack of documentation. Selinux is not an easy topic eve
From: Rafał Miłecki
Flashing image with BCM4908 CFE bootloader requires specific firmware
format. It needs 20 extra bytes with magic numbers and CRC32 appended.
This tools allows appending such a tail to the specified image and also
verifying CRC32 of existing BCM4908 image.
Signed-off-by: Rafa
On 2021-01-09 09:40, Andre Heider wrote:
Hi,
(cc'ed some recent commiters for lantiq)
On 15/12/2020 10:35, Andre Heider wrote:
v2:
- drop 0002-ltq-vdsl-app-fix-Wundef-warnings.patch
- use "/dev/dsl_cpe_api" without the "0" suffix for the adsl daemon:
package/kernel/lantiq/ltq-adsl/patches/1
Stijn Segers kirjoitti 13.1.2021 klo 0.48:
Have tested this on a few low-RAM devices, among which a TL-WR841N v7 (32
MiB) and a WNDR3700 v2 (64 MiB).
No idea if this is still necessary/wanted but would be nice to see this end
up in master (and trickle down to 21.xx :-D ).
Tested-by: Stijn Se
Hello Alberto,
Thanks for you input. I agree that leveraging SELinux is, like for
example leveraging Linux netfilter, not trivial.
SELinux is however well documenting and with the exception of OpenWrt
specifics it might not be productive to yet again document aspects
that are already published els
OpenWRT uses different commands than other distros for manipulating configs, so
those different programs are going to need to be given appropriate permissions.
Who is going to do that work? Who is going to field all the issues that will
come up because the permissions are not correct for some u
On 1/13/21 5:42 PM, David Lang wrote:
> OpenWRT uses different commands than other distros for manipulating
> configs, so those different programs are going to need to be given
> appropriate permissions.
UCI should already be addressed barring any loose ends (LuCI coverage is
still rough though)
Hi,
On Mon, 2020-11-30 at 23:19 +0100, Bjørn Mork wrote:
> Bjørn Mork (10):
> dt-bindings: mtd: partitions: add OpenWrt defined U-Boot Image
> kernel: mtdsplit_uimage: read extralen from device tree
> kernel: mtdsplit_uimage: replace "fonfxc" and "sge" parsers
> kernel: mtdsplit_uimage: ad
Ben,
seems to me, that at least "firmware-5-ct-full-community-12.bin-lede.013" is
still not recovered. File is there, but contains only 0x00.
This seems to cause my fresh build of 19.07.5 to fail.
+ curl -f --connect-timeout 20 --retry 5 --location --insecure https://
www.candelatech.com/downlo
---
package/network/services/libteam/Makefile | 30 +
.../0001-fix-build-on-OpenWRT-musl-libc.patch | 43 +++
2 files changed, 73 insertions(+)
create mode 100644 package/network/services/libteam/Makefile
create mode 100644
package/network/services/libteam/patche
---
package/libs/libnl/Makefile | 19 ++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/package/libs/libnl/Makefile b/package/libs/libnl/Makefile
index db0c65c7a7..3b9bad4533 100644
--- a/package/libs/libnl/Makefile
+++ b/package/libs/libnl/Makefile
@@ -52,16 +52,26
13 matches
Mail list logo
