Re: OpenWrt 21.02.3 Third service release

2022-04-22 Thread Bas Mevissen via openwrt-devel
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 ---

On 2022-04-21 00:21, Hauke Mehrtens wrote:

Hi,

The OpenWrt community is proud to announce the third service release
of OpenWrt 21.02. It fixes security issues, improves device support,
and brings a few bug fixes.



Thanks for all the hard work put into this!

I noticed a small issue during the upgrade using the sysupgrade in Luci. 
After the first attempt, it showed I was still running 21.02.2. Flashing 
the same file again gave me the correct version (21.02.3). (the status 
overview also showed the old kernel version and a low uptime, so there 
was a reboot and I did not misread the version).
I also only have the latest binary for a single router on my PC, so no 
mistake possible there as well.


The only difference between my first and second attempt was that I did 
not tick the box "Include in backup a list of current installed packages 
at /etc/backup/installed_packages.txt" the second time. I do have some 
extra packages installed and updated some during the 21.02.2 lifetime.


Router is a TP Link Archer C7 v5 that was running 21.02.2 before the 
upgrade.


If more people experience this, it might be worth spending time on it. 
Otherwise, it might be best to just retry and be happy!


Regards,

Bas.

--- End Message ---
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [PATCH] tplink-safeloader: add TP-Link Deco M4R v1 and v2 support

2022-04-22 Thread Ole Kristian Lona via openwrt-devel
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 ---
Thank you! I wish I knew of this before. Maybe this should be added to 
https://lists.openwrt.org/mailman/listinfo/openwrt-devel?

Seems my very first email to the list also came through, so I now have the same 
patch lying there twice. 


Best regards,

Ole Kristian Lona

On 22/04/2022, 12:26, "Bjørn Mork"  wrote:

Ole Kristian Lona via openwrt-devel 
writes:

> I tried sending a patch yesterday for Deco M4R v3 and Deco M5. I am very 
new
> to this "send patches to mailing-list" procedure. Did my patch ever reach
> this list?

All patches to this list will end up in patchwork, so you can easily
verify that the status yourself:
https://patchwork.ozlabs.org/project/openwrt/list/

Looks like your patch is there:
mailman.7137.1650526985.441203.openwrt-de...@lists.openwrt.org 
https://patchwork.ozlabs.org/project/openwrt/patch/mailman.7137.1650526985.441203.openwrt-de...@lists.openwrt.org/


Bjørn



--- End Message ---
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: [PATCH] tplink-safeloader: add TP-Link Deco M4R v1 and v2 support

2022-04-22 Thread Bjørn Mork
Ole Kristian Lona via openwrt-devel 
writes:

> I tried sending a patch yesterday for Deco M4R v3 and Deco M5. I am very new
> to this "send patches to mailing-list" procedure. Did my patch ever reach
> this list?

All patches to this list will end up in patchwork, so you can easily
verify that the status yourself:
https://patchwork.ozlabs.org/project/openwrt/list/

Looks like your patch is there:
https://patchwork.ozlabs.org/project/openwrt/patch/mailman.7137.1650526985.441203.openwrt-de...@lists.openwrt.org/


Bjørn

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


Re: OpenWrt 19.07.10 service release

2022-04-22 Thread Roger Pueyo Centelles | Guifi.net via openwrt-devel
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 ---
Hi,

Congratulations for this service release! Could it be that the index
page at https://downloads.openwrt.org hadn't been updated to show
19.07.10? The same goes for 21.02.3.

Thanks,

Roger

El 21/4/22 a les 0:21, Hauke Mehrtens ha escrit:
> Hi,
>
> The OpenWrt community is proud to announce the newest service release
> of OpenWrt 19.07. It fixes security issues, improves device support,
> and brings a few bug fixes.
>
> OpenWrt 19.07.10 is the final release of the 19.07 release branch,
> this branch is now end of life and we will not fix problems on this
> branch any more, not even severe security problems. We encourage all
> users still using OpenWrt 19.07 to upgrade to OpenWrt 21.02 or more
> recent OpenWrt versions.
>
> We recently moved our bugs to GitHub, please report issues over there
> (after checking that nobody else posted the same issue before).
> https://github.com/openwrt/openwrt/issues/
>
> Download firmware images via the Firmware Selector or directly from
> our download servers:
>  * https://firmware-selector.openwrt.org
>  * https://downloads.openwrt.org/releases/19.07.10/
>
> The main changes from OpenWrt 19.07.9 are:
>
> Security fixes
> ==
>
>  * wolfssl: Fix multiple security problems
>    (CVE-2022-25638, CVE-2022-25640)
>  * openssl: Fix security problem (CVE-2022-0778)
>  * zlib: Backport security fix for a reproducible crash in compressor
>
> Device support
> ==
>
>  * OCEDO Raccoon: Fix link for long cables with
>  * MikroTik wAP: Fix device detection
>
> Various fixes and improvements
> ==
>
>  * imagebuilder: Fix broken image generation with external targets
>  * imagebuilder: Fix partition signature
>  * patchelf: Backport fix for rpath endianness
>  * base-files: Call “sync” after initial setup
>  * ubus: backport Fixes for UAF and other issues
>
> Core components
> ===
>
>  * Update Linux kernel from 4.14.167 to 4.14.275
>  * Update mac80211 from 4.19.221-1 to 4.19.237-1
>  * Update openssl from 1.1.1m to 1.1.1n
>  * Update wolfssl from 4.7.0 to 5.2.0
>
> Regressions
> ===
>
>  * at91 images are not created any more because the build needs Python.h
>    which is not installed on the build bots.
>    * To fix this issue export the missing environmental variable before
>  using the ImageBuilder: export SOURCE_DATE_EPOCH=1
>  * oxnas/ox820 images are not created any more because of a
>    build problem
>
> Full release notes and upgrade instructions are available at
> https://openwrt.org/releases/19.07/notes-19.07.10
>
> In particular, make sure to read the regressions and known issues before
> upgrading:
> https://openwrt.org/releases/19.07/notes-19.07.10#regressions
>
> For a very detailed list of all changes since 19.07.9, refer to
> https://openwrt.org/releases/19.07/changelog-19.07.10
>
> For latest information about the 19.07 series, refer to the wiki at:
> https://openwrt.org/releases/19.07/
>
> To download a OpenWrt 19.07.10 firmware image for your device, head to
> the Table of Hardware:
> https://openwrt.org/toh/start
>
> Or use the new firmware selector:
> https://firmware-selector.openwrt.org/
>
> You can also navigate directly in the list of firmware images:
> https://downloads.openwrt.org/releases/19.07.10/targets/
>
> As always, a big thank you goes to all our active package maintainers,
> testers, documenters, and supporters.
>
> Have fun!
>
> The OpenWrt Community
>
> ---
>
> To stay informed of new OpenWrt releases and security advisories, there
> are new channels available:
>
>  * a low-volume mailing list for important announcements:
> https://lists.openwrt.org/mailman/listinfo/openwrt-announce
>
>  * a dedicated "announcements" section in the forum:
> https://forum.openwrt.org/c/announcements/14
>
>  * other announcement channels (such as RSS feeds) might be added in the
>    future, they will be listed at https://openwrt.org/contact
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel


--- End Message ---
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


RE: [PATCH] tplink-safeloader: add TP-Link Deco M4R v1 and v2 support

2022-04-22 Thread Ole Kristian Lona via openwrt-devel
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 ---
Hello.

I tried sending a patch yesterday for Deco M4R v3 and Deco M5. I am very new
to this "send patches to mailing-list" procedure. Did my patch ever reach
this list? (I got a message back regarding DMARC, and using original From:
Header, and it was hard to determine from the message whether it would
actually get delivered.)  Seems it would "fit" very nicely with this one, as
that would get at least most Deco M4Rs covered by tplink-safeloader. I will
try to find firmware from M4R v4, to verify whether it uses the same
partition scheme as v3.

Regards,

Ole Kristian

-Original Message-
From: openwrt-devel  On Behalf Of
Foica David
Sent: fredag 22. april 2022 00:10
To: openwrt-devel@lists.openwrt.org
Cc: Foica David 
Subject: [PATCH] tplink-safeloader: add TP-Link Deco M4R v1 and v2 support

Support creating images for TP-Link Deco M4R v1 and v2.

Original partition layout from OEM image:
 partition fs-uboot base 0x0 size 0x8  partition os-image base
0x8 size 0x20  partition file-system base 0x28 size 0xc0
partition product-info base 0xe8 size 0x05000  partition default-mac
base 0xe85000 size 0x01000  partition device-id base 0xe86000 size 0x01000
partition support-list base 0xe87000 size 0x1  partition user-config
base 0xea7000 size 0x1  partition device-config base 0xeb7000 size
0x1  partition group-info base 0xec7000 size 0x1  partition
partition-table base 0xed7000 size 0x02000  partition soft-version base
0xed9000 size 0x1  partition profile base 0xee9000 size 0x1
partition default-config base 0xef9000 size 0x1  partition url-sig base
0xfe size 0x1  partition radio base 0xff size 0x1

The 'os-image' and 'file-system' partitions were merged into 'firmware'
to make use of the automatic mtd split.

The first 2 versions of the device use the same firmware image,
v3 and v4 are different.

Signed-off-by: Foica David 
---
 src/tplink-safeloader.c | 49 +
 1 file changed, 49 insertions(+)

diff --git a/src/tplink-safeloader.c b/src/tplink-safeloader.c index
c4727df..604cce8 100644
--- a/src/tplink-safeloader.c
+++ b/src/tplink-safeloader.c
@@ -1779,6 +1779,55 @@ static struct device_info boards[] = {
.last_sysupgrade_partition = "file-system"
},
 
+   /** Firmware layout for the Deco M4R v1 and v2 */
+   {
+   .id = "DECO-M4R",
+   .vendor = "",
+   .support_list =
+   "SupportList:\n"
+
"{product_name:M4R,product_ver:1.0.0,special_id:5553}\n"
+
"{product_name:M4R,product_ver:1.0.0,special_id:4555}\n"
+
"{product_name:M4R,product_ver:1.0.0,special_id:4341}\n"
+
"{product_name:M4R,product_ver:1.0.0,special_id:4A50}\n"
+
"{product_name:M4R,product_ver:1.0.0,special_id:4155}\n"
+
"{product_name:M4R,product_ver:1.0.0,special_id:4B52}\n"
+
"{product_name:M4R,product_ver:1.0.0,special_id:4944}\n"
+
"{product_name:M4R,product_ver:2.0.0,special_id:5553}\n"
+
"{product_name:M4R,product_ver:2.0.0,special_id:4555}\n"
+
"{product_name:M4R,product_ver:2.0.0,special_id:4341}\n"
+
"{product_name:M4R,product_ver:2.0.0,special_id:4A50}\n"
+
"{product_name:M4R,product_ver:2.0.0,special_id:4155}\n"
+
"{product_name:M4R,product_ver:2.0.0,special_id:4B52}\n"
+
"{product_name:M4R,product_ver:2.0.0,special_id:5457}\n"
+
"{product_name:M4R,product_ver:2.0.0,special_id:4234}\n"
+
"{product_name:M4R,product_ver:2.0.0,special_id:4944}\n",
+   .part_trail = 0x00,
+   .soft_ver = SOFT_VER_DEFAULT,
+
+   /* We're using a dynamic kernel/rootfs split here */
+   .partitions = {
+   {"fs-uboot", 0x0, 0x8},
+   {"firmware", 0x8, 0xe0},/** Stock:
name os-image base 0x8 size 0x20 */
+   /** Stock:
name file-system base 0x28 size 0xc0 */
+   {"product-info", 0xe8, 0x05000},
+   {"default-mac", 0xe85000, 0x01000},
+   {"device-id", 0xe86000, 0x01000},
+   {"support-list", 0xe87000, 0x1},
+   {"user-config", 0xea7000, 0x1},
+   {"device-config", 0xeb7000, 0x1},
+   {"group-info", 0xec7000, 0x1},
+   {"partition-table", 0xed7000, 0x02000},
+   {"soft-version", 0xed9000, 0x1},
+   {"profile", 0xee9000, 0x1},
+   {"default-config", 0xef9000, 0x1},
+   {"url-sig",